附:退出码说明.

Exit Code Number	Meaning	Example	Comments
1	Catchall for general errors	let “var1 = 1/0”	Miscellaneous errors, such as “divide by zero” and other impermissible operations
2	Misuse of shell builtins (according to Bash documentation)	empty_function() {}	Missing keyword or command, or permission problem (and diff return code on a failed binary file comparison).
126	Command invoked cannot execute	/dev/null	Permission problem or command is not an executable
127	“command not found”	illegal_command	Possible problem with $PATH or a typo
128	Invalid argument to exit	exit 3.14159	exit takes only integer args in the range 0 - 255 (see first footnote)
128+n	Fatal error signal “n”	kill -9 $PPID of script	$? returns 137 (128 + 9)
130	Script terminated by Control-C	Ctl-C	Control-C is fatal error signal 2, (130 = 128 + 2, see above)
255*	Exit status out of range	exit -1	exit takes only integer args in the range 0 - 255

退出代码137(128 + 9)表示您的进程被（信号9）SIGKILL终止。
如果您没有手动停止脚本并仍然得到此错误代码，且脚本将被您的操作系统终止。在大多数情况下，这是由于过度使用内存造成的。

附: linux退出码

Process Exit Codes

When invoking a unit process the service manager possibly fails to apply the execution parameters configured with the settings above. In that case the already created service process will exit with a non-zero exit code before the configured command line is executed. (Or in other words, the child process possibly exits with these error codes, after having been created by the fork(2) system call, but before the matching execve(2) system call is called.) Specifically, exit codes defined by the C library, by the LSB specification and by the systemd service manager itself are used.

The following basic service exit codes are defined by the C library.

Table 6. Basic C library exit codes

Exit Code	Symbolic Name	Description
0	EXIT_SUCCESS	Generic success code.
1	EXIT_FAILURE	Generic failure or unspecified error.

The following service exit codes are defined by the LSB specification.

Table 7. LSB service exit codes

Exit Code	Symbolic Name	Description
2	EXIT_INVALIDARGUMENT	Invalid or excess arguments.
3	EXIT_NOTIMPLEMENTED	Unimplemented feature.
4	EXIT_NOPERMISSION	The user has insufficient privileges.
5	EXIT_NOTINSTALLED	The program is not installed.
6	EXIT_NOTCONFIGURED	The program is not configured.
7	EXIT_NOTRUNNING	The program is not running.

The LSB specification suggests that error codes 200 and above are reserved for implementations. Some of them are used by the service manager to indicate problems during process invocation:

Table 8. systemd-specific exit codes

Exit Code	Symbolic Name	Description
200	EXIT_CHDIR	Changing to the requested working directory failed. See WorkingDirectory= above.
201	EXIT_NICE	Failed to set up process scheduling priority (nice level). See Nice= above.
202	EXIT_FDS	Failed to close unwanted file descriptors, or to adjust passed file descriptors.
203	EXIT_EXEC	The actual process execution failed (specifically, the execve(2) system call). Most likely this is caused by a missing or non-accessible executable file.
204	EXIT_MEMORY	Failed to perform an action due to memory shortage.
205	EXIT_LIMITS	Failed to adjust resource limits. See LimitCPU= and related settings above.
206	EXIT_OOM_ADJUST	Failed to adjust the OOM setting. See OOMScoreAdjust= above.
207	EXIT_SIGNAL_MASK	Failed to set process signal mask.
208	EXIT_STDIN	Failed to set up standard input. See StandardInput= above.
209	EXIT_STDOUT	Failed to set up standard output. See StandardOutput= above.
210	EXIT_CHROOT	Failed to change root directory (chroot(2)). See RootDirectory=/RootImage= above.
211	EXIT_IOPRIO	Failed to set up IO scheduling priority. See IOSchedulingClass=/IOSchedulingPriority= above.
212	EXIT_TIMERSLACK	Failed to set up timer slack. See TimerSlackNSec= above.
213	EXIT_SECUREBITS	Failed to set process secure bits. See SecureBits= above.
214	EXIT_SETSCHEDULER	Failed to set up CPU scheduling. See CPUSchedulingPolicy=/CPUSchedulingPriority= above.
215	EXIT_CPUAFFINITY	Failed to set up CPU affinity. See CPUAffinity= above.
216	EXIT_GROUP	Failed to determine or change group credentials. See Group=/SupplementaryGroups= above.
217	EXIT_USER	Failed to determine or change user credentials, or to set up user namespacing. See User=/PrivateUsers= above.
218	EXIT_CAPABILITIES	Failed to drop capabilities, or apply ambient capabilities. See CapabilityBoundingSet=/AmbientCapabilities= above.
219	EXIT_CGROUP	Setting up the service control group failed.
220	EXIT_SETSID	Failed to create new process session.
221	EXIT_CONFIRM	Execution has been cancelled by the user. See the systemd.confirm_spawn= kernel command line setting on kernel-command-line(7) for details.
222	EXIT_STDERR	Failed to set up standard error output. See StandardError= above.
224	EXIT_PAM	Failed to set up PAM session. See PAMName= above.
225	EXIT_NETWORK	Failed to set up network namespacing. See PrivateNetwork= above.
226	EXIT_NAMESPACE	Failed to set up mount, UTS, or IPC namespacing. See ReadOnlyPaths=, ProtectHostname=, PrivateIPC=, and related settings above.
227	EXIT_NO_NEW_PRIVILEGES	Failed to disable new privileges. See NoNewPrivileges=yes above.
228	EXIT_SECCOMP	Failed to apply system call filters. See SystemCallFilter= and related settings above.
229	EXIT_SELINUX_CONTEXT	Determining or changing SELinux context failed. See SELinuxContext= above.
230	EXIT_PERSONALITY	Failed to set up an execution domain (personality). See Personality= above.
231	EXIT_APPARMOR_PROFILE	Failed to prepare changing AppArmor profile. See AppArmorProfile= above.
232	EXIT_ADDRESS_FAMILIES	Failed to restrict address families. See RestrictAddressFamilies= above.
233	EXIT_RUNTIME_DIRECTORY	Setting up runtime directory failed. See RuntimeDirectory= and related settings above.
235	EXIT_CHOWN	Failed to adjust socket ownership. Used for socket units only.
236	EXIT_SMACK_PROCESS_LABEL	Failed to set SMACK label. See SmackProcessLabel= above.
237	EXIT_KEYRING	Failed to set up kernel keyring.
238	EXIT_STATE_DIRECTORY	Failed to set up unit’s state directory. See StateDirectory= above.
239	EXIT_CACHE_DIRECTORY	Failed to set up unit’s cache directory. See CacheDirectory= above.
240	EXIT_LOGS_DIRECTORY	Failed to set up unit’s logging directory. See LogsDirectory= above.
241	EXIT_CONFIGURATION_DIRECTORY	Failed to set up unit’s configuration directory. See ConfigurationDirectory= above.
242	EXIT_NUMA_POLICY	Failed to set up unit’s NUMA memory policy. See NUMAPolicy= and NUMAMask= above.
243	EXIT_CREDENTIALS	Failed to set up unit’s credentials. See LoadCredential= and SetCredential= above.

Finally, the BSD operating systems define a set of exit codes, typically defined on Linux systems too:

Table 9. BSD exit codes

Exit Code	Symbolic Name	Description
64	EX_USAGE	Command line usage error
65	EX_DATAERR	Data format error
66	EX_NOINPUT	Cannot open input
67	EX_NOUSER	Addressee unknown
68	EX_NOHOST	Host name unknown
69	EX_UNAVAILABLE	Service unavailable
70	EX_SOFTWARE	internal software error
71	EX_OSERR	System error (e.g., can’t fork)
72	EX_OSFILE	Critical OS file missing
73	EX_CANTCREAT	Can’t create (user) output file
74	EX_IOERR	Input/output error
75	EX_TEMPFAIL	Temporary failure; user is invited to retry
76	EX_PROTOCOL	Remote error in protocol
77	EX_NOPERM	Permission denied
78	EX_CONFIG	Configuration error

综合资料查找判断,exit value 137 为内存不足导致的系统自动kill脚本的执行. exit value 247未查找到足够资料,根据查找的资料基本判断业务内存问题. 调整pod的分配的内存后,脚本顺利执行,未再出现异常.

记一次Process.waitFor()的exit value返回137,247的问题相关推荐

1. 记一次Process finished with exit code 1 项目异常

   一.环境 自己是nacos注册的微服务项目,而且所有代码都是经过测试进行git提交. 今天将代码clone下来进行新手教程文档的编写 但是自己怎么都跑不起来,就很无语,如果不是怀揣着自己对测试代码的信 ...

2. Java Process.waitFor() 阻塞卡住不返回

   1. 现象 在Java程序中,启动另一个进程执行一个命令时可以使用ProcessBuilder类启动一个进程. 以运行 ps 命令为例: ProcessBuilder processBuilder = ...

3. java执行python返回null_[转]java调用python脚本以及通过Process.waitFor()直接调用python模块返回错误代码1的一种解决办法...

   常见的java调用python脚本方式 通过jython提供的类库实现 通过Runtime.getRuntime()开启进程来执行脚本文件 通过jython提供的类库实现 通过jython实现的话,我 ...

4. Process finished with exit code 143

   跑一个深度学习模型 第一次运行出现Process finished with exit code 137 之后再运行均出现Process finished with exit code 143 137 ...

5. 记解决pycharm报错 Process finished with exit code -1073741819 (0xC0000005)

   最近在做一个抢单项目: python项目莫名出现:Process finished with exit code -1073741819 (0xC0000005),程序没执行结束退出! . 网上找了好 ...

6. 为Process.waitFor设置超时

   2019独角兽企业重金招聘Python工程师标准>>> Java中在使用Runtime.getRuntime().exec(command)调用系统命令后 一般会调用Process. ...

7. 解决报错Process finished with exit code -1073741571 (0xC00000FD),修改栈大小

   运行程序时程序意外终止,并返回提示: Process finished with exit code -1073741571 (0xC00000FD) 导致的原因是StackOverflow(栈区溢出 ...

8. java 使用Process调用exe程序 及 Process.waitFor() 死锁问题了解和解决

   前言 最近在开发android的同时也在开发java ,碰到了需要使用java 程序调用exe的需求,这里我使用的 process 来调用的.该篇文章 读完需要8+分钟,文章类型为 小白入门类型,此处 ...

9. python Process finished with exit code -1073741819 (0xC0000005) 解决

   运行程序时,Process finished with exit code -1073741819 (0xC0000005) 报错 原因:没有 python33.dll 在 c:\WINDOWS\sy ...

10. Process finished with exit code -1073741819 (0xC0000005)

    Process finished with exit code -1073741819 (0xC0000005) pycharm报错:Process finished with exit code - ...

最新文章

1. 树哈希判断同构无根同构问题转有根同构问题
2. TCP/IP网络编程之基于TCP的服务端/客户端（二）
3. bootstrap登录表单
4. can总线报文是固定的吗_CAN总线传输协议
5. aes算法c语言实现_C语言实现常用数据结构：Dijkstra最短路径算法（第18篇）
6. 拦截器CacheInterceptor
7. 2016蓝桥杯C++A：剪邮票（抓取法）
8. 数值分析(3)-多项式插值: 牛顿插值法
9. yolov4训练自己的数据 灰度图像_还在为图像训练数据少发愁吗？那是因为你还不会这几招...
10. 7、创建ROS msg和srv
11. 计算机二级C语言考试题库软件
12. 【QT学习之路】Charts的简单使用
13. nero免费中文版内含注册激活码获取器
14. 修改tomcat版本号解决eclipse中tomcat版本不对应
15. 怎么禁用笔记本的键盘
16. Coursera | Introduction to Data Science in Python（University of Michigan）| Assignment4
17. 谷歌的seo原理是什么
18. NEON指令优化指南学习之一
19. 学籍管理系统源代码java_java学籍管理系统完整版.zip
20. 微信小程序利用git提交项目

热门文章

1. 汽车维修企业管理【2】
2. C语言条件运算符详解
3. mysql netbeans_使用Netbeans操作MySQL数据库
4. Python实现股票涨跌预测——随机森林模型
5. three.js学习笔记(十四)——Shaders着色器
6. Ceph分布式存储详解
7. amoeba mysql proxy_mysql-proxy和amoeba 分别实现Mariadb读写分离
8. 應用高解析度線掃描CCD於ITO導電玻璃表面瑕疵檢測之研究
9. appium自动注册完整脚本
10. Stata：各类盈余管理指标估算方法