Steps to reproduce:

1. Requires a Zabbix Server or Proxy with local PostgreSQL and PgBouncer instance.
2. Reboot or shut down the system.

Result:
PgBouncer is terminated before Zabbix Server or Proxy is shut down and the complete process is hanging infinitely.

A Stop Job is Running for Zabbix Server

A Stop Job is Running for Zabbix Proxy

Expected:
PgBouncer should also be considered and terminated after the Zabbix Server or Proxy has been shut down. If something speaks against it, perhaps a note in the documentation with the workaround would also be sufficient.

Workaround:

Add an override for Zabbix server or proxy.

systemctl edit zabbix-server.service

systemctl edit zabbix-proxy.service

Add following configuration.

[Unit]
After=pgbouncer.service

Reload systemd.

systemctl daemon-reload