Its my best theory that that’s what is going on. Maybe I should describe the situation a little more fully. The server was operating fine, and then it became unresponsive, spinning beach ball on the machine. I was able to bring up a force quit dialog, but unable to interact with it. I was connected via ssh from another machine, and was able to do anything that didn’t require a new process or thread to launch. I had to power off the server. When it came back, the Open Directory node wasn’t responding to connection attempts. When attempting to to access the node through Workgroup Manager I get the error that the node couldn’t be opened because of an unexpected error -14002. The system log indicates failed attempts to bind to the Open Directory node due to bad parameters or something (I can’t remember the exact message now, but can check tomorrow at the office) reported by the Directory Service process. The Open Directory log from Server Admin is recording connections when I attempted to connect with Workgroup Manager, but like I said, I just get an error from there. Database corruption is the thing that I suspect since the power off could have hosed it.
As to send/receive mail, we don’t use this server as a mail server.
.
.
Comments are closed