Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-25816

Proxy 7.2 fails to open a SQLite3 file

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • None
    • 7.2.0, 7.2.1
    • Proxy (P)
    • OS Oracle Linux 9.5
      Zabbix Proxy 7.2.0/1

      I've just upgraded a Zabbix Proxy instance from 7.0 to 7.2 on a OS Oracle Linux 9.5.

      The application upgrade was successful, but when I tried to start the Proxy, it failed because it won't start the SQLite3 database file.

      Here's the error:

      SystemCTL:

       

      $ sudo systemctl start zabbix-proxy.service
      Job for zabbix-proxy.service failed because the service did not take the steps required by its unit configuration.
      See "systemctl status zabbix-proxy.service" and "journalctl -xeu zabbix-proxy.service" for details.

       

      Zabbix Proxy log:

       

      42656:20241231:121203.761 Starting Zabbix Proxy (active) [pxl1sgs00021]. Zabbix 7.2.1 (revision 67f3c838b2a).
       42656:20241231:121203.761 **** Enabled features ****
       42656:20241231:121203.761 SNMP monitoring:       YES
       42656:20241231:121203.761 IPMI monitoring:       YES
       42656:20241231:121203.761 Web monitoring:        YES
       42656:20241231:121203.761 VMware monitoring:     YES
       42656:20241231:121203.761 ODBC:                  YES
       42656:20241231:121203.761 SSH support:           YES
       42656:20241231:121203.761 IPv6 support:          YES
       42656:20241231:121203.761 TLS support:           YES
       42656:20241231:121203.761 **************************
       42656:20241231:121203.761 using configuration file: /etc/zabbix/zabbix_proxy.conf
       42656:20241231:121203.762 cannot open database file "/var/lib/zabbix/zabbix_proxy.db": [2] No such file or directory
       42656:20241231:121203.762 creating database ...
       42656:20241231:121203.762 [Z3001] connection to database '/var/lib/zabbix/zabbix_proxy.db' failed: [0] unable to open database file
       42656:20241231:121203.762 cannot initialize database: cannot open database

       

      JournalCTL:

       

       The job identifier is 2174.
      Dec 31 12:06:58 [HOST] systemd[1]: zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted
      Dec 31 12:06:58 [HOST] systemd[1]: zabbix-proxy.service: Failed with result 'protocol'.
       Subject: Unit failed
       Defined-By: systemd
       The unit zabbix-proxy.service has entered the 'failed' state with result 'protocol'.
      Dec 31 12:06:58 [HOST] systemd[1]: Failed to start Zabbix Proxy.
       Subject: A start job for unit zabbix-proxy.service has failed
      

       

      Here's the main Zabbix Proxy configuration file:

       

      Server=[ZABBIX SERVER]
      Hostname=[HOSTNAME]
      LogFile=/var/log/zabbix/zabbix_proxy.log
      LogFileSize=10
      PidFile=/run/zabbix/zabbix_proxy.pid
      SocketDir=/run/zabbix
      DBName=/var/lib/zabbix/zabbix_proxy.db
      DBUser=zabbix
      ProxyOfflineBuffer=720
      ProxyBufferMode=hybrid
      ProxyMemoryBufferSize=16M
      SNMPTrapperFile=/var/log/snmptrap/snmptrap.log
      Timeout=4
      LogSlowQueries=3000
      Include=/etc/zabbix/zabbix_proxy.conf.d/*.conf
      Include=/etc/zabbix/zabbix_proxy.d/*.conf
      StatsAllowedIP=127.0.0.1

       

      The "/var/lib/zabbix" directory is owned by the Zabbix user and should be writable by the Proxy.

      $ ls -lahd /var/lib/zabbix
      drwxr-xr-x 2 zabbix zabbix 6 Dec 31 11:49 /var/lib/zabbix

      I've enable debug log, but it didn't show anything meaningful.
      So, I'm not sure why the Proxy won't start the SQLite3 file.

      I've also tried a fresh install of the Proxy 7.2, but it also failed.

      Version 7.0 works, but not 7.2

      Please, any thoughts?

            Unassigned Unassigned
            markfree MArk
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: