cpsrvd on server failed. Takes down full machine

[housefire]

Every couple of days, for random reasons, we receive the server email that states that

cpsrvd on server failed.

After this happens, the whole server just drops offline. Even ssh doesnt work until a reboot.

Any ideas on how we can fix this? Happens at random times and random dates.

 

[AndyReed]

Every couple of days, for random reasons, we receive the server email that states that

cpsrvd on server failed.

After this happens, the whole server just drops offline. Even ssh doesnt work until a reboot.

Check log files for errors or messages prior to and after the crash. You might have a hardware going bad, or OS malfunction.

 

[gmagana]

Anyone have a solution for this? I am right now in another country and am severly limited in my access to my machine... What logs should I check? After my machine is rebooted it stays up anywhere from 5 minutes to 12 hours and then it locks up again...


Needless to say, this is having a very very negative effect on my server. As far as I know this is entirely a cpanel problem since it is the notice I get cpsrvd failed and then I cannot access my server either through cpanel or through ssh.

If my hardware was going bad I would not even be able to access the hosted websites, some of which I can access.

Please, this is extremely urgent, I am in the middle of nowhere and it is extremely hard to access the internet, much less do some sort of big-scale troubleshooting.

 

[haesu]

Anyone have a solution for this? I am right now in another country and am severly limited in my access to my machine... What logs should I check? After my machine is rebooted it stays up anywhere from 5 minutes to 12 hours and then it locks up again...


Needless to say, this is having a very very negative effect on my server. As far as I know this is entirely a cpanel problem since it is the notice I get cpsrvd failed and then I cannot access my server either through cpanel or through ssh.

If my hardware was going bad I would not even be able to access the hosted websites, some of which I can access.

Please, this is extremely urgent, I am in the middle of nowhere and it is extremely hard to access the internet, much less do some sort of big-scale troubleshooting.

are you running FreeBSD? I'm having same problem even on hardware that was rock solid for years, but this happened after a recent run of upcp via cron. Server locks up anywhere between 5 minutes and up each time you reboot, doesn't even respond to ping.

 

[gmagana]

My hardware is less than 1 year old, all Intel. I am running CentOS 3.

 

[gmagana]

Now that I am back in the USA, I think my problem may be fixed (or helped out at least)... Looking through the posts in this forum, I did several things, I do not know which one did the most to help:

- Through WHM, increased the max amount of RAM cpanel may use to 256 MB (Why is this limit needed? Speaking as a programmer, it sounds like a cheap hack to hide a memory leak in the cpanel daemon, certainly it does not inspire confidence in the cpanel programming).

- Did upcp --force to force a cpanel reinstall.

- Updated RVSkins (I'd be extremely surprised if this had anything to do with the problem at hand).

After doing these things, my server has been up for about 12 hours, which is a vas improvement over 5 minutes. So far, so good. I still get a bunch of these two messages in the error_log file:

Child [22593]: exited with signal 13 [BTW: Does this have to do with the max RAM setting?]

Internal Error: "" Normal Connection Timeout (Probably closed browser on a HTTP/1.1 session) at cpsrvd.pl line 1572.

But my server has not gone down again, even though I get these messages.

BTW: the cpanel logs files are in /usr/local/cpanel/logs, and if your error_log file is empty (as mine was) you have to enable writing to it in WHM.

 

[chirpy]

The age of your hardware is irrelevant. As Andy said, the most likely reason for unexplained server crashes is hardware failures or, less likely, file system corruption. The key would be to look at the console when it crashes and see if there's a kernel oops.

 

[gmagana]

Did you even see my message? If there is a hardware malfunction then nothing would work at all, not just the cpanel/WHM part while the websites continue to work.

Anyway, given the changes I made that I stated above, the server has now stayed up for about 36 hours now, so I have to say this issue was entirely a cpanel problem (no hardware malfunction). There are very few hardware problems that are fixed by high-level (non-driver config) means.

It's very surprising to me that cpanel staff never addressed this very important issue, since our servers are going down, that's about as bad as it gets... I guess there is room for another competitor in the field.

 

[Myrosy]

It happened to me too, after upgraded the CPanel to Latest Version…
There was no problem at all…!!!

 

[chirpy]

Did you even see my message? If there is a hardware malfunction then nothing would work at all, not just the cpanel/WHM part while the websites continue to work.

Yes, I did, and please be less patronising of those trying to help.

You said that the server keeps crashing, and because of that my and Andy's statements stand.

It's very surprising to me that cpanel staff never addressed this very important issue, since our servers are going down, that's about as bad as it gets... I guess there is room for another competitor in the field.

I don't understand this statement. If you've logged a ticket with cPanel support, then why are you posting about it here, since these forums and not for support from cPanel.

 

[gmagana]

Yes, I did, and please be less patronising of those trying to help.
You said that the server keeps crashing, and because of that my and Andy's statements stand.

I also said I could access some of the websites... And if I sounded like an a-hole I apologize, I just got angry at someone re-defining the problem to fit the proposed (and easy to diagnose) cause.

I don't understand this statement. If you've logged a ticket with cPanel support, then why are you posting about it here, since these forums and not for support from cPanel.

I guess it's an act of desperation... It's always easy for a company to say "we don't do support on the forums, put in a ticket." Then the ticket can be gleefully ignored and no one notices (I guess this is the tech support equivalent of killing a process to fix a memory leak). Truly good companies also do support on the forums, and everyone can see what the response time is (not to mention everyone sees the correct solution to the problem without needing to go through the ticket system).

Anyway, I'm blabbing. I know I should vote with my wallet if I'm that disappointed in cpanel...

 

[chirpy]

Indeed you should. But its your own fault if you don't get support when you cannot be bothered to ask for it correctly.

Just so it's clear for you: If you need support from cPanel, then log a ticket through your cPanel license provider. These forums are not an avenue for cPanel support.

 

[deathvult]

I understand the conversatiuon took a dirferent turn, but i would still be interested in know the end of case, after all, same problem on my server, and i figure if i find a solution here, would be interesting.
Have a nice day to you all.:p

 

[ahostli]

This is cPanel problem on 64bit machines. Just disable cpup cron job (update manualy via WHM).

 

[jrehmer]

I'm having the problem on x86 platform. It happens sporadically and I have to restart the cpanel services to get webmail, cpanel, and whm back up.

 

[rafaelgp]

My cpsrvd restarts at 5:31 everydays... That's because upcp is on crontab? I dunno if it is ok, but I don't receive an e-mail when it happens.

 

[maverick23]

same issues with all my servers

even i am having the same issues with all my servers....

whenever i try and save any config file it says 404 error(Page can not be displayed) and then on the othr side nothing functions till i restart cpanel...

after going thorugh the error logs i found given below entries in one of the server:-

Internal Error: "" Normal Connection Timeout (Probably closed browser on a HTTP/1.1 session) a
t cpsrvd-ssl.pl line 1574.
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe
Internal Error: "" Normal Connection Timeout (Probably closed browser on a HTTP/1.1 session) a
t cpsrvd-ssl.pl line 1574.
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe
cp: write error: Broken pipe
cp: write error: Broken pipe
Undefined subroutine &IO::Handle::blocking called at /usr/lib/perl5/site_perl/5.6.2/IO/Socket/
SSL.pm line 223.
cp: write error: Broken pipe

 

[dalem]

do this and it will fix your stunnel and fix your 404 errors

rm -f /usr/local/cpanel/perl/Net/SSLeay/SSLeay.so
kill `cat /var/run/cpsrvd.pid`
/usr/local/cpanel/cpsrvd
/usr/local/cpanel/etc/init/startstunnel


not sure abbout the cp: write error: Broken pipe error


fixed on of my servers today that was suffering the same error

 

[maverick23]

after running /usr/local/cpanel/cpsrvd i got given below error...

Loader: /usr/local/cpanel/3rdparty/etc/ioncube/ioncube_loader_lin_4.4.so: file not found at /usr/local/cpanel/bin/checkphpini line 61.
==> cpsrvd 10.6.1 started

 

[dalem]

untick the ioncube loader in whm tweak setings unlless you are running a third party ap in WHM that needs it you will have to install it