I can't login anymore to the server, neither via Remote Desktop nor ssh

done. will post whatever reply I get. may just bite the bullet and reinstall the OS. This problem showed up again this morning (Friday). Only made it three days this time. 😐

Bill

This might not be an option for you (or perhaps many others), but I solved it by setting the server to automatically reboot every day or so ( Energy Saver control panel - Schedule... button). I am always suspect of the "reinstall the OS" option, especially when it is an issue that only raises it's head after many week or even months of trouble free operation. Since applying above band-aid the problem hasn't appear in 2 weeks. The issue is no doubt still there, but just isn't allowed a chance to screw anything up before being reset.

Vince

I will most likely take your advise. Yeah, it isn't the most elegant solution in the world, but I just don't know if Apple is even working on this one.

I'm hoping this thread does not die an untimely death. We're having the same EXACT symptoms on an XServe running 10.5.4. This same computer was running 10.4 just fine, a few weeks after bringing up to 10.5.4 and setting it up as an Open Directory Master it started doing this.

It appears to me that Open Directory is crashing. Unfortunately this is also killing logins from locally authenticated users, even root can't log in. I'd be very interested in hearing from anyone who has made progress on this, or has any kind of confirmation from Apple. On this particular server it seems to run for about a week between recurrences.

I'm having a similar problem after updating to 10.5.4 from 10.5.1. Everything ran smoothly for about a day and then I found I was locked out.

Not working:
SSH, Server Admin (remote), Screen Sharing, ARD, FTP, VNC, Mail, probably other services too.

Working:
WGM, Web server

I had my host reboot with the power button and then I was able to connect with VNC and enter my localadmin id and pw in the server's login window. The login window went away and it just hung on the login background screen. (Now VNC just hangs without opening a window.) Then tried to connect with SSH and eventually got this message:

"Operation could not be completed: An unexpected error occurred (error code -10810)"

That message happened only the first time. Since then SSH times out with this message:

Keith-Kavanaughs-Computer:~ keith$ ssh me@000.00.000.000 -v -v -v
OpenSSH_4.7p1, OpenSSL 0.9.7l 28 Sep 2006
debug1: Reading configuration data /etc/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to bwd01.bauwau.com [216.23.180.214] port 22.
debug1: connect to address 216.23.180.214 port 22: Operation timed out
ssh: connect to host bwd01.bauwau.com port 22: Operation timed out

Server Admin and the other services that aren't working all just hang with no message or error.

For what it's worth, I scanned the ports that Apple says are open by default in the firewall and indeed they were except 626 (Serial Number Support). Maybe that's normal.

Another thing that may or may not be relevant: I used Disk Utility to duplicate the startup disk to a partition on an external drive before updating. When I did that it changed the name of the partition from Backup2 to Macintosh HD, which is the same as the startup volume. I noticed right after that in Server Admin > File Sharing that in the volumes list only the two external drive partitions were listed. Not the startup drive. It did show up in Disk Utility though.

I'm a designer trying to run a server so I'm learning and have just enough server knowledge to screw it up. Any help on a direction to look or even a way to get in and look at the logs would be helpful.

I am having the same problem on two the 2 10 leopard server at my work....

They are both mac pros the rest are G5 towers and a mini.


I think it must be something to do with Mac Pros running leopard server.

I must say leopard server is a sad sight still even after almost a year so much stuff just does not work.
If anyone had seen the directory service and AFP shutting off all the time problem and that it was not fixed until 10.5.3 more then 6 months after it was released they finally made it able to share a file using afp (SAD!).

I hope they can put more effort into snow leopard because I can believe they released leopard server and Im still running into problems all the time...


I really am hoping 10.5.5 will fix this anyone fined a work around besides restarting the server everyday?

Now that 10.5.5 has been released, I'm able to say that I've been running a 10.5.5 seed for over two weeks and I haven't seen this problem since.

This is what I was hoping to hear. I'm going to update the worst offender of my 16 Leopard Servers to 10.5.5 and see if it helps.

If I can go more than a 10 days with that bad boy, then I'm going to update the rest of 'em.

<knocking on wood, throwing salt over my shoulder and crossing my fingers>

- s

Steve

Please report back - success or failure. For logistical reasons, I have to hold off upgrading my two offenders for a couple more weeks. I look forward to hearing something positive from you in 10 or more days.

Vince Dolan

I have installed the update on a server that is doing it everyday so we should know by tomorrow. 🙂

Hi John,

Did 10.5.5 help to resolve the problems for you?

It been working well for me no problem since 🙂 It seems like they have fixed it!!!!


John

Glad it's working for you so far.

I have just upgraded 2 x 10.5.4 xserves, one of which was doing it every 2 ~ 5 days.

I'll post back on how it goes here.

OK, it's been going on 10 days since I updated to 10.5.5 Server and my prime offender is still running fine. Usually, by now, it would've dropped off the network.

I'll feel better after even more time goes by but am pleased so far...

- s

I just wanted to let all of you know that I upgraded to 10.5.5 and still had to restart the server after the 3rd day so that users could login again.