On Mar 31, 2007, at 5:56 PM, Peter J. Russell wrote: Hi All,
I have had this issue on a couple of sites I visit now since December and now have a total of 5 different sites all showing the same errors with the same setup.
Basically what happens is that I build the server with a base OS, reboot, create DNS and test that both forward and reverse lookups work perfectly, promote the server to an Open Directory Master and reboot, open Workgroup Manager and create a user and the following error appears:
"Got unexpected error
Error of type Not a known DirStatus (-1) on line 1922
of /SourceCache/ServerManagerUserGeneral/
ServerManagerUserGeneral-193.4.1/
UserAdvancedPluginView.mm"
As far as I can tell, the Password Service crashes when the user is created and when it restarts does not completely re-read the full password database. As a result of this, all other users in the directory when this error occurs, are suddenly locked out until the server is restarted.
An interesting thing I did note, is that if I create a user and leave the default shortname as generated by the server (eg. untitled_1) then the error does not happen. As soon as the shortname is modified then it crashes.
Because of this, all 5 sites need to reboot their servers immediately following the creation of any new users which as one would assume is very frustrating.
The only thing in common I have been able to determine is that the servers are all running 10.4 on Intel chipsets. I can replicate my procedure exactly on a PowerPC server and have no issues.
One other thing to note is that when I logon to a machine as a local administrator after the password service crash happens and attempt to mount a share using basic authentication, it fails. If I create a kerberos ticket manually using the client as part of 10.4, then I can successfully mount shares to the server.
System Details as follows:
Hardware - Servers:
Either Intel XServe or Intel MacPro, I have also tested on an Intel iMac just to see what would happen and I was able to replicate the errors on that as well so I'm thinking here that hardware is not a factor. I have also run full hardware tests using the DVDs that shipped with the machines just in case RAM or something else was an issue originally. Now that it's happening everytime I build a machine I fail to see how this is possible.
Software - OS:
I'm using the build that shipped with the XServes on them at 10.4.8 OSX Server, for the Mac Pros I'm using 10.4.7 purchased separately and then upgraded to 10.4.8 - the issues happen on both OSs
I have lodged a support call with Apple but so far have had little to no results as far as figuring out what the cause is, let alone solution for this is.
If anyone has anything to shed on this that would be fantastic. I know of at least two others who are based in Australia with exactly the same problem.
Just for anecdotal counter-evidence, on the (only two) Intel Xserves I'm working with to date, I have categorically not seen this issue.
A couple thoughts: are you using the supplied version of Server Admin/WM on the server itself in each case ?
For the MacPros did you follow Apple's procedure ? |
