General discussion

Locked

Proliant ML350 G3 Random Reboots

By Dana Grantham ·
Our office is running a Proliant ML350 G3 Server with dual Xeon 2.2GHz processors with 2GB memory and Windows 2000 Server OS. Approximately 3 months or so after we had this server up and running it began rebooting for no apparent reason. We are an accounting firm and it seemed to do it all the time during busy season. After tax season ended, it continued to reboot but less often. However, around 7 months later it started rebooting more and more. Now it is rebooting sometimes on a daily basis and then it will stop for a few days or a week and then reboot again. It never does it at the same time...sometimes during the weekdays...sometimes on week nights and sometimes on the weekend. It does it when there are employees trying to work and it does it when there is nobody on the network or here. The server is updated with all updates. No help with any logs or event viewer.

We have had a local company (that we purchased the system from) look at it numerous times and they feel it is software related. Therefore, it has been reformatted and we installed only the programs that HAD to be installed on the Server...one at a time...and it still does it. And, by-the-way, the partners decided when it first started doing this that it may be a hardware issue and so another server (exact same kind) was purchased as a backup...we could then just pull the drives if something happened and install in backup server and be up and running. Well it reboots randomly too!

Any suggestions would be helpful!!!

Thanks,

Dana

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to Proliant ML350 G3 Random ...

Most probably would say "Lsassa worm" infection which will cause a computer to continually reboot. If no one ever ran a virus check, ought to do that. Also, in the admin tools event log, there HAS to be a critical error message somewhere. Even with default logging there will be something in the events showing a critical error. Even if its "system unexpectantly stopped".

Also, a bad memory chip or chip going bad where the data in memory can't be read might cause the system to hault or cause a critical error and reboot. To stop a critical error reboot, follow the procedure below.

click start,then go to control panel. Click on the System Icon. With the system properties page open click on the Advanced tab [far right top tab]. On the Advanced page, bottom Title is Startup and Recovery. click the button startup & recovery. Under system Failure uncheck the box "Automatically reboot". click ok. Close out all open pages. This should keep the server from continually rebooting itself upon a critical error detection BUT doesn't solve the "Why" your server is acting up.

Collapse -

by CG IT In reply to

note: if you are NOT running antivirus software there, I recommend that you do. Symantecs Corporate Antivirus 8.0/8.1 is a pretty good package and can install antivirus on client computers as well as scan email if you get the version which support it. If you have an "always on" Internet connection e.g. DSL or Cable, get a router. You can use a consumer level router like Linksys BEFxxx series routers with a network [domain or peer to peer].

Also check your system temperatures and recheck your system memory. Check ALL drivers for W2K compatibility especially your graphics drivers and/or NIC drivers.

Collapse -

by CG IT In reply to

note: if you move drives over to another computer with exact same hardware configuration [EXACT} and that reboots as well, you might be looking at a corrupted O/S, and if you reinstall and the rebooting stops for a while but then starts up again, look for a security hole where it takes someone some time to break in and muck up your network. see installing a router and antivirus comments above.

Collapse -

by Dana Grantham In reply to

Poster rated this answer.

Collapse -

by zaferus In reply to Proliant ML350 G3 Random ...

I would recommend troubleshooting the problem in this manner:

1. Look at your cables that connect to the server: Change your switch port, replace the cable to your server. If you have a printer connected to your server move it to a PC for the time being. Eliminate a bad cable causing an electrical problem that forces a server reboot.

2. Look at your power: What type of UPS do you have connected? If it is a smart UPS are you SURE that the cables/software are set up correctly? This could certainly cause your server to reboot.

3. Now if you are comfortable that your environment the server is connected too is all good, time to look at the server itself. Of course do an antivirus sweep in the system - but now you need to realize that you have a Compaq server, with Insight Manager bundled for free with the system. Get this installed and turn the monitoring up on what it watches for software in your system. What happens just before a reboot, what does your event log tell you? These "bread crumbs" can point to your real culprit.

Something as simple as a bad driver or memory leak could be causing a reboot. Mirror your switch port (if it supports it) and run a 24x7 traffic analysis on your server. Is there a pattern to what is sent or recieved just before a reboot to an application/service or process that is running?

Zaf

Collapse -

by Dana Grantham In reply to

Poster rated this answer.

Collapse -

by ross.bale In reply to Proliant ML350 G3 Random ...

Check whether you have windows update running on the server - it is set by default to automatically reboot after succesful installation of patches that require a reboot. There is an option in Group Policy to disable the automatic restart from running (due to the machine being a server).

Collapse -

by Dana Grantham In reply to

Poster rated this answer.

Collapse -

by Dana Grantham In reply to Proliant ML350 G3 Random ...

This question was closed by the author

Back to Networks Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums