Ad Widget

Collapse

Zabbix server is not running: the information displayed may not be current.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dion
    Junior Member
    • Mar 2024
    • 7

    #1

    Zabbix server is not running: the information displayed may not be current.

    Hey everyone,

    I'm reaching out for some assistance from our community!

    I've successfully installed Zabbix via the GUI, and all prechecks passed without any issues. However, I'm encountering a problem where I can't seem to load any data into Zabbix. It's giving me a warning that the Zabbix server isn't running, but here's the twist: it seems to be running just fine (at least according to rockyos services), and I've exhausted all my options!

    Here are some details:
    • Operating System: Rocky Linux release 9.3 (Blue Onyx)
    • SELinux: Disabled
    • SQL: MariaDB permissions checked; ensured that user 'zabbix' has all necessary privileges, and logging in with the credentials provided in the server_config works fine.
    • PHP: Verified PHP settings and added an IP and port.
    • Firewall: Firewalld is turned off for testing purposes, but unfortunately, it didn't resolve the issue.
    The 'zabbix_server.conf' file includes all the necessary configurations, such as DB host (localhost), DB password (user password), and DB user (zabbix).
    Here's the output of a few MySQL queries:

    MariaDB [(none)]> SHOW GRANTS FOR 'zabbix'@'localhost';
    +---------------------------------------------------------------------------------------------------------------+ | Grants for zabbix@localhost | +---------------------------------------------------------------------------------------------------------------+ |
    GRANT USAGE ON *.* TO `zabbix`@`localhost` IDENTIFIED BY PASSWORD '*CA42378B56924608F36A61C1A0CE10437F66F82F' | | GRANT ALL PRIVILEGES ON `zabbix`.* TO `zabbix`@`localhost` | +---------------------------------------------------------------------------------------------------------------+ 2 rows in set (0.000 sec)




    MariaDB [(none)]> SHOW DATABASES;
    +--------------------+ | Database | +--------------------+ | information_schema | | mysql | | performance_schema | | zabbix | +--------------------+ 4 rows in set (0.002 sec) MariaDB [(none)]>



    MariaDB [(none)]> USE zabbix;
    Reading table information for completion of table and column names
    You can turn off this feature to get a quicker startup with -A

    Database changed
    MariaDB [zabbix]>
    MariaDB [zabbix]> SHOW TABLES;
    +----------------------------+
    | Tables_in_zabbix |
    +----------------------------+
    | acknowledges |
    | actions |
    | alerts |
    | auditlog |
    | autoreg_host |
    | conditions |
    | config |
    | config_autoreg_tls |
    | corr_condition |
    | corr_condition_group |
    | corr_condition_tag |
    | corr_condition_tagpair |
    | corr_condition_tagvalue |
    | corr_operation |
    | correlation |
    | dashboard |
    | dashboard_page |
    | dashboard_user |
    | dashboard_usrgrp |
    | dbversion |
    | dchecks |
    | dhosts |
    | drules |
    | dservices |
    | escalations |
    | event_recovery |
    | event_suppress |
    | event_tag |
    | events |
    | expressions |
    | functions |
    | globalmacro |
    | globalvars |
    | graph_discovery |
    | graph_theme |
    | graphs |
    | graphs_items |
    | group_discovery |
    | group_prototype |
    | ha_node |
    | history |
    | history_log |
    | history_str |
    | history_text |
    | history_uint |
    | host_discovery |
    | host_inventory |
    | host_tag |
    | hostmacro |
    | hosts |
    | hosts_groups |
    | hosts_templates |
    | housekeeper |
    | hstgrp |
    | httpstep |
    | httpstep_field |
    | httpstepitem |
    | httptest |
    | httptest_field |
    | httptest_tag |
    | httptestitem |
    | icon_map |
    | icon_mapping |
    | ids |
    | images |
    | interface |
    | interface_discovery |
    | interface_snmp |
    | item_condition |
    | item_discovery |
    | item_parameter |
    | item_preproc |
    | item_rtdata |
    | item_tag |
    | items |
    | lld_macro_path |
    | lld_override |
    | lld_override_condition |
    | lld_override_opdiscover |
    | lld_override_operation |
    | lld_override_ophistory |
    | lld_override_opinventory |
    | lld_override_opperiod |
    | lld_override_opseverity |
    | lld_override_opstatus |
    | lld_override_optag |
    | lld_override_optemplate |
    | lld_override_optrends |
    | maintenance_tag |
    | maintenances |
    | maintenances_groups |
    | maintenances_hosts |
    | maintenances_windows |
    | media |
    | media_type |
    | media_type_message |
    | media_type_param |
    | module |
    | opcommand |
    | opcommand_grp |
    | opcommand_hst |
    | opconditions |
    | operations |
    | opgroup |
    | opinventory |
    | opmessage |
    | opmessage_grp |
    | opmessage_usr |
    | optemplate |
    | problem |
    | problem_tag |
    | profiles |
    | proxy_autoreg_host |
    | proxy_dhistory |
    | proxy_history |
    | regexps |
    | report |
    | report_param |
    | report_user |
    | report_usrgrp |
    | rights |
    | role |
    | role_rule |
    | script_param |
    | scripts |
    | service_alarms |
    | service_problem |
    | service_problem_tag |
    | service_status_rule |
    | service_tag |
    | services |
    | services_links |
    | sessions |
    | sla |
    | sla_excluded_downtime |
    | sla_schedule |
    | sla_service_tag |
    | sysmap_element_trigger |
    | sysmap_element_url |
    | sysmap_shape |
    | sysmap_url |
    | sysmap_user |
    | sysmap_usrgrp |
    | sysmaps |
    | sysmaps_element_tag |
    | sysmaps_elements |
    | sysmaps_link_triggers |
    | sysmaps_links |
    | tag_filter |
    | task |
    | task_acknowledge |
    | task_check_now |
    | task_close_problem |
    | task_data |
    | task_remote_command |
    | task_remote_command_result |
    | task_result |
    | timeperiods |
    | token |
    | trends |
    | trends_uint |
    | trigger_depends |
    | trigger_discovery |
    | trigger_queue |
    | trigger_tag |
    | triggers |
    | users |
    | users_groups |
    | usrgrp |
    | valuemap |
    | valuemap_mapping |
    | widget |
    | widget_field |
    +----------------------------+
    173 rows in set (0.001 sec)

    MariaDB [zabbix]>


    I've checked various tables in the 'zabbix' database, and everything seems to be in order. Do i miss tables, or just overseeing a simple problem?
    Any help or insights would be greatly appreciated! Thanks in advance for your support."
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    GUI has a feature, that it checks servers 10051 port to determine is it running or not. if it cannot connect to it, it will display a "server is not running" error on a webpage...
    "systemctl status zabbix-server" says everything is OK and running?

    Comment


    • Mugugnu
      Mugugnu commented
      Editing a comment
      I'd like to be sure about this: is the check of zabbix server port 10051 performed by the web server and then the browser reports it, so it is basically saying: "web server cannot reach zabbix server"  or is the check performed by the browser thati is reporting that it cannot connect to the zabbix server ?
  • Dion
    Junior Member
    • Mar 2024
    • 7

    #3
    Hi cyber,

    yes with “systemctl status zabbix-server” i can see it is running fine, and i turned of firewalld, so i don’t think it can be a port issue.

    thanks for the help!

    kind regards,
    Dion

    Comment

    • Dion
      Junior Member
      • Mar 2024
      • 7

      #4
      ● zabbix-server.service - Zabbix Server
      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; preset: disabled)
      Active: active (running) since Sun 2024-03-17 21:12:08 CET; 19h ago
      Process: 1056 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
      Main PID: 1080 (zabbix_server)
      Tasks: 1 (limit: 22772)
      Memory: 9.2M
      CPU: 1.128s
      CGroup: /system.slice/zabbix-server.service
      └─1080 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

      Mar 17 21:12:07 zabbix systemd[1]: Starting Zabbix Server...
      Mar 17 21:12:08 zabbix systemd[1]: Started Zabbix Server.
      [dion@zabbix ~]$ systemctl status firewalld
      ○ firewalld.service - firewalld - dynamic firewall daemon
      Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; preset: enabled)
      Active: inactive (dead)
      Docs: man:firewalld(1)
      [dion@zabbix ~]$

      Comment

      • Dion
        Junior Member
        • Mar 2024
        • 7

        #5
        i think i see the problem, but the weird thing is that my config seems okay and the permissions are all granted. I can also login with those credentials in mysql/mariadb.

        [dion@zabbix ~]$ cat /var/log/zabbix/zabbix_server.log

        1080:20240318:164132.913 database is down: reconnecting in 10 seconds
        1080:20240318:164142.914 [Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: YES)
        1080:20240318:164142.914 database is down: reconnecting in 10 seconds
        [dion@zabbix ~]$

        Comment

        • Dion
          Junior Member
          • Mar 2024
          • 7

          #6
          Hm, i can’t find the issue. I rebuilded the db, but didn’t work. Could someone help me out?

          Comment

          • vinicius.ropke
            Junior Member
            • Apr 2024
            • 2

            #7
            Hello,

            I have the same problem. I'm running zabbix server 6.4.12 on Oracle 19 with Redhat Enterprise 8.9 servers.

            I have exhausted all possibilities for analysis. apparently it seems that something is getting stuck, as the use of trapper increases at the moment that the communication says it is OFF and it is not. Att,

            Comment

            • vinicius.ropke
              Junior Member
              • Apr 2024
              • 2

              #8

              Atualizei para a versão 6.4.14 e o resultado de erro mudou;
              O Zabbix Server continua funcionando normalmente, parece ser algo com os fontes PHP.
              Attached Files

              Comment

              • Mugugnu
                Junior Member
                • Dec 2020
                • 10

                #9
                Originally posted by cyber
                GUI has a feature, that it checks servers 10051 port to determine is it running or not. if it cannot connect to it, it will display a "server is not running" error on a webpage...
                "systemctl status zabbix-server" says everything is OK and running?
                Hi, can you explain "GUI has a feature "?
                I mean: is the check of server port 10051 performed by the web server and then the browser reports it, so it is basically saying: "web server cannot reach zabbix server" or is the check performed by the browser (which i don't believe..) ?

                Comment

                • Dion
                  Junior Member
                  • Mar 2024
                  • 7

                  #10
                  Found the issue. I missed a lot of packages, because the apt-get command only installed the first package of the command i used from the zabbix manual. I have zabbix running currently. Make sure to check if you installed all packages by doing them 1 by 1.

                  Comment

                  • masterguru
                    Junior Member
                    • Sep 2024
                    • 1

                    #11
                    Well, in my case the problem was related to /etc/zabbix/zabbix_server.conf that was overwrriten by the update (it asked and I selected to overwritte it). And the old one was saved as zabbix_server.conf.dpkg-old. And in the old one it has a line with the zabbix DB password in this parameter:

                    DBPassword=xxxxxxxxxx

                    that was missing in the updated /etc/zabbix/zabbix_server.conf, so I added the missing line with the DBPassword and all was running well again after a zabbix-server restart. I am using Debian 12.

                    Comment

                    • AndreasM
                      Junior Member
                      • Jul 2024
                      • 2

                      #12
                      Had the same issue, but in addition to the DBPassword I also had to activate Cachesize again in the zabbix_server.conf. Remove the # and restore the value, in my case: Cachesize=128M

                      Comment

                      • cyber
                        Senior Member
                        Zabbix Certified SpecialistZabbix Certified Professional
                        • Dec 2006
                        • 4807

                        #13
                        Originally posted by Mugugnu

                        Hi, can you explain "GUI has a feature "?
                        I mean: is the check of server port 10051 performed by the web server and then the browser reports it, so it is basically saying: "web server cannot reach zabbix server" or is the check performed by the browser (which i don't believe..) ?
                        Its webserver, not your browser...

                        Originally posted by AndreasM
                        Had the same issue, but in addition to the DBPassword I also had to activate Cachesize again in the zabbix_server.conf. Remove the # and restore the value, in my case: Cachesize=128M
                        if it is there with a comment, it is just using default value, which is pretty small, I think... 32M, IIRC But it has nothing to do with DB connection ...
                        Last edited by cyber; 26-09-2024, 15:09.

                        Comment

                        • AndreasM
                          Junior Member
                          • Jul 2024
                          • 2

                          #14
                          Originally posted by cyber

                          Its webserver, not your browser...


                          if it is there with a comment, it is just using default value, which is pretty small, I think... 32M, IIRC But it has nothing to do with DB connection ...
                          I noticed now that the main problem is that every value in the zabbix_server.conf was reset to default after the latest update, which wasn't the case with previous updates.

                          Comment

                          Working...