-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 03:12 AM
06-05-2011 03:12 AM
cron woes
I have a script that needs to be run at 3AM. It has to be run as the oraprod user. So, I open crontab, # crontab -e oraprod - set all the settings, (full path and everything) - make sure oraprod is in the cron.allow file, and let her rip. The script deosn't run. There is no fanfare in the log file, just,
CMD: /u03/oracle/oraprod/backup/do_backup.sh
> oraprod 12542 c Sun Jun 5 14:10:00 WAT 2011
< oraprod 12542 c Sun Jun 5 14:10:00 WAT 2011 rc=1
Any ideas?
Ron
- Tags:
- crontab
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 04:50 AM
06-05-2011 04:50 AM
Re: cron woes
If would be helpful to see the actual script. You might temporarily add 'set -x' to it and let 'cron' mail that trace to you.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 08:21 AM
06-05-2011 08:21 AM
Re: cron woes
I believe rc=1 just means your script has failed. Try running it from the command line directly to make sure it's doing what you think it should.
Hth,
-klb
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 08:27 AM
06-05-2011 08:27 AM
Re: cron woes
thanks for your help guys.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 08:28 AM
06-05-2011 08:28 AM
Re: cron woes
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-05-2011 09:42 PM
06-05-2011 09:42 PM
Re: cron woes
MK
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-06-2011 04:19 AM
06-06-2011 04:19 AM
Re: cron woes
Should we worry that 14:10:00 != 0300?
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP