aLeX_1

Registered
Jun 6, 2006
1
0
151
Hello, i don't know if this is the right place to post this but i really dont know what to do about it. I got a new server before some days, everything seemed to be ok at least the first hours.. Then it started rebooting, when it boots i get an email of the type "cpsrvd failed @ Tue Jun 6 17:37:54 2006. A restart was attempted automagicly."

Sometimes, the server hangs up and i need to send a ticket to get my server rebooted. Any ideas about what the fault might be or how do i avoid that in future?
 

innovative2001

Active Member
Jun 5, 2006
29
0
151
Hello,


The cpsrvd is part of cPanel services, it's crashing is pretty common. In fact, it's so common cPanel wrote a watchdog script to restart it when it goes down. This is what's emailing you telling you i
It's really nothing to be too worried over, because as long as the watchdog script is restarting it, you'll have access.

This issue generally happens in case of cPanel get crashed. Here is the possible solution to resolve this issue.
1) Try downgrade to Release version,

2) Use below intruction to resolve the issue.
-Login to your server and su to root.
- Then , run the following commands
rm -f /usr/local/cpanel/cpanel /
/cripts/installgd
/cripts/cleanmd5
/cripts/upcp


Nia R.
Technical Support Executive
Accuwebhosting

3)You can check cpsrvd is starting or not usiong below mentioned command
/etc/init.d/chkservd restart as well works
 

chirpy

Well-Known Member
Verifed Vendor
Jun 15, 2002
13,465
30
473
Go on, have a guess
Well, yes and no - I think you're mis-read their issue.

You're seeing the "cpsrvd failed" message on boot because it didn't start up and chkservd picked it up. That's a symptom, not a cause of the reboot.

As to why it is rebooting, it's impossible to say without more information. You really need to check:

1. /var/log/messages for anything from just before the boot that might indicate a problem

2. Check the serial console for kernel oops messages when it crashes

If you're running a current support OS and it is up to date, then it could point to a hardware problem. Most commonly, it's faulty memory chips, but you may have to start swapping bits in and out to track it down.