- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: strange crond
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 01:28 AM
тАО10-27-2009 01:28 AM
strange crond
I found the two crond process in my server.
new one is created by old one crond. Is it normal?
The crontab job seems running well with no problem even two crond process running.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 02:45 AM
тАО10-27-2009 02:45 AM
Re: strange crond
You can investigate system crontab jobs by reviewing /etc/cron.*/ directories.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 06:00 AM
тАО10-27-2009 06:00 AM
Re: strange crond
First the crond process duplicates itself using a fork(2)/vfork(2) system call.
Then the new copy will switch its identity to to the owner of the cron job and prepare the environment. After the environment is set up, the new copy will replace itself with a shell that runs the actual cron job, using one of the exec(3) family of functions.
Meanwhile, the parent crond process will log that the cron job has been started, and will wait for the SIGCHLD signal that indicates job completion, or start other cron jobs as necessary.
If you grabbed your process list at exactly the right moment, you may have caught the crond in the process of forking itself.
If the child crond remains listed as "crond" for a while, the environment set-up may be delayed for some reason:
- if NIS or LDAP is used, is the NIS/LDAP server responding?
- if the user's home directory is on NFS, is the NFS server responding?
- is the binary or script that the cron job is supposed to run on a NFS filesystem? Is it accessible?
- if the filesystems involved are not NFS, are your disks OK? A failing disk can sometimes cause a disk operation to retry forever, causing a process that requested it to hang.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2009 07:45 PM
тАО10-27-2009 07:45 PM
Re: strange crond
Got your point, and give you points for your feedback.
I have checked back to my crontab configuration, it alwasy occurred on one job which will backup files to remote file systems.
What can I do next?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2009 03:46 PM
тАО10-30-2009 03:46 PM
Re: strange crond
Examine the filesystem that contains the home directory of that user. Is it working OK?
Do you see any error messages in the system logs? (output of "dmesg", log files in /var/log)
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2009 10:47 PM
тАО11-01-2009 10:47 PM
Re: strange crond
No error from dmesg.
Further information for your reference.
1) This 2nd crond issue generated by root's cron job.
2) I use this root account start backup script to backup Oracle database.
3) The backup script will perform su oracle to start RMAN backup database.
Does this su oracle to casue problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 01:07 AM
тАО11-02-2009 01:07 AM
Re: strange crond
The database backup job is apparently running, but is it *finishing*? Or does it leave a script or some other process running in an infinite loop?
The cron job normally attempts to send the job output as email to the job's owner. Maybe the root's inbox (/var/mail/root) has grown huge from accumulated cron job outputs and needs some serious trimming?
*Can* your root account successfully send email to itself? Test with:
echo "Test message" | mail root
or
echo "Test message" | mailx root
What's the load level of your system?
If your system is extremely busy when the backup process is supposed to start, it might take a while for the child crond process to load & start the su command.
How exactly did you detect this "problem"? Have you actually seen it in the "ps" listing, or is this from alerts produced by some monitoring system?
If you can see it in the "ps" listing (and it does not go away before you can run another command), run "ps axf" to see the process listing in a tree form. If the child crond process has children of its own, examine them.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 01:39 AM
тАО11-02-2009 01:39 AM
Re: strange crond
yes, this cron daemon process issue detected by OVO (OpenView Operations).
It says "more cron process exceed 2"