Ad Widget

Collapse

First time frontend run failed

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Nehemoth
    Junior Member
    • Apr 2020
    • 8
    #1

    First time frontend run failed

    I just finished installing Zabbix on Centos. Everything wen't just fine after troubleshooting an issue when you import initial DB schema and data (long story short I was passing the password instead of the db name in my command).

    When I try to reach my server http://My.Server.IP/zabbix I received a 404 error
    also the same think happen when I ran elinks http://localhost/zabbix

    Could it be a php or apache issue?

    SE has been disable
    Zabbix server it's running just fine.
    Configured the /etc/zabbix/zabbix_server.conf file with the bellow parameters

    DBHost=MY Server IP
    DBName=zabbix_DB_Name
    DBUser=zabbix_User_Name
    DBPassword=Zabbix_DB_Password
    PidFile=/var/run/zabbix/zabbix_server.pid

    I checked that the DB was created, that I can connect with the created user and password, that was populated with the tables.
    I'd configure that the httpd, zabbix server et al and mariadb ran when the system start
    I created the necessary rules for the firewall BUT I also stopped the firewall to see if that was the issue (it was not).

    modified the /etc/php-fpm.d/zabbix.conf file with the below information

    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
    php_value[date.timezone] = America/Santo_Domingo

    commented this line php_value[always_populate_raw_post_data] = -1 and restarted the server to see if that was the problem, it was not.


    Below there's a bunch of info that are usually request for troubleshooting.


    I would like to know what should I'll look



    Regards


    Code:
    [root@ALAPROZABBIX01 ~]# systemctl status zabbix-server.service
● zabbix-server.service - Zabbix Server
   Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2020-04-02 08:37:40 AST; 1h 48min ago
  Process: 2696 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCCESS)
 Main PID: 2725 (zabbix_server)
    Tasks: 38 (limit: 52428)
   Memory: 64.9M
   CGroup: /system.slice/zabbix-server.service
           ├─2725 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
           ├─2771 /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.075428 sec, idle 60 sec]
           ├─2783 /usr/sbin/zabbix_server: housekeeper [deleted 30 hist/trends, 0 items/triggers, 0 events, 0 sessions, 0 alarms, 0 audit items, 0 records in 0.007942 sec, idle for 1 hour(s)]
           ├─2784 /usr/sbin/zabbix_server: timer #1 [updated 0 hosts, suppressed 0 events in 0.000714 sec, idle 59 sec]
           ├─2785 /usr/sbin/zabbix_server: http poller #1 [got 0 values in 0.000754 sec, idle 5 sec]
           ├─2787 /usr/sbin/zabbix_server: discoverer #1 [processed 0 rules in 0.000730 sec, idle 60 sec]
           ├─2788 /usr/sbin/zabbix_server: history syncer #1 [processed 0 values, 0 triggers in 0.000036 sec, idle 1 sec]
           ├─2790 /usr/sbin/zabbix_server: history syncer #2 [processed 0 values, 0 triggers in 0.000037 sec, idle 1 sec]
           ├─2792 /usr/sbin/zabbix_server: history syncer #3 [processed 0 values, 0 triggers in 0.000032 sec, idle 1 sec]
           ├─2793 /usr/sbin/zabbix_server: history syncer #4 [processed 2 values, 0 triggers in 0.001252 sec, idle 1 sec]
           ├─2795 /usr/sbin/zabbix_server: escalator #1 [processed 0 escalations in 0.001385 sec, idle 3 sec]
           ├─2797 /usr/sbin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000032 sec, idle 5 sec]
           ├─2798 /usr/sbin/zabbix_server: self-monitoring [processed data in 0.000031 sec, idle 1 sec]
           ├─2800 /usr/sbin/zabbix_server: task manager [processed 0 task(s) in 0.000422 sec, idle 5 sec]
           ├─2802 /usr/sbin/zabbix_server: poller #1 [got 0 values in 0.000032 sec, idle 1 sec]
           ├─2803 /usr/sbin/zabbix_server: poller #2 [got 1 values in 0.000620 sec, idle 1 sec]
           ├─2804 /usr/sbin/zabbix_server: poller #3 [got 0 values in 0.000032 sec, idle 1 sec]
           ├─2805 /usr/sbin/zabbix_server: poller #4 [got 0 values in 0.000037 sec, idle 1 sec]
           ├─2806 /usr/sbin/zabbix_server: poller #5 [got 1 values in 0.000553 sec, idle 1 sec]
           ├─2807 /usr/sbin/zabbix_server: unreachable poller #1 [got 0 values in 0.000033 sec, idle 5 sec]
           ├─2808 /usr/sbin/zabbix_server: trapper #1 [processed data in 0.002949 sec, waiting for connection]
           ├─2809 /usr/sbin/zabbix_server: trapper #2 [processed data in 0.003049 sec, waiting for connection]
           ├─2810 /usr/sbin/zabbix_server: trapper #3 [processed data in 0.002727 sec, waiting for connection]
           ├─2811 /usr/sbin/zabbix_server: trapper #4 [processed data in 0.002673 sec, waiting for connection]
           ├─2812 /usr/sbin/zabbix_server: trapper #5 [processed data in 0.002821 sec, waiting for connection]
           ├─2813 /usr/sbin/zabbix_server: icmp pinger #1 [got 0 values in 0.000028 sec, idle 5 sec]
           ├─2815 /usr/sbin/zabbix_server: alert manager #1 [sent 0, failed 0 alerts, idle 5.005388 sec during 5.005543 sec]
           ├─2816 /usr/sbin/zabbix_server: alerter #1 started
           ├─2818 /usr/sbin/zabbix_server: alerter #2 started
           ├─2825 /usr/sbin/zabbix_server: alerter #3 started
           ├─2826 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 0, processed 10 values, idle 5.001734 sec during 5.002124 sec]
           ├─2827 /usr/sbin/zabbix_server: preprocessing worker #1 started
           ├─2828 /usr/sbin/zabbix_server: preprocessing worker #2 started
           ├─2829 /usr/sbin/zabbix_server: preprocessing worker #3 started
           ├─2830 /usr/sbin/zabbix_server: lld manager #1 [processed 0 LLD rules during 5.005442 sec]
           ├─2831 /usr/sbin/zabbix_server: lld worker #1 [processed 1 LLD rules, idle 3598.230783 sec during 3598.250600 sec]
           ├─2832 /usr/sbin/zabbix_server: lld worker #2 [processed 1 LLD rules, idle 1705.477273 sec during 1705.508158 sec]
           └─2835 /usr/sbin/zabbix_server: alert syncer [queued 0 alerts(s), flushed 0 result(s) in 0.000957 sec, idle 1 sec]
    Code:
    # journalctl -xn
-- Logs begin at Thu 2020-04-02 08:37:28 AST, end at Thu 2020-04-02 10:37:38 AST. --
Apr 02 10:29:49 ALAPROZABBIX01.Domain.name systemd[1]: Stopping Zabbix Server...
-- Subject: Unit zabbix-server.service has begun shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun shutting down.
Apr 02 10:29:49 ALAPROZABBIX01.Domain.name systemd[1]: Stopped Zabbix Server.
-- Subject: Unit zabbix-server.service has finished shutting down
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished shutting down.
Apr 02 10:29:49 ALAPROZABBIX01.Domain.name systemd[1]: Starting Zabbix Server...
-- Subject: Unit zabbix-server.service has begun start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has begun starting up.
Apr 02 10:29:49 ALAPROZABBIX01.Domain.name systemd[1]: zabbix-server.service: Supervising process 6007 which is not our child. We'll most likely not notice when it exits.
Apr 02 10:29:49 ALAPROZABBIX01.Domain.name systemd[1]: Started Zabbix Server.
-- Subject: Unit zabbix-server.service has finished start-up
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- Unit zabbix-server.service has finished starting up.
--
-- The start-up result is RESULT.
Apr 02 10:37:01 ALAPROZABBIX01.Domain.name systemd[1]: Reloading.
Apr 02 10:37:14 ALAPROZABBIX01.Domain.name systemd[1]: Reloading.
Apr 02 10:37:27 ALAPROZABBIX01.Domain.name systemd[1]: Reloading.
Apr 02 10:37:33 ALAPROZABBIX01.Domain.name systemd[1]: Reloading.
Apr 02 10:37:38 ALAPROZABBIX01.Domain.name systemd[1]: Reloading.
    Code:
    ● zabbix-agent.service - Zabbix Agent
   Loaded: loaded (/usr/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2020-04-02 10:50:31 AST; 7min ago
  Process: 6162 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=0/SUCCESS)
  Process: 6170 ExecStart=/usr/sbin/zabbix_agentd -c $CONFFILE (code=exited, status=0/SUCCESS)
 Main PID: 6172 (zabbix_agentd)
    Tasks: 6 (limit: 52428)
   Memory: 5.6M
   CGroup: /system.slice/zabbix-agent.service
           ├─6172 /usr/sbin/zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf
           ├─6173 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
           ├─6174 /usr/sbin/zabbix_agentd: listener #1 [waiting for connection]
           ├─6175 /usr/sbin/zabbix_agentd: listener #2 [waiting for connection]
           ├─6176 /usr/sbin/zabbix_agentd: listener #3 [waiting for connection]
           └─6177 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]

Apr 02 10:50:31 ALAPROZABBIX01.Domain.name systemd[1]: Starting Zabbix Agent...
Apr 02 10:50:31 ALAPROZABBIX01.Domain.name systemd[1]: zabbix-agent.service: Can't open PID file /run/zabbix/zabbix_agentd.pid (yet?) after start: No such file or directory
Apr 02 10:50:31 ALAPROZABBIX01.Domain.name systemd[1]: zabbix-agent.service: Supervising process 6172 which is not our child. We'll most likely not notice when it exits.
Apr 02 10:50:31 ALAPROZABBIX01.Domain.name systemd[1]: Started Zabbix Agent.
    Code:
    [root@ALAPROZABBIX01 ~]# more /run/zabbix/zabbix_agentd.pid
6172
[root@ALAPROZABBIX01 ~]# more /var/run/zabbix/zabbix_agentd.pid
6172
    Last edited by Nehemoth; 02-04-2020, 17:25.
    Tags: None
    • tim.mooney
      Senior Member
      • Dec 2012
      • 1427
      #2
      Thanks for including all the detail that you did.

      It appears that zabbix-server is running just fine, it's just that the web-based front end is not working. That's (mostly) independent of the zabbix-server process, and depends more on your web server and PHP.

      In your case, because it's the web server that is returning a 404 error, I would look at your web server logs and also potentially your PHP logs, if you have any. The problem is most likely with your web server configuration. Make certain that you've followed the "Zabbix frontend configuration" section of the installation guide for your OS/distro. The PHP settings are just one part of that. You must also configure your web server to correctly serve PHP pages from your install location. See the docs for more information on that.

        Comment

        • Nehemoth
          Junior Member
          • Apr 2020
          • 8
          #3
          Originally posted by tim.mooney
          Thanks for including all the detail that you did.

          It appears that zabbix-server is running just fine, it's just that the web-based front end is not working. That's (mostly) independent of the zabbix-server process, and depends more on your web server and PHP.

          In your case, because it's the web server that is returning a 404 error, I would look at your web server logs and also potentially your PHP logs, if you have any. The problem is most likely with your web server configuration. Make certain that you've followed the "Zabbix frontend configuration" section of the installation guide for your OS/distro. The PHP settings are just one part of that. You must also configure your web server to correctly serve PHP pages from your install location. See the docs for more information on that.
          That was my initial assessment too.
          As I indeed followed the documentation that's why I did not understood why this was happening.

          Searching online I found out someone talking about changing a path inside the /etc/httpd/conf.d/zabbix.conf file
          Again it did not work BUT it looks like was something related to the httpd service, this because while don't the changes in the above file I had to restart the service several times after one of those restart, zabbix came back to life.
          Go figure.

          Thank you

            Comment

            Previous template Next
            Working...