In the company I am working now there is a legacy service and its init script is using old SysvInit, but is running over systemd (CentOS 7).
Because there's a lot of computation, this service takes around 70 seconds to finish. I didn't configure any timeout for systemd, and didn't change the default configs at
/etc/systemd/system.conf, but still when I execute
service SERVICE stop my service is timing out after 60 seconds.
journalctl -b -u SERVICE.service I find this log:
Sep 02 11:27:46 service.hostname systemd: Stopping LSB: Start/Stop Sep 02 11:28:46 service.hostname SERVICE: Stopping service: Error code: 255 Sep 02 11:28:46 service.hostname SERVICE: [FAILED]
I already tried changing the
DefaultTimeoutStopSec property at
90s, but the timeout still happens.
Does anyone have any idea why is it timeouting at 60s? Is there somewhere else that this timeout value is configured? Is there a way I can check it?
This service runs with java 7 and to daemonize it, it uses JSVC. I configured the
-wait parameter with the value