Quantcast
Channel: Active questions tagged crash - Stack Overflow
Viewing all articles
Browse latest Browse all 7193

Ubuntu service stops randomly with "Main Process exited, status 143/n/a"

$
0
0

My apps deployed as debians and started using systemd service.The app is getting crashed randomly. I am unable to find the reason for the crash.

I have 4 applications running[built using java, scala], out of which two are getting killed(named as op and common). All are started using systemd services.

Error on syslog is

Jul 22 11:45:44 misqa mosquitto[2930]: Socket error on client 005056b76983-Common, disconnecting

Jul 22 11:45:44 misqa systemd[1]: commonmod.service: Main process exited, code=exited, status=143/n/a

Jul 22 11:45:44 misqa systemd[1]: commonmod.service: Unit entered failed state

Jul 22 11:45:44 misqa systemd[1]: commonmod.service: Failed with result 'exit-code'

Jul 22 11:45:44 misqa systemd[1]: opmod.service: Main process exited, code=exited, status=143/n/a

Jul 22 11:45:44 misqa systemd[1]: opmod.service: Unit entered failed state

Jul 22 11:45:44 misqa systemd[1]: opmod.service: Failed with result'exit-code'

But I am not getting any error on my application log file for both op and common

When I read more, I understood that the reason for crash is due to SIGTERM command, but unable to find out what is causing it. In any of these applications, I dont have exec commands for killall.

Is there anyway to identify which process is killing my applications.

My systemd service is like this:

[Unit]Description=common ModuleAfter=common-apiRequires=common-api[Service]TimeoutStartSec=0ExecStart=/usr/bin/common-api[Install]WantedBy=multi-user.target

Viewing all articles
Browse latest Browse all 7193

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>