Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
07-10-2006, 09:31 PM
|
#1
|
LQ Newbie
Registered: Jul 2006
Posts: 14
Rep:
|
crond freezes centos 4.3 box
I have ran redhat enterprise 3.0 for quite a while before upgrading to centos 4.3, without any freezes or server hangs.
Once I installed and configured centos 4.3, it seems that crond is hanging the box. Each time that this happens, it is always the last entry in /var/log/messages as well as /var/log/cron (right as the box freezes) as follows:
Jul 6 02:01:01 server_name crond(pam_unix)[5465]: session closed for user root
This happens intermittently, once a week, or even 2 days in a row.
This has stopped now that crond has been shut down…
Any thoughts?
|
|
|
07-11-2006, 06:40 PM
|
#2
|
Moderator
Registered: May 2001
Posts: 29,415
|
Any thoughts?
My first thought is what breaks by disabling crond: for instance logrotate is run from cronjob. Also stopping crond isn't a solution, it's just like taking painkillers: most likely you're only remedying symptoms, not the cause.
Jul 6 02:01:01 server_name crond(pam_unix)[5465]: session closed for user root
This happens intermittently, once a week, or even 2 days in a row.
Start by examining the commands from your crontabs.
|
|
|
07-12-2006, 12:01 AM
|
#3
|
LQ Newbie
Registered: Jul 2006
Posts: 14
Original Poster
Rep:
|
crond was only disabled temporarily to verify that it was in fact causing the server lock-ups.
Prior to that, most cronjobs were disabled during the troubleshooting process. It turns out that lockups occur during any given valid cron command. It happens with any cronjob, at any time. This seems to be an issue with cron, as the same cronjobs run without issue on the same box when booted up into RH Enterprise 3.0...
Also, the MB is new, and we monitor the temps via lm_sensors so it is not an overheating-related issue.
|
|
|
07-12-2006, 02:44 AM
|
#4
|
Moderator
Registered: May 2001
Posts: 29,415
|
It turns out that lockups occur during any given valid cron command. It happens with any cronjob, at any time. This seems to be an issue with cron, as the same cronjobs run without issue on the same box when booted up into RH Enterprise 3.0...
If it is crond itself you could try and replace the crond rpm for the one from RHEL3.
|
|
|
07-12-2006, 10:25 AM
|
#5
|
LQ Newbie
Registered: Jul 2006
Posts: 14
Original Poster
Rep:
|
Quote:
Originally Posted by unSpawn
It turns out that lockups occur during any given valid cron command. It happens with any cronjob, at any time. This seems to be an issue with cron, as the same cronjobs run without issue on the same box when booted up into RH Enterprise 3.0...
If it is crond itself you could try and replace the crond rpm for the one from RHEL3.
|
Sounds like the best direction to go in at this point... When this first occurred, we updated cron using yum, but that did not help.
Also, another consideration not mentioned before is that we use webmin to update/create some cron jobs and crontab at the cmd prompt for others.
Thanks!
|
|
|
All times are GMT -5. The time now is 11:33 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|