crwdns2934065:0crwdne2934065:0: 11
1
1
Our xserve keeps shutting down overnight and needs to be rebooted each morning. We have a spare motherboard that came with the original computer and wonder if you folks would install it or is it easy enough for us to do?
crwdns2934109:0crwdne2934109:0
crwdns2934065:0crwdne2934065:0: 12crwdns2936485:0crwdne2936485:0
79
26
25
I use to run one of these servers for a local University and never had any issues with it for the 4 years I was using it. If there was anything that came along that was not right it would throw out a warning that created a log entry. Find the log and read what it has done. Also I had it set up to notify me by email of any issues and it would send out one if it was not happy about something. Go to the site Markus Weiher mentions above to set up these functions. Also Make sure you have a large enough power/battery backup on the unit.
It is good you bought the server with the service package with it so you have the spare parts. Did it come with spare fan also? Check to see if all the fans are running. This thing is very loud. If yours is not then the fans could be the issue. Make sure that if you try the replacement board you have someone who is use to working with a static mat so they do not zap the board. Do Not Take It Out Of The Bad With Out Using Grounded Static Strap!!!
Good luck. But learn the Management system for the server before starting to tear it apart to fix what may just be a setting.
crwdns2934105:0crwdne2934105:0
crwdns2934065:0crwdne2934065:0: 13,3crwdns2936485:0crwdne2936485:0
45
21
11
Is there the possibility that it's a software issue? I think of something like a cron job misconfigured or forgotten.
crwdns2934105:0crwdne2934105:0
what's a cron job?
Cron jobs are unix scripts that are called to a specified time. In a server enviroment they are used a lot and that made me think that thats the problem, not a hardware fault.
That's along the lines of what I was thinking, software issue, maybe not even an issue. Just something forgotten.
The log files will tell you what you need to know. Unix logs just about everything it does.
crwdns2934065:0crwdne2934065:0: 35,2crwdns2936485:0crwdne2936485:0
142
71
53
crwdns2934105:0crwdne2934105:0
If you think Software is shutting it down, you can come in on a weekend, disconnect all Network connections (so the internal clock cannot update from a time server) and set the clock forward 8 hours or so. Come back every 2 hours and see if it is still running.
crwdns2934065:0crwdne2934065:0: 457
5
1
2
It could be temperature related. Many companies, trying to be more energy efficient, shut down the Air Conditioning at night. I would run Console and check your log files. You should be able to see if a chron job or temperature is shutting it down.
If you do not understand what Console is, someone will either need to do some studying or hire a Unix Guru. You may be able to send the logs to Apple Support, if you have a Service Agreement. It is far beyond the scope of this site to instruct how to analyze log files.
If you think it might be temperature related, leave the door to the room the server is in open (put furniture in the way with a 'do not move' sign) or put a cheap box fan (less than $20) where it will blow air on the server and see if it stays up that night. Note: this is a test, not a permanent solution.
crwdns2934105:0crwdne2934105:0
crwdns2936751:024crwdne2936751:0 0
crwdns2936753:07crwdne2936753:0 0
crwdns2936753:030crwdne2936753:0 4
crwdns2942667:0crwdne2942667:0 1,624
crwdns2947414:01crwdne2947414:0
Does it shut down at the same exact time each time?
crwdns2934271:0crwdnd2934271:0 rab777hp crwdne2934271:0