Ubuntu packages: systemd has "no limit" on the zabbix-server stop

[elyograg]

I rebooted my server today for a kernel update. Ubuntu 22.04, x86_64. During the shutdown, it was stopping services, but when it got to zabbix-server, it had no stop timeout. About the time it was saying "7m XXs/no limit" I got tired of waiting and power-cycled the server.

In /etc/systemd/system.conf I set the default stop limit to 300 seconds a few reboots ago, and ran "systemctl daemon-reload" but that appears to have had no effect on the zabbix-server service. The service file does not have any override for the stop timeout, so I am confused about why the stop had no time limit. I have not modified the .service files. Version info below:

elyograg@smeagol:~$ dpkg -l | grep zabbix | awk '{print $2, $3, $4}'
zabbix-agent2 1:6.4.0~rc1-1+ubuntu22.04 amd64
zabbix-apache-conf 1:6.4.0~rc1-1+ubuntu22.04 all
zabbix-frontend-php 1:6.4.0~rc1-1+ubuntu22.04 all
zabbix-get 1:6.4.0~rc1-1+ubuntu22.04 amd64
zabbix-js 1:6.4.0~rc1-1+ubuntu22.04 amd64
zabbix-release 1:6.3-3+ubuntu22.04 all
zabbix-sender 1:6.4.0~rc1-1+ubuntu22.04 amd64
zabbix-server-mysql 1:6.4.0~rc1-1+ubuntu22.04 amd64
zabbix-sql-scripts 1:6.4.0~rc1-1+ubuntu22.04 all
zabbix-web-service 1:6.4.0~rc1-1+ubuntu22.04 amd64
​

[tcweb]

Hi elyograg,

Did you ever find an answer? I am seeing the same behavior. I just ran systemctl edit zabbix-server, and added a line to set the timeout to 300s. I'd rather not wait until it happens again.
It seems as if it's related to the speed of mysql starting, as it did not start to happen until mysql hit about 70GB.

-TC