Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Zabbix2-proxy-2.0.8 pkg v0.7_1 on Netgate does not work, reference missing files

    Scheduled Pinned Locked Moved pfSense Packages
    4 Posts 1 Posters 1.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      ahull
      last edited by

      So I'm pretty sure I did this to myself. I'm hoping to get some advice on how to proceed from here.

      I migrated a white box pfSense 2.1 build to an Alix 2d13 with the Netgate 2.1 release. I use Zabbix for monitoring, and had the Agent and the Proxy installed on the white box.

      After the migration, I'm getting the zabbix packages re-installed and I notice that they won't start.

      It looks like pfSense package repository has Zabbix2 packages up to zabbix2-agent-2.2.1 pkg v0.8_0 and zabbix2-proxy-2.2.1 pkg v0.8_0, but the Netgate release limits them to zabbix2-agent-2.0.8 pkg v0.7_1 and zabbix2-proxy-2.0.8 pkg v0.7_1.  There must have been some holdover 2.2 stuff in there, because my /usb/pbi directory has both 2 and 2.2 directories in it:

      [2.1p1-RELEASE][admin@pfsense]/usr/pbi(24): ls -la /usr/pbi | grep zabbix
      drwxr-xr-x  13 root  wheel     512 Feb 15 08:49 zabbix2-agent-i386
      drwxr-xr-x  13 root  wheel     512 Feb 15 08:42 zabbix2-proxy-i386
      drwxr-xr-x   3 root  operator  512 Feb 14 15:56 zabbix22-proxy-i386
      
      

      and the startup scripts point to files in 22 that only exist in 2:

      [2.1p1-RELEASE][admin@pfsense]/usr/local/etc/rc.d(30): ./zabbix2_proxy.sh start
      Starting Zabbix Proxy...
      ./zabbix2_proxy.sh: /usr/pbi/zabbix22-proxy-i386/sbin/zabbix_proxy: not found
      [2.1p1-RELEASE][admin@pfsense]/usr/local/etc/rc.d(31): ./zabbix2_agentd.sh start
      Starting Zabbix Agent...
      ./zabbix2_agentd.sh: /usr/pbi/zabbix22-agent-i386/sbin/zabbix_agentd: not found
      
      

      Both of the referenced files exist in the zabbix2-xxxxx-i386 directories.

      I've uninstalled both packages the the /usr/pbi/zabbix22-proxy-i386 remains, and the /usr/pbi/zabbix22-agent-i386 directly is never created. Re-installing the packages yields the same results.

      Is there something I can do to to get this cleaned out short of wiping the config and starting from scratch?

      Thanks,
      Andy

      1 Reply Last reply Reply Quote 0
      • A
        ahull
        last edited by

        Update:

        -I uninstalled both packages

        • switched file system to RW
        • removed the /usr/pbi/zabbix22-proxy-i386 directory
        • switched fs back to ro
        • installed zabbix2-proxy package

        and the zabbix22-proxy-i386 and zabbix2-proxy-i386 directories were both re-created. Same issue running the startup script as I posted above.

        Is there a PBI command that I can use to flush a cache or something?

        1 Reply Last reply Reply Quote 0
        • A
          ahull
          last edited by

          Alright, now I'm confidant I did NOT do this to myself.

          I just did a nuke-and-pave of this device. Reimaged the flash card (netgate - 2.1p1-RELEASE (i386)), performed re-config from scratch, and installed the latest available zabbix2-proxy (zabbix2-proxy-2.0.8 pkg v0.7_1).

          There is a mix of zabbix2-proxy-i386 and zabbix22-proxy-i386 directories in /usr/pbi and the launch script references a file that does not exist.

          [2.1p1-RELEASE][root@pfsense.localdomain]/usr/local/etc/rc.d(33): cat zabbix2_proxy.sh
          #!/bin/sh
          # This file was automatically generated
          # by the pfSense service handler.
          
          rc_start() {
                  if [ ! -d /var/log/zabbix2 ]
           then
           /bin/mkdir -p /var/log/zabbix2
           /usr/sbin/chmod 755 /var/log/zabbix2
           fi
          /usr/sbin/chown -R zabbix:zabbix /var/log/zabbix2
          
          if [ ! -d /var/run/zabbix2 ]
           then
           /bin/mkdir -p /var/run/zabbix2
           /usr/sbin/chmod 755 /var/run/zabbix2
           fi
          /usr/sbin/chown -R zabbix:zabbix /var/run/zabbix2
          
          if [ ! -d /var/db/zabbix2 ]
           then
           /bin/mkdir -p /var/db/zabbix2
           /usr/sbin/chmod 755 /var/db/zabbix2
           fi
          /usr/sbin/chown -R zabbix:zabbix /var/db/zabbix2
          
          echo "Starting Zabbix Proxy"...
          /usr/pbi/zabbix22-proxy-i386/sbin/zabbix_proxy # <----------------------------------- this is in /usr/pbi/zabbix2-proxy......
          
          }
          
          rc_stop() {
                  echo "Stopping Zabbix Proxy"
          /usr/bin/killall zabbix_proxy
          /bin/sleep 5
          
          }
          
          case $1 in
                  start)
                          rc_start
                          ;;
                  stop)
                          rc_stop
                          ;;
                  restart)
                          rc_stop
                          rc_start
                          ;;
          esac
          
          

          Does anyone know what's going on here?

          1 Reply Last reply Reply Quote 0
          • A
            ahull
            last edited by

            It has to do with how the Netgate release of pfSense seems to be limiting the Zabbix2 packages to the 2.0.x branch.

            Perhaps the init scripts are not versioned or something. Installing the zabbix2-proxy-2.0.8 pkg v0.7_1 package but pulling the init script that has been updated for zabbix2-proxy-2.2.1 pkg v0.8_0.

            I know the Netgate release package repository lags behind a little, perhaps I can help get the zabbix2.2 updates fully tested so they can be released to the Netgate release.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.