[RESOLVED] Chef server 12.16.9 systemctl stop private_chef-runsvdir-start failed

Chef Infra (archive)
1

Dear sir/madam,

I installed chef servcer 12.16.9, but I found a problem when I stop chef server by running the following command:
root> systemctl stop private_chef-runsvdir-start
And the status is:
systemctl status private_chef-runsvdir-start

● private_chef-runsvdir-start.service - private_chef Runit Process Supervisor
Loaded: loaded (/etc/systemd/system/private_chef-runsvdir-start.service; disabled; vendor preset: disabled)
Active: failed (Result: timeout) since Mon 2017-09-04 14:10:24 CST; 3min 28s ago
Main PID: 3839 (code=exited, status=0/SUCCESS)

Sep 04 13:48:16 systemd[1]: Started Cluster Controlled private_chef-runsvdir-start.
Sep 04 13:48:16 systemd[1]: Starting Cluster Controlled private_chef-runsvdir-start…
Sep 04 13:48:26 oc_bifrost[4886]: Starting up
Sep 04 14:08:54 systemd[1]: Stopping private_chef Runit Process Supervisor…
Sep 04 14:10:24 systemd[1]: private_chef-runsvdir-start.service stop-final-sigterm timed out. Killing.
Sep 04 14:10:24 systemd[1]: Stopped private_chef Runit Process Supervisor.
Sep 04 14:10:24 systemd[1]: Unit private_chef-runsvdir-start.service entered failed state.
Sep 04 14:10:24 systemd[1]: private_chef-runsvdir-start.service failed.

But I found version 12.11.1 do not have this kind of problem.

Anyone can help me? Thanks!

Br,
Samuel

2

You shouldn’t ever be stopping chef-server in that fashion as chef-server manages it’s own services and chef-server-ctl should be used in all cases as per documentation. I can’t say why that would have worked in the past or doesn’t work now but as I said, that shouldn’t be a think you’re managing yourself directly through systemctl.

Cheers,

3

Thanks. According to your comments, I added ExecStop=/usr/bin/chef-server-ctl stop in the private_chef-runsvdir-start.service. This helps me to shutdown the service quickly.