Ad Widget

Collapse

zabbix proxy 6.0.3 and 6.2 startup problems with pid file

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • trta
    Junior Member
    • Jul 2010
    • 18

    #1

    zabbix proxy 6.0.3 and 6.2 startup problems with pid file

    I'm tried to run newest zabbix-proxy on Debian 11 (up to date) from oficial zabbix repo and also directly from .deb. Always service cannot start because missing pid file. Also I try to make file by hand and set proper permissions (chown zabbix:zabbix, chmod 644, also chmod 774) but systemctl start zabbix-proxy hang on and won't start the service properly.
    Is this some bug in version 6 or how can I solve this please?
  • Answer selected by trta at 12-09-2022, 09:40.
    tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    If you're seeing a message from systemctl status or journalctl about a PID file not yet being present, that's likely not the underlying cause for whatever problem is preventing the proxy from starting. The real problem is somewhere else.

    That message about the PID file is a problem, but it's a very minor one, and it's present for many otherwise-working deployments.

    Look in the proxy log file to see if there are any messages about what the true problem is.

    Comment

    • tim.mooney
      Senior Member
      • Dec 2012
      • 1427

      #2
      If you're seeing a message from systemctl status or journalctl about a PID file not yet being present, that's likely not the underlying cause for whatever problem is preventing the proxy from starting. The real problem is somewhere else.

      That message about the PID file is a problem, but it's a very minor one, and it's present for many otherwise-working deployments.

      Look in the proxy log file to see if there are any messages about what the true problem is.

      Comment

      • trta
        Junior Member
        • Jul 2010
        • 18

        #3
        thank you, the problem was with unsupported db version (we install mariadb from their repo) , so set
        Code:
        AllowUnsupportedDBVersions=1
        in zabbix conf solve my problem. Thank you :-)

        Originally posted by tim.mooney
        If you're seeing a message from systemctl status or journalctl about a PID file not yet being present, that's likely not the underlying cause for whatever problem is preventing the proxy from starting. The real problem is somewhere else.

        That message about the PID file is a problem, but it's a very minor one, and it's present for many otherwise-working deployments.

        Look in the proxy log file to see if there are any messages about what the true problem is.

        Comment

        Working...