- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cron rc=137
Operating System - HP-UX
1753361
Members
5599
Online
108792
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО11-28-2000 11:13 AM
тАО11-28-2000 11:13 AM
cron rc=137
cron is reporting a return code of 137
getting same code on both Solaris 2.6 and HP-UX 10.20
but each are executing very different scripts
trying to discover what this code means
have had numerous sysmap ovflo reported on HP-UX but
not aware of any problems on Solaris system
thanks
Bill
getting same code on both Solaris 2.6 and HP-UX 10.20
but each are executing very different scripts
trying to discover what this code means
have had numerous sysmap ovflo reported on HP-UX but
not aware of any problems on Solaris system
thanks
Bill
so many toys, so little time
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2000 01:05 PM
тАО11-28-2000 01:05 PM
Re: cron rc=137
The rc= field in cron logs indicates the "return code" or exit value
of a process. For example, if the cron log indicates rc=1, then the process exited with return status 1. There is also a "ts=" which
is for when the process is terminated with a signal. See wait(2) and /usr/include/sys/wait.h for more details on how return status is returned
to the parent process (in this case cron).
Undocumented errors which are returned (especially those which are very
unusual values such as 137) are generally caused by a program not returning
a specific code upon exit, causing random return code. Since Unix does not impose a standard return-code scheme, there is no requirement for a program to have an interesting return code at all.
Steffi Jones
of a process. For example, if the cron log indicates rc=1, then the process exited with return status 1. There is also a "ts=" which
is for when the process is terminated with a signal. See wait(2) and /usr/include/sys/wait.h for more details on how return status is returned
to the parent process (in this case cron).
Undocumented errors which are returned (especially those which are very
unusual values such as 137) are generally caused by a program not returning
a specific code upon exit, causing random return code. Since Unix does not impose a standard return-code scheme, there is no requirement for a program to have an interesting return code at all.
Steffi Jones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2000 01:34 PM
тАО11-28-2000 01:34 PM
Re: cron rc=137
though the return code may not be predictable
I need to find out what command/program is
creating it
what do you recommend as a diagnostic means of
discovering what is generating the 137 return
code?
I need to find out what command/program is
creating it
what do you recommend as a diagnostic means of
discovering what is generating the 137 return
code?
so many toys, so little time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-28-2000 02:42 PM
тАО11-28-2000 02:42 PM
Re: cron rc=137
Hi William,
you need to share the information about your crontab file and your cron.log file to see which program was running.
You will most likely ending up with a problem with the application and/or program running at that time rather than a cron problem.
Please provide more info,
Steffi Jones
you need to share the information about your crontab file and your cron.log file to see which program was running.
You will most likely ending up with a problem with the application and/or program running at that time rather than a cron problem.
Please provide more info,
Steffi Jones
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP