Read more
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- Touch command return code 137
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
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
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
Touch command return code 137
SOLVED- 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
03-16-2011 06:28 AM
03-16-2011 06:28 AM
This may sound like a very stupid question but I just can't find the answer. I have a touch command that runs at certain intervals. The problem is that every now and then, the touch fails and it exits with 137. I have no clue what 137 means, and I, unfortunately, cannot reproduce at will, thus my dilemma to get an answer for this problem.
Can you help please?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2011 06:33 AM
03-16-2011 06:33 AM
Re: Touch command return code 137
Re: Touch command return code 137
well the man page for touch is non-specific, simply stating any non-zero value is an error... it might help if you showed us the code snippet where you exectute the touch and get its return code... maybe some error in the script?
HTH
Duncan
HTH
Duncan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2011 06:38 AM
03-16-2011 06:38 AM
Re: Touch command return code 137
Re: Touch command return code 137
It's actually not a script.. it a command that we run from within OVO but the command looks like this :
node=<$MSG_NODE_NAME>;touch /var/opt/OV/share/tmp/OpC/hbm/msg/$(echo ${node%%.*} | tr [A-Z] [a-z])
and as I said, this command is executed several times and works 99% of the times.. and it is not one node in particular. It just "happens"
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-16-2011 11:02 AM
03-16-2011 11:02 AM
SolutionYou got signal 9, SIGKILL. So does some rogue sysadmin or script automation have it out for you? :-)
I've heard that sometimes the kernel will kill you with signal 9 but that is in low memory cases and I'm not sure why touch would need that much.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-22-2011 07:16 AM
03-22-2011 07:16 AM
Re: Touch command return code 137
Re: Touch command return code 137
The reason I'm asking is I'm wondering if too many touch are happening at the same time because this is a scheduled process. Since you talked about low memory.. I doubt the memory is running low but I wonder if the kernel is having an issue handling so many touch at the same time. And since the problem is intermittent, sometimes just a few microseconds is good enough to process them all.. but other times not.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-25-2011 03:57 PM
03-25-2011 03:57 PM
Re: Touch command return code 137
Re: Touch command return code 137
If you are creating files in a directory, you can only do one at a time. But this is synchronized by locks.
>I'm wondering if too many touch are happening at the same time because this is a scheduled process.
Are you talking about 1000s?
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP