Ad Widget

Collapse

Zabbix 7.0.26 update on ubuntu 22.04

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • steingat
    Junior Member
    • May 2026
    • 3

    #1

    Zabbix 7.0.26 update on ubuntu 22.04

    Anyone else having issues with this build? Attempting to upgrade to it seems to kill the front end, either Apache2 service fails to start or PHP does not appear to function correctly.

    APT does throw one error. Was able to revert back to 7.0.25 via APT downgrade commands and that seemed to fix the issue, also reverted a snapshot back to two days ago, install all updates except zabbix, and then tried the zabbix update again, same results.

    Setting up zabbix-server-mysql (1:7.0.26-1+ubuntu22.04) ...
    Setting up zabbix-sql-scripts (1:7.0.26-1+ubuntu22.04) ...
    Setting up zabbix-frontend-php (1:7.0.26-1+ubuntu22.04) ...
    Setting up zabbix-agent (1:7.0.26-1+ubuntu22.04) ...
    Setting up zabbix-apache-conf (1:7.0.26-1+ubuntu22.04) ...
    Installing new version of config file /etc/zabbix/apache.conf ...
    realpath: '/etc/php/*/fpm/pool.d': No such file or directory
    Processing triggers for man-db (2.10.2-1) ...
    Log ended: 2026-05-05 20:32:24
  • elpengo
    Junior Member
    • May 2026
    • 1

    #2
    Hello,

    I had mostly the same issue on debian 13 as the frontend url shows php sources and figured out that the package in cause seems to be zabbix-apache-conf 7.0.26.

    The package await a php-fpm installation and not a "classic" apache with mod_php (MPM Prefork) while installing its own conf file /etc/apache2/conf-available/zabbix.conf
    Code:
    <FilesMatch \.(php|phar)$>
            SetHandler "proxy:unix:/var/run/php/zabbix.sock|fcgi://localhost"
    </FilesMatch>​
    If you have your own vhost configuration to serve zabbix frontend, disabling the zabbix package configuration via this apache command fix the problem :
    Code:
    a2disconf zabbix && systemctl reload apache2

    Comment

    • svbuser
      Junior Member
      • May 2026
      • 1

      #3
      my solution was

      a2enmod proxy
      a2enmod proxy_fcgi
      apt install php8.1-fpm
      nano /etc/apache2/conf-enabled/zabbix.conf
      systemctl restart apache2​

      in zabbix.conf

      -- proxy:unix:/var/run/php/zabbix.sock|fcgi://localhost
      ++ proxy:unix:/var/run/php/php8.1-fpm.sock|fcgi://localhost

      Comment

      • Antimidas
        Junior Member
        • May 2026
        • 7

        #4
        I have had nothing but problems with the upgrade of just the front-end to 7.0.26 on Ubuntu 22.04.5 LTS. I was able to restore prior snapshots on the Nutanix which got me back. I have three front-end servers running in HA mode along wiht three Zabbix Server installations in cluster with pacemaker/corosync and three DB servers with a master/slave round robin. svbuser - Do you just have just one server, or multiple? Can you confirm your fix worked to get it running?

        With the HA enabled, I have a feeling I will need to set up a test environment before moving to this version. Otherwise, I will need to wait and hope a later version fixes this issue. I really don't look forward to rebuilding all 9 servers for something that appears to be a small issue triggering the problem with a minor version update.

        Comment

        • bebe
          Junior Member
          • Jan 2014
          • 6

          #5
          "just" installing php-fpm is not a real fix and could break other web-sites running on this apache2 instance, so be careful.
          The same issue applies to 7.4.10. 7.4.9 was ok.

          There were significant changes in the file /etc/zabbix/apache.conf which were not mentioned in the upgrade notes and are breaking existing installations.
          Last edited by bebe; Yesterday, 16:49.

          Comment

          • Antimidas
            Junior Member
            • May 2026
            • 7

            #6
            bebe - Do you have a documented process of what needs to be configured in the /etc/zabbix/apache.conf file to make it work? Or would it be best to set up a test box with 7.0.26 and do a file compare between the two iterations? Seems like a lot of work for what is supposed to be a minor update. I wish the release notes would have mentioned all of the changes -- especially since they affect the configuration files and installation of php_fpm instead of mod_php. That seems like a dramatic change that should be documented somewhere.

            Comment

            • bebe
              Junior Member
              • Jan 2014
              • 6

              #7
              I think this is a bug and was not intended.
              You could revert the content of the file and take the content from the previous version. Just extract the content of the .deb files to get the differences.

              URLs:

              Zabbix 7.0 - Ubuntu 22.04 packages:
              last working version: https://repo.zabbix.com/zabbix/7.0/u...u22.04_all.deb
              newest (NOT working): https://repo.zabbix.com/zabbix/7.0/u...u22.04_all.deb

              Zabbix 7.0 - Ubuntu 24.04 packages:
              last working version: https://repo.zabbix.com/zabbix/7.0/u...u24.04_all.deb
              newest (NOT working): https://repo.zabbix.com/zabbix/7.0/u...u24.04_all.deb

              Zabbix 7.4 - Ubuntu 22.04 packages
              last working version: https://repo.zabbix.com/zabbix/7.4/s...u22.04_all.deb
              newest (NOT working): https://repo.zabbix.com/zabbix/7.4/s...u22.04_all.deb

              Zabbix 7.4 - Ubuntu 24.04 packages
              last working version: https://repo.zabbix.com/zabbix/7.4/s...u24.04_all.deb
              newest (NOT working): https://repo.zabbix.com/zabbix/7.4/s...u24.04_all.deb

              Comment

              • Antimidas
                Junior Member
                • May 2026
                • 7

                #8
                Since it is an LTS release, I am hoping that the devs notice that people are having issues and get a patch published sooner than they would on the bleeding edge releases. I think I will turn off my automated maintenance plan and stick with 70.25 rather than spending a lot of time digging in to it.

                Thanks for the pointers and assistance, however. It is very much appreciated. If I have a chance after my weekend maintenance (and they have not yet fixed it), I might spend next week building out a test-bed since the boss is on vacation for a couple of weeks.

                Comment

                • steingat
                  Junior Member
                  • May 2026
                  • 3

                  #9
                  Originally posted by svbuser
                  my solution was

                  a2enmod proxy
                  a2enmod proxy_fcgi
                  apt install php8.1-fpm
                  nano /etc/apache2/conf-enabled/zabbix.conf
                  systemctl restart apache2

                  in zabbix.conf

                  -- proxy:unix:/var/run/php/zabbix.sock|fcgi://localhost
                  ++ proxy:unix:/var/run/php/php8.1-fpm.sock|fcgi://localhost
                  Ya, that is what i suspected as php8.1-fpm was not installed for me either. I missed the Zabbix.conf portion. Thank you. However, I think i will wait for the next patch incase this change breaks things moving forward.

                  Comment

                  • steingat
                    Junior Member
                    • May 2026
                    • 3

                    #10
                    Looks like someone has reported the problem as a bug.

                    Comment

                    • sperkins74
                      Junior Member
                      • May 2026
                      • 4

                      #11
                      hello

                      I reported this in a another section for zabbix 7 + debian 13

                      Commenting out the below is "good enough" and from i read here should be quite ok

                      /etc/zabbixapache.conf

                      ProxyTimeout 300

                      and

                      <FilesMatch \.(php|phar)$>
                      SetHandler "proxy:unix:/var/run/php/zabbix.sock|fcgi://localhost"
                      </FilesMatch>

                      and restart apache2

                      Comment

                      • sperkins74
                        Junior Member
                        • May 2026
                        • 4

                        #12
                        I also experienced odd php config errors on the dashboard, i have found the pre change zabbix.conf which explains that too

                        here it is

                        # Define /zabbix alias, this is the default
                        <IfModule mod_alias.c>
                        Alias /zabbix /usr/share/zabbix
                        </IfModule>

                        <Directory "/usr/share/zabbix">
                        Options FollowSymLinks
                        AllowOverride None
                        Order allow,deny
                        Allow from all

                        <IfModule mod_php.c>
                        php_value max_execution_time 300
                        php_value memory_limit 128M
                        php_value post_max_size 16M
                        php_value upload_max_filesize 2M
                        php_value max_input_time 300
                        php_value max_input_vars 10000
                        php_value always_populate_raw_post_data -1
                        </IfModule>

                        <IfModule mod_php7.c>
                        php_value max_execution_time 300
                        php_value memory_limit 128M
                        php_value post_max_size 16M
                        php_value upload_max_filesize 2M
                        php_value max_input_time 300
                        php_value max_input_vars 10000
                        php_value always_populate_raw_post_data -1
                        </IfModule>
                        </Directory>

                        <Directory "/usr/share/zabbix/conf">
                        Order deny,allow
                        Deny from all
                        <files *.php>
                        Order deny,allow
                        Deny from all
                        </files>
                        </Directory>

                        <Directory "/usr/share/zabbix/app">
                        Order deny,allow
                        Deny from all
                        <files *.php>
                        Order deny,allow
                        Deny from all
                        </files>
                        </Directory>

                        <Directory "/usr/share/zabbix/include">
                        Order deny,allow
                        Deny from all
                        <files *.php>
                        Order deny,allow
                        Deny from all
                        </files>
                        </Directory>

                        <Directory "/usr/share/zabbix/local">
                        Order deny,allow
                        Deny from all
                        <files *.php>
                        Order deny,allow
                        Deny from all
                        </files>
                        </Directory>

                        <Directory "/usr/share/zabbix/vendor">
                        Order deny,allow
                        Deny from all
                        <files *.php>
                        Order deny,allow
                        Deny from all
                        </files>
                        </Directory>

                        Comment


                        • Antimidas
                          Antimidas commented
                          Editing a comment
                          Thanks for that. I copied my zabbix.conf files to .orig and then performed the update to 7.0.26. I then copied the .orig files back over the .conf files. There was no need for me to comment out the lines in the apache.conf. Everythign appears to be working properly through pacemaker/corosync. I have not rebooted the servers, but I did not need to last time for the site to fail. It appears to be working.

                        • Antimidas
                          Antimidas commented
                          Editing a comment
                          Nevermind. That broke things again. Back to waiting for a permanent fix.
                      Working...