Linux Error 137
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow
Exit Code 137 Java
the company Business Learn more about hiring developers or posting ads with us Stack docker exit code 137 Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of
Docker Exited With Code 137
6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up My server exited with code 137 up vote -1 down vote favorite I wrote a C++ server/client linux exit codes pair using C++11, boost::asio and HDF5. The server was running fine for a some time (2 days), and then it stopped with code 137. Since I executed the server with an infinite loop, it was restarted. Unfortunately, my error logs don't provide sufficient information to understand the problem. So I've been trying to understand what this code means. It seems there's consensus that this means it's an error of 128+9, with 9 docker exit 137 meaning that the program was killed with kill -9. Now I'm not sure at all why this happened. I need help to find out. By reading further, I found out that it could have been killed by the system because it exceeded a certain allowed execution time, and thus the system killed it. Now this is not so unlikely, since my linux server is provided by my university, so they could be applying some kind of security to do this. I read about something called timeout in linux. My first question is: How can I know if this is the cause of the problem? My second question is: what should I check also to understand this problem? What would you do? Please advise. If you require any additional information, please ask. Thanks. c++ linux boost-asio exit-code error-code share|improve this question edited Oct 21 '15 at 11:22 asked Jul 27 '15 at 17:46 The Quantum Physicist 3,42822156 The exit status is eight bits, so it can be 0 to 255 (inclusive). What 137 means could be anything. My guess it's either HDF5 or some other external library (except Boost, which usually throws exceptions instead) that call exit on certain error conditions. –Joachim Pileborg Jul 27 '15 at 17:56 Also see stackoverflow.com/questions/11801783/resolv
>ExampleComments1Catchall for general errorslet "var1 = 1/0"Miscellaneous errors, such as "divide by zero" and other impermissible operations2Misuse of shell builtins (according to Bash documentation)empty_function() {}
C++ Exit Code 137
>Missing keyword or command, or permission problem (and diff return code on exit status 137 npm a failed binary file comparison).126Command invoked cannot execute/dev/nullPermission problem or command is not an executable
Exit Code 137 Python
>127"command not found"illegal_commandPossible problem with $PATH or a typo128Invalid argument to exitexit 3.14159exit takes only integer args in the range 0 - http://stackoverflow.com/questions/31659840/my-server-exited-with-code-137 255 (see first footnote)128+nFatal error signal "n"kill -9 $PPID of script$? returns 137 (128 + 9)130Script terminated by Control-CCtl-CControl-C is fatal error signal 2, (130 = 128 + 2, see above)255*Exit status out of rangeexit -1exit takes only integer args in the range 0 http://tldp.org/LDP/abs/html/exitcodes.html - 255
and Memory Discuss NAS, SAN, RAID, Robotic Libraries, backup devices, RAM, DRAM, SCSI, IDE, EIDE topics here. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... linux operating commands and unix operating http://www.unix.com/filesystems-disks-and-memory/6820-exit-code-137-backup.html commands Exit code 137 on a backup Filesystems, Disks and Memory https://github.com/npm/npm/issues/4008 Thread Tools Search this Thread Display Modes #1 06-25-2002 twins Registered User Join Date: Jun 2002 Last Activity: 16 July 2002, 3:55 PM EDT Posts: 2 Thanks: 0 Thanked 0 Times in 0 Posts Exit code 137 on a backup Can some one tell me what it means to get a exit code od 137 from a cron scheduled backup exit code on HP-UX. Also if you know of a book that has the HP-UX codes that would be great. Thanks Remove advertisements Sponsored Links twins View Public Profile Find all posts by twins #2 07-16-2002 rene_metaal Registered User Join Date: Jul 2002 Last Activity: 3 August 2014, 5:28 AM EDT Posts: 27 Thanks: 0 Thanked 1 Time in 1 Post Backup on HP-UX: err 137 From the man page of fbackup: (no 137) RETURN VALUE fbackup returns one of the exit code 137 following values: 0 upon normal completion. 1 if it is interrupted but allowed to save its state for possible restart. 2 if any error conditions prevent the session from completing. 4 if any warning conditions are encountered. If warnings occur, the operator should check the fbackup logs to verify the sanity of the backup. ============= But normally there is some more text or a message in the /var/adm/syslog/syslog.log file. Does the command run from the command line? What version of HP-UX is it and what are you running? Cheers Rene Remove advertisements Sponsored Links rene_metaal View Public Profile Visit rene_metaal's homepage! Find all posts by rene_metaal #3 06-19-2007 hill_0613 Registered User Join Date: Jun 2007 Last Activity: 20 June 2007, 1:58 AM EDT Posts: 1 Thanks: 0 Thanked 0 Times in 0 Posts Process under HP-UX was killed with return code 137 One process in HP-UX was killed for unknown reason, but our application shell caught the return code 137. Do you know why it's killed? It should not be killed by someone manually, we can see it from the return code. Thanks! hill_0613 View Public Profile Find all posts by hill_0613 #4 06-19-2007 porter Registered User Join Date: Jan 2007 Last Activity: 8 January 2008, 6:50 PM EST Posts: 2,965 Thanks: 0 Thanked 5 Times in 5 Posts Quote: Originally Posted by hill_0613 One process in HP-UX was killed for unknown reason, but our applic
Sign in Pricing Blog Support Search GitHub This repository Watch 613 Star 10,708 Fork 2,188 npm/npm Code Issues 2,385 Pull requests 70 Projects 0 Wiki Pulse Graphs New issue npm ERR! weird error 137 #4008 Closed richb-hanover opened this Issue Oct 17, 2013 · 10 comments Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 5 participants richb-hanover commented Oct 17, 2013 Folks, I hope this is the right place to ask this question about an error message that I think is coming from node.js. I am using npm version 1.3.11 on a Ubuntu 10.04 VPS with limited RAM. I have installed ghost (http://ghost.org) according to the directions. It seems to work OK for the most part. But sometimes it stops on its own, and displays the "weird error 137" message, without any activity from a client. (see terminal session below.) Any ideas what might be causing it? What other information could I provide? Many thanks. Rich Brown Hanover, NH USA richb@myhost:~/ghost$ npm start > ghost@0.3.2 start /home/richb/ghost > node index Ghost is running... Listening on 0.0.0.0:2368 Url configured as: http://myhost.com:2368 Ctrl+C to shut down ... it runs a while, then says... Killed npm ERR! weird error 137 npm ERR! not ok code 0 richb@myhost:~/ghost$ luk- commented Oct 17, 2013 The program is exiting or crashing with an exit code that npm doesn't recognize, which is why you see "weird error". It's not specifically an npm error, but the output isn't super helpful. … On Thursday, October 17, 2013, richb-hanover wrote: Folks, I hope this is the right place to ask this question about an error message that I think is coming from node.js. I am using npm version 1.3.11 on a Ubuntu 10.04 VPS with limited RAM. I have installed ghost (http://ghost.org) according to the directions. It seems to work OK for the most part. But sometimes it stops on its own, and displays the "weird error 137" message, without any activity from a client. (see terminal session below.) Any ideas what might be causing it? What other information could I provide? Many thanks. Rich Brown Hanover, NH USA ***@***.***:~/ghost$ npm start > ***@***.*** start /home/richb/ghost > node index Ghost is running... Listening on 0.0.0.0:2368 Url configured as: http://myhost.com:2368 Ctrl+C to shut down ... it runs a while, then says... Killed npm ERR! weird error 137 npm ERR! not ok code 0 ***@***.***:~/ghost$ — R