- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: cron daemon errors in syslog
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
Forums
Discussions
Discussions
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
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
05-07-2007 11:05 PM
05-07-2007 11:05 PM
I added these jobs to cron:
00 20 * * 1-5 /backups/Fbackup.nightly > /backups/nightly.log 2>&1
0,10,20,30,40,50 * * * * /usr/lbin/sa/sa1
00 18 * * * find / -name core -print -exec /usr/bin/rm {} \; >/dev/null 2>&1
2 0 * * * find /var/tmp -mtime +6 -exec rm {} \;
3 0 * * * find /var/tmp -mtime +6 -exec rm -rf {} \;
00 19 * * * find / -name 'nohup.out' -exec rm {} \; 2>/dev/null
The syslog is showing the errors for the jobs I added. I just listed this sar.
Cron daemon - could not change the compartment for the job /usr/lbin/sa/sa1
What are these and how do I fix them??
Steve
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 11:17 PM
05-07-2007 11:17 PM
Re: cron daemon errors in syslog
Due to a reference to an uninitialised variable when compartments are
not active on a HP-UX 11i v3 system you may see the following message
logged into syslog.log:
Cron daemon - could not change the compartment for the job /XXXXX
If compartments are not active you can safely ignore this message, your cron jobs will still be scheduled and run correctly.
Best regards,
Marco
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 11:20 PM
05-07-2007 11:20 PM
Re: cron daemon errors in syslog
Any way to find out what variables are needed?
If not how do I prevent them in the syslog?
A get one every ten minutes from sar.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 11:25 PM
05-07-2007 11:25 PM
Re: cron daemon errors in syslog
Marco
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 11:32 PM
05-07-2007 11:32 PM
SolutionThe patch will be "crontab" but has not been launched yet, we need to wait a little bit more for that patch, apparently is under testing right now.
In this case I believe that your cron jobs are working fine, but they are logging that info to the syslog, is the syslog is making its job, so you can ignore those messages while the patch is launched.
Best regards,
Marco ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2007 11:40 PM
05-07-2007 11:40 PM