7.4 Upgrade - GUI Reporting "Zabbix Server is not running" - But it is.

[tjh]

Hi,
I have just upgraded from 7.2 to 7.4 on my Debian 12 host - Debian 12, Mysql, php-fpm (8.2.28) and Apache2.

Everything appered to go fine as it has with previous Zabbix upgrades, but now on using the GUI I am met with the message "Zabbix Server is not running: the information displayed may not be currnet" along the bottom of the GUI.
However, the server is running. Checking the process list clearly shows the Zabbix Server running. There are valid logs (with no errors I can see) in /var/log/zabbix/zabbix_server.log
And most obviously, the data is updating in my Zabbix server - graphs are staying up to date, the Queue details page always has up to date information when I reload the page.

I've tried a different browser, I've tried clearing cache, I've tried restarting Zabbix Server, Zabbix Agent, php-fpm and Apache. All to no avail.

Previously on 7.2 I didn't have this error.

Can anyone provide me any pointers as to what Zabbix GUI is checking here to determine that the server isn't running? I've read the release notes etc, but I can't see anything obvious and I've diffed my zabbix_server.conf against zabbix_server.conf.dpkg-dist and I can't see any obvious missing setting etc.

Thanks!

[tjh]

I found this bug
The fix for me was to comment out

//$ZBX_SERVER = '192.168.0.253';
//$ZBX_SERVER_PORT = '10051';

in my /etc/zabbix/web/zabbix.conf.php file

Hope this helps someone else.

[tjh]

I should also point out alerting/alarming is working. So I am 100% sure the zabbix_server process is fine. It's something to do with how the check is performed that's not working.


469516:20250702:080741.837 Starting Zabbix Server. Zabbix 7.4.0 (revision 372a4e93c48).
469516:20250702:080741.837 ****** Enabled features ******
469516:20250702:080741.837 SNMP monitoring: YES
469516:20250702:080741.837 IPMI monitoring: YES
469516:20250702:080741.837 Web monitoring: YES
469516:20250702:080741.837 VMware monitoring: YES
469516:20250702:080741.837 SMTP authentication: YES
469516:20250702:080741.837 ODBC: YES
469516:20250702:080741.837 SSH support: YES
469516:20250702:080741.837 IPv6 support: YES
469516:20250702:080741.837 TLS support: YES
469516:20250702:080741.837 ******************************
469516:20250702:080741.837 using configuration file: /etc/zabbix/zabbix_server.conf
469516:20250702:080741.842 current database version (mandatory/optional): 07040000/07040000
469516:20250702:080741.842 required mandatory version: 07040000
469517:20250702:080741.844 starting HA manager
469517:20250702:080741.851 HA manager started in active mode
469516:20250702:080741.851 server #0 started [main process]
469518:20250702:080741.852 server #1 started [service manager #1]
469519:20250702:080741.853 server #2 started [configuration syncer #1]
469521:20250702:080742.068 server #3 started [alert manager #1]
469522:20250702:080742.069 server #4 started [alerter #1]
469523:20250702:080742.069 server #5 started [alerter #2]
469524:20250702:080742.070 server #6 started [alerter #3]
469525:20250702:080742.070 server #7 started [preprocessing manager #1]
469526:20250702:080742.071 server #8 started [lld manager #1]
469529:20250702:080742.074 server #11 started [housekeeper #1]
469527:20250702:080742.075 server #9 started [lld worker #1]
469528:20250702:080742.075 server #10 started [lld worker #2]
469530:20250702:080742.075 server #12 started [timer #1]
469531:20250702:080742.075 server #13 started [http poller #1]
469532:20250702:080742.076 server #14 started [http poller #2]
469533:20250702:080742.076 server #15 started [browser poller #1]
469534:20250702:080742.078 server #16 started [discovery manager #1]
469535:20250702:080742.087 server #17 started [history syncer #1]
469536:20250702:080742.089 server #18 started [history syncer #2]
469537:20250702:080742.090 server #19 started [history syncer #3]
469538:20250702:080742.090 server #20 started [history syncer #4]
469539:20250702:080742.095 server #21 started [escalator #1]
469542:20250702:080742.098 server #24 started [task manager #1]
469540:20250702:080742.098 server #22 started [proxy poller #1]
469525:20250702:080742.098 [1] thread started [preprocessing worker #1]
469525:20250702:080742.099 [2] thread started [preprocessing worker #2]
469525:20250702:080742.099 [3] thread started [preprocessing worker #3]
469525:20250702:080742.099 [4] thread started [preprocessing worker #4]
469525:20250702:080742.099 [5] thread started [preprocessing worker #5]
469525:20250702:080742.099 [6] thread started [preprocessing worker #6]
469525:20250702:080742.099 [7] thread started [preprocessing worker #7]
469525:20250702:080742.099 [8] thread started [preprocessing worker #8]
469525:20250702:080742.100 [11] thread started [preprocessing worker #11]
469541:20250702:080742.101 server #23 started [self-monitoring #1]
469544:20250702:080742.101 server #25 started [poller #1]
469525:20250702:080742.103 [9] thread started [preprocessing worker #9]
469525:20250702:080742.103 [10] thread started [preprocessing worker #10]
469525:20250702:080742.103 [12] thread started [preprocessing worker #12]
469525:20250702:080742.103 [13] thread started [preprocessing worker #13]
469525:20250702:080742.103 [14] thread started [preprocessing worker #14]
469525:20250702:080742.103 [15] thread started [preprocessing worker #15]
469525:20250702:080742.103 [16] thread started [preprocessing worker #16]
469560:20250702:080742.104 server #26 started [poller #2]
469561:20250702:080742.107 server #27 started [poller #3]
469562:20250702:080742.110 server #28 started [poller #4]
469564:20250702:080742.110 server #30 started [unreachable poller #1]
469563:20250702:080742.113 server #29 started [poller #5]
469565:20250702:080742.119 server #31 started [trapper #1]
469566:20250702:080742.120 server #32 started [trapper #2]
469567:20250702:080742.122 server #33 started [trapper #3]
469568:20250702:080742.124 server #34 started [trapper #4]
469576:20250702:080742.128 server #42 started [history poller #4]
469569:20250702:080742.128 server #35 started [trapper #5]
469570:20250702:080742.131 server #36 started [icmp pinger #1]
469571:20250702:080742.131 server #37 started [icmp pinger #2]
469572:20250702:080742.132 server #38 started [alert syncer #1]
469582:20250702:080742.132 server #48 started [agent poller #1]
469573:20250702:080742.132 server #39 started [history poller #1]
469582:20250702:080742.135 thread started
469584:20250702:080742.135 server #49 started [snmp poller #1]
469574:20250702:080742.135 server #40 started [history poller #2]
469585:20250702:080742.135 server #50 started [configuration syncer worker #1]
469586:20250702:080742.136 server #51 started [internal poller #1]
469577:20250702:080742.138 server #43 started [history poller #5]
469584:20250702:080742.139 thread started
469587:20250702:080742.139 server #52 started [proxy group manager #1]
469575:20250702:080742.139 server #41 started [history poller #3]
469578:20250702:080742.140 server #44 started [availability manager #1]
469579:20250702:080742.140 server #45 started [trigger housekeeper #1]
469580:20250702:080742.141 server #46 started [odbc poller #1]
469581:20250702:080742.143 server #47 started [http agent poller #1]
469581:20250702:080742.147 thread started
469534:20250702:080742.149 thread started [discovery worker #1]
469534:20250702:080742.149 thread started [discovery worker #2]
469534:20250702:080742.149 thread started [discovery worker #3]
469544:20250702:080747.108 forced reloading of the snmp cache on [poller #1]
469560:20250702:080747.111 forced reloading of the snmp cache on [poller #2]
469561:20250702:080747.114 forced reloading of the snmp cache on [poller #3]
469562:20250702:080747.117 forced reloading of the snmp cache on [poller #4]
469563:20250702:080747.120 forced reloading of the snmp cache on [poller #5]
469564:20250702:080747.122 forced reloading of the snmp cache on [unreachable poller #1]

That's my zabbix_server.log file contents.

[tjh]

I found this bug
The fix for me was to comment out

//$ZBX_SERVER = '192.168.0.253';
//$ZBX_SERVER_PORT = '10051';

in my /etc/zabbix/web/zabbix.conf.php file

Hope this helps someone else.

[eaterofcode]

Thank you very much, this worked for me.

[macdvd]

I believe I have this issue too... but my zabbix is running on containers, not sure how to apply this fix to that.
If I remove the env variables for the server... it wont know where the server is.. as in another container.

Any help appreciated

[macdvd]

Ah.... got it.... should have Read the "this bug" link more carefuly, I see all in needed to do was add the two env variables to the zabbix server container:

Saw AV's note re:

For docker installation add that parameters to zabbix/zabbix-server-mysql section (follow name of your container):

ZBX_NODEADDRESS=zabbix-server-mysql
ZBX_NODEADDRESSPORT=10051

Done and now fixed.

[mdx8]

Thank you very much, this worked for me.

[Firehead]

Thanks a lot! this worked for me as well!

[robertronq]

Thank you for this. This worked for me.

[omar.cacciotti]

[SOLVED]

My FE is still not working even by commenting out the two variables. If I disable the variables the FE is starting to use localhost but it's a different machine.



When I enable the two options, it still not working



Server, proxy and frontend are working properly.
Agents are working too



I had to setup the NodeAddress=IP:10051 on zabbix_server.conf

[Orisha Obatala]

I am experiencing the same issue. Please help if you have found a solution to this problem.

[Orisha Obatala]

I have the same issue, and the fixes here seem not to be working for me. This issue arises at random times, and the logs do not show any errors to suspect. What I am observing is that Zabbix might be restarting at this time, as I will be getting time difference triggers on the hosts that I am monitoring.

[BhumikaZabbix]

I have same issue and how to fixes it, we are installation fresh with Ubuntu with Mysql do what is the solution for it?