Ad Widget

Collapse

Fail to Access Zabbix Web After Installation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Acho
    Junior Member
    • Apr 2019
    • 9

    #1

    Fail to Access Zabbix Web After Installation

    Hi good guys,

    Can somebody help me please, I have a problem to access Zabbix web / frontend installation after did any script to install Zabbix server on Ubuntu 16.04.
    This is the link I refer to install zabbix server :


    But, after installation on ubuntu terminal and intend to continue frontend installation via web to my PC IP:
    http://172.16.2.2 -> it shows me apache 'it works!'
    and also tried
    http://172.16.2.2/zabbix -> it shows me this: 403 Forbidden nginx/1.10.3 (Ubuntu).

    What I have done to get some diagnoses is:
    sukarno@devel-comp:/$ sudo service zabbix-server status
    ● zabbix-server.service - Zabbix Server
    Loaded: loaded (/lib/systemd/system/zabbix-server.service; enabled; vendor preset: enabled)
    Active: active (running) since Sen 2019-04-01 17:46:42 WIB; 1h 52min ago
    Main PID: 9782 (zabbix_server)
    CGroup: /system.slice/zabbix-server.service
    ├─9782 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf
    ├─9783 /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.004757 sec, idle 60 sec
    ├─9784 /usr/sbin/zabbix_server: alerter #1 started
    ├─9785 /usr/sbin/zabbix_server: alerter #2 started
    ├─9786 /usr/sbin/zabbix_server: alerter #3 started
    ├─9787 /usr/sbin/zabbix_server: housekeeper [deleted 0 hist/trends, 0 items/triggers, 0 events, 0 sessions, 0 alarms, 0 audit items in 0.000901 sec, idle
    ├─9788 /usr/sbin/zabbix_server: timer #1 [processed 0 triggers, 0 events in 0.000041 sec, 0 maintenances in 0.000729 sec, idle 30 sec
    ├─9789 /usr/sbin/zabbix_server: http poller #1 [got 0 values in 0.000584 sec, idle 5 sec
    ├─9790 /usr/sbin/zabbix_server: discoverer #1 [processed 0 rules in 0.000609 sec, idle 60 sec
    ├─9791 /usr/sbin/zabbix_server: history syncer #1 [synced 0 items in 0.000026 sec, idle 1 sec
    ├─9792 /usr/sbin/zabbix_server: history syncer #2 [synced 0 items in 0.000030 sec, idle 1 sec
    ├─9793 /usr/sbin/zabbix_server: history syncer #3 [synced 0 items in 0.000026 sec, idle 1 sec
    ├─9794 /usr/sbin/zabbix_server: history syncer #4 [synced 0 items in 0.000026 sec, idle 1 sec
    ├─9795 /usr/sbin/zabbix_server: escalator #1 [processed 0 escalations in 0.000283 sec, idle 3 sec
    ├─9796 /usr/sbin/zabbix_server: proxy poller #1 [exchanged data with 0 proxies in 0.000029 sec, idle 5 sec
    ├─9797 /usr/sbin/zabbix_server: self-monitoring [processed data in 0.000029 sec, idle 1 sec
    ├─9798 /usr/sbin/zabbix_server: task manager [processed 0 task(s) in 0.000173 sec, idle 5 sec
    ├─9799 /usr/sbin/zabbix_server: poller #1 [got 0 values in 0.000030 sec, idle 5 sec
    ├─9800 /usr/sbin/zabbix_server: poller #2 [got 0 values in 0.000030 sec, idle 5 sec
    ├─9801 /usr/sbin/zabbix_server: poller #3 [got 0 values in 0.000031 sec, idle 5 sec
    ├─9802 /usr/sbin/zabbix_server: poller #4 [got 0 values in 0.000030 sec, idle 5 sec
    ├─9803 /usr/sbin/zabbix_server: poller #5 [got 0 values in 0.000031 sec, idle 5 sec
    ├─9804 /usr/sbin/zabbix_server: unreachable poller #1 [got 0 values in 0.000030 sec, idle 5 sec
    ├─9805 /usr/sbin/zabbix_server: trapper #1 [processed data in 0.000000 sec, waiting for connection
    ├─9806 /usr/sbin/zabbix_server: trapper #2 [processed data in 0.000000 sec, waiting for connection
    ├─9808 /usr/sbin/zabbix_server: trapper #3 [processed data in 0.000000 sec, waiting for connection
    ├─9809 /usr/sbin/zabbix_server: trapper #4 [processed data in 0.000000 sec, waiting for connection
    ├─9810 /usr/sbin/zabbix_server: trapper #5 [processed data in 0.000000 sec, waiting for connection
    ├─9813 /usr/sbin/zabbix_server: icmp pinger #1 [got 0 values in 0.000026 sec, idle 5 sec
    ├─9814 /usr/sbin/zabbix_server: alert manager #1 [sent 0, failed 0 alerts, idle 5.006332 sec during 5.006402 sec
    ├─9815 /usr/sbin/zabbix_server: preprocessing manager #1 [queued 0, processed 0 values, idle 5.005441 sec during 5.005515 sec
    ├─9816 /usr/sbin/zabbix_server: preprocessing worker #1 started
    ├─9817 /usr/sbin/zabbix_server: preprocessing worker #2 started
    └─9818 /usr/sbin/zabbix_server: preprocessing worker #3 started

    Apr 01 17:46:42 devel-comp systemd[1]: Starting Zabbix Server...
    Apr 01 17:46:42 devel-comp systemd[1]: Started Zabbix Server.


    sukarno@devel-comp:/$ sudo service mysql status
    ● mysql.service - LSB: Start and stop the mysql database server daemon
    Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
    Active: active (running) since Jum 2019-03-29 16:54:04 WIB; 3 days ago
    Docs: man:systemd-sysv-generator(8)
    CGroup: /system.slice/mysql.service
    ├─1657 /bin/bash /usr/bin/mysqld_safe
    ├─1811 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --skip-log-error --pid-file=/var/run/mysql
    └─1812 logger -t mysqld -p daemon error

    Mar 29 16:54:02 devel-comp mysqld[1812]: 190329 16:54:02 [Note] InnoDB: Highest supported file format is Barracuda.
    Mar 29 16:54:03 devel-comp mysqld[1812]: 190329 16:54:03 [Note] InnoDB: 128 rollback segment(s) are active.
    Mar 29 16:54:03 devel-comp mysqld[1812]: 190329 16:54:03 [Note] InnoDB: Waiting for purge to start
    Mar 29 16:54:03 devel-comp mysqld[1812]: 190329 16:54:03 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence number 10326963
    Mar 29 16:54:03 devel-comp mysqld[1812]: 190329 16:54:03 [Note] Plugin 'FEEDBACK' is disabled.
    Mar 29 16:54:03 devel-comp mysqld[1812]: 190329 16:54:03 [Note] Server socket created on IP: '127.0.0.1'.
    Mar 29 16:54:04 devel-comp mysqld[1812]: 190329 16:54:04 [Note] /usr/sbin/mysqld: ready for connections.
    Mar 29 16:54:04 devel-comp mysqld[1812]: Version: '10.0.38-MariaDB-0ubuntu0.16.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Ubuntu 16.04
    Mar 29 16:54:04 devel-comp mysql[1509]: ...done.
    Mar 29 16:54:04 devel-comp systemd[1]: Started LSB: Start and stop the mysql database server daemon.


    And somehow this one shows a different status: inactive (dead)
    sukarno@devel-comp:/$ sudo service apache status

    ● apache.service
    Loaded: not-found (Reason: No such file or directory)
    Active: inactive (dead)
    sukarno@devel-comp:/$ sudo service apache2 status
    ● apache2.service - LSB: Apache2 web server
    Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
    Drop-In: /lib/systemd/system/apache2.service.d
    └─apache2-systemd.conf
    Active: inactive (dead) since Sen 2019-04-01 19:35:06 WIB; 8min ago
    Docs: man:systemd-sysv-generator(8)
    Process: 10906 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS)
    Process: 10889 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS)

    Apr 01 19:35:06 devel-comp apache2[10889]: (98)Address already in use: AH00072: make_sock: could not bind to address [::]:80
    Apr 01 19:35:06 devel-comp apache2[10889]: (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:80
    Apr 01 19:35:06 devel-comp apache2[10889]: no listening sockets available, shutting down
    Apr 01 19:35:06 devel-comp apache2[10889]: AH00015: Unable to open logs
    Apr 01 19:35:06 devel-comp apache2[10889]: Action 'start' failed.
    Apr 01 19:35:06 devel-comp apache2[10889]: The Apache error log may have more information.
    Apr 01 19:35:06 devel-comp apache2[10889]: *
    Apr 01 19:35:06 devel-comp apache2[10906]: * Stopping Apache httpd web server apache2
    Apr 01 19:35:06 devel-comp apache2[10906]: *
    Apr 01 19:35:06 devel-comp systemd[1]: Started LSB: Apache2 web server.


    I have been trying to do it about last few days but still unable to access this frontend zabbix web installation.
    Just FYI, I am just a junior network engineer and not knowing too much about backend and frontend programming.
    So if You guys were willing to help me, pls just make it eassy to me

    Thanks.



  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #2
    The web server running in your environment seems to be nginx. You will need to either stop nginx and start apache2 or start apache2 on a different port number.

    It is possible to run Zabbix by combining nginx and PHP without using apache2, but it may be difficult for beginners.

    Comment


    • kenorosarioPH
      kenorosarioPH commented
      Editing a comment
      Hi , i am newbie to apache2 and webserver. is there a link i can follow on how to do this?

      I already changed my apache2 listening port to 8081 and it redirects me to apache2 default page not the zabbix.

    • Atsushi
      Atsushi commented
      Editing a comment
      Hi kenorosarioPH,
      I don't know exactly what you set and how. What I can tell from the phenomenon is that the settings are missing or incorrect, so first check the Apache HTTP Server settings.
  • Acho
    Junior Member
    • Apr 2019
    • 9

    #3
    Originally posted by Atsushi
    The web server running in your environment seems to be nginx. You will need to either stop nginx and start apache2 or start apache2 on a different port number.

    It is possible to run Zabbix by combining nginx and PHP without using apache2, but it may be difficult for beginners.
    Well Mr. Atsushi, it works now. Thanks for your advices.

    Comment

    • Andrey123987456
      Member
      • Apr 2019
      • 44

      #4

      Good afternoon everybody, I also have a problem, it’s written in the web interface that the zabbix server is not running, although in fact it is active, please tell me
      Attached Files

      Comment


      • Atsushi
        Atsushi commented
        Editing a comment
        Please check SELinux settings.
    • Andrey123987456
      Member
      • Apr 2019
      • 44

      #5

      At the moment I have it turned off, but I turned it on and set it up under turned on did not help

      This file controls the state of SELinux on the system.
      # SELINUX= can take one of these three values:
      # enforcing - SELinux security policy is enforced.
      # permissive - SELinux prints warnings instead of enforcing.
      # disabled - No SELinux policy is loaded.
      SELINUX=enforcing
      # SELINUXTYPE= can take one of three values:
      # targeted - Targeted processes are protected,
      # minimum - Modification of targeted policy. Only selected processes are protected.
      # mls - Multi Level Security protection.
      SELINUX=disabled


      setenforce 0

      Comment

      • Andrey123987456
        Member
        • Apr 2019
        • 44

        #6
        [root@localhost ~]# getenforce
        Disabled

        Is this a mistake?
        Attached Files

        Comment

        • Andrey123987456
          Member
          • Apr 2019
          • 44

          #7
          this is problem ?
          Attached Files

          Comment

          • Andrey123987456
            Member
            • Apr 2019
            • 44

            #8
            maybe it will help to understand
            Attached Files

            Comment

            Working...