ssh no longer working...

[Santoman]

Hi Folks - I'm hoping someone can help me. I received the dreaded [statscheck] Stats/Server overload message again. This server is just driving me crazy.

Normally, when I get this message, I also cannot get into the server via ssh, NOR can I create new accounts, and my normal cron jobs do not run, so log files get huge, and backups do not run.

Sometimes I can reboot and it is cleared up. Tonight, that did not work. I ssh into the box, and it allows the username and password then just sits there.

I am running:

WHM 10.8.0 cPanel 10.8.2-E4
RedHat Enterprise 3 i686 - WHM X v3.1.0

Anyone have ANY ideas? And yes, I've searched the forum before when this happened, with no success. I can't remember what I did last time to fix this, other than bringing the box up at a lower run level, cleaned up some files, I THINK. This time I REALLY need to document, so I can fix it when it happens again...

Thanks for any help anyone can provide.

Steve

[blweb]

I think you might be able to (when this happens again) log in if you can get access to your whm : security / shell fork bomb protection / disable that so you can get in ssh, do what you have to do and then enable it again.

Hi Folks - I'm hoping someone can help me. I received the dreaded [statscheck] Stats/Server overload message again. This server is just driving me crazy.

Normally, when I get this message, I also cannot get into the server via ssh, NOR can I create new accounts, and my normal cron jobs do not run, so log files get huge, and backups do not run.

Sometimes I can reboot and it is cleared up. Tonight, that did not work. I ssh into the box, and it allows the username and password then just sits there.

I am running:

WHM 10.8.0 cPanel 10.8.2-E4
RedHat Enterprise 3 i686 - WHM X v3.1.0

Anyone have ANY ideas? And yes, I've searched the forum before when this happened, with no success. I can't remember what I did last time to fix this, other than bringing the box up at a lower run level, cleaned up some files, I THINK. This time I REALLY need to document, so I can fix it when it happens again...

Thanks for any help anyone can provide.

Steve

[Santoman]

Thanks for the idea BL, but it IS disabled. And oddly enough, I CAN access WHM without a problem, as long as I don't do anything that requries... cgi? It will not allow me to ssh into the box, and I can't do things like create new accounts from WHM.

The server is overloaded though, which I think is the effect that the stats aren't running properly because of the same problem it's having running things like the create new accounts script...

I think you might be able to (when this happens again) log in if you can get access to your whm : security / shell fork bomb protection / disable that so you can get in ssh, do what you have to do and then enable it again.

[Santoman]

I was able to get in through webmin, and I found THIS in the messages logfile during startup, I don't know if it is relevant or not:

Apr 8 22:21:40 bonaire cpanel: startcpsrvd startup succeeded
Apr 8 22:21:42 bonaire cpanellogd: (internal death) Sat Apr 8 22:21:42 2006 [2870] error: Modification of a read-only value attempted at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBI.pm line 279.
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBI.pm line 276
Apr 8 22:21:42 bonaire cpanellogd: require DBI.pm called at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/mysql.pm line 7
Apr 8 22:21:42 bonaire cpanellogd: DBD::mysql::BEGIN() called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: require DBD/mysql.pm called at /usr/local/cpanel/cpanellogd line 62
Apr 8 22:21:42 bonaire cpanellogd: main::BEGIN() called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: [a fatal error or timeout occurred while processing this directive]

[Santoman]

So, does Cpanel folks provide support to the cpanel product, or do I get support via EV1? My customers are starting to get very frustrated because they do not have stat's (the stat program is hung as well)

Thanks...

Steve

[webignition]

So, does Cpanel folks provide support to the cpanel product, or do I get support via EV1?

For support, you would need to contact whomever supplies your cPanel license.

[Santoman]

For support, you would need to contact whomever supplies your cPanel license.

Thanks!

Steve

[easyhoster1]

I was able to get in through webmin, and I found THIS in the messages logfile during startup, I don't know if it is relevant or not:

Apr 8 22:21:40 bonaire cpanel: startcpsrvd startup succeeded
Apr 8 22:21:42 bonaire cpanellogd: (internal death) Sat Apr 8 22:21:42 2006 [2870] error: Modification of a read-only value attempted at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBI.pm line 279.
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBI.pm line 276
Apr 8 22:21:42 bonaire cpanellogd: require DBI.pm called at /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/DBD/mysql.pm line 7
Apr 8 22:21:42 bonaire cpanellogd: DBD::mysql::BEGIN() called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: require DBD/mysql.pm called at /usr/local/cpanel/cpanellogd line 62
Apr 8 22:21:42 bonaire cpanellogd: main::BEGIN() called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: eval {...} called at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Scalar/Util.pm line 0
Apr 8 22:21:42 bonaire cpanellogd: [a fatal error or timeout occurred while processing this directive]

These errors are due to an outdated perl version. Upgrade perl to 5.8.7 from cpanel and then check for outdated mods by running;

/usr/local/cpanel/bin/checkperlmodules

[Santoman]

These errors are due to an outdated perl version. Upgrade perl to 5.8.7 from cpanel and then check for outdated mods by running;

/usr/local/cpanel/bin/checkperlmodules

I would love to if I could connect to my server via ssh...

[Santoman]

Ok, so the problem was that I had like 20-30GB of audit logs in /var/log/audit.d

This brought the disk to 85%.

I cleaned the files up, rebooted and I can ssh back into the box, and the disk is now at like 13% and the load is down to about 1.

Thanks for all the help folks!!!


Steve

[chirpy]

You should remove laus to stop those being generated as they're usually of little use. Laus (which creates the audit.d logs) is known to make cPanel servers unstable too:
http://forums.cpanel.net/showpost.ph...39&postcount=3

[killerid2k]

Ok, so the problem was that I had like 20-30GB of audit logs in /var/log/audit.d

This brought the disk to 85%.

I cleaned the files up, rebooted and I can ssh back into the box, and the disk is now at like 13% and the load is down to about 1.

Thanks for all the help folks!!!


Steve

Ok wait how can u delete or clean up files if you didnt have ssh access (i read u couldnt ssh in the server).

[Santoman]

Ok wait how can u delete or clean up files if you didnt have ssh access (i read u couldnt ssh in the server).

The system was brought to a run level that allowed me access to it. Then I logged in, poked around, cleaned up, and had thought, when I got it down to 70% clean that it was cool again.

Now I'm back to like 13% free on that disk, and life is good.


Steve