Почему фронт ZABBIX не запускается когда я перехожу по IP?
Добрый день
есть сервер, к которому подключаюсь по ssh на CentOS Stream release 8
Установил по инструкции ZABBIX
Но по IP не открывается в браузере страница настроек setup.php
Подскажите пожалуйста что нужно сделать чтобы открылась страница настроек?
я уже все конфиги и логи излазил только нужно чтобы кто-то направил в правильном направлении
zabbix-server запущен
что еще нужно сделать?
в файле /etc/nginx/conf.d/zabbix.conf прописал server_name IP адрес
server {
listen 80;
server_name 139.162.155.83;
root /usr/share/zabbix;
index index.php;
location = /favicon.ico {
log_not_found off;
}
лог
Starting Zabbix Server. Zabbix 6.0.9 (revision 64721203c07).
172684:20221106:083819.139 ****** Enabled features ******
172684:20221106:083819.139 SNMP monitoring: YES
172684:20221106:083819.139 IPMI monitoring: YES
172684:20221106:083819.139 Web monitoring: YES
172684:20221106:083819.139 VMware monitoring: YES
172684:20221106:083819.139 SMTP authentication: YES
172684:20221106:083819.139 ODBC: YES
172684:20221106:083819.139 SSH support: YES
172684:20221106:083819.139 IPv6 support: YES
172684:20221106:083819.139 TLS support: YES
172684:20221106:083819.139 ******************************
172684:20221106:083819.139 using configuration file: /etc/zabbix/zabbix_server.conf
172684:20221106:083819.216 current database version (mandatory/optional): 06000000/06000006
172684:20221106:083819.216 required mandatory version: 06000000
172685:20221106:083819.280 starting HA manager
172685:20221106:083819.297 HA manager started in active mode
172684:20221106:083819.299 server #0 started [main process]
172686:20221106:083819.303 server #1 started [service manager #1]
172687:20221106:083819.305 server #2 started [configuration syncer #1]
172688:20221106:083819.750 server #3 started [alert manager #1]
172689:20221106:083819.751 server #4 started [alerter #1]
172690:20221106:083819.752 server #5 started [alerter #2]
172691:20221106:083819.752 server #6 started [alerter #3]
172692:20221106:083819.753 server #7 started [preprocessing manager #1]
172693:20221106:083819.754 server #8 started [preprocessing worker #1]
172694:20221106:083819.755 server #9 started [preprocessing worker #2]
172695:20221106:083819.769 server #10 started [preprocessing worker #3]
172696:20221106:083819.770 server #11 started [lld manager #1]
172697:20221106:083819.771 server #12 started [lld worker #1]
172698:20221106:083819.774 server #13 started [lld worker #2]
172699:20221106:083819.776 server #14 started [housekeeper #1]
172700:20221106:083819.776 server #15 started [timer #1]
172701:20221106:083819.798 server #16 started [http poller #1]
172702:20221106:083819.800 server #17 started [discoverer #1]
172703:20221106:083819.804 server #18 started [history syncer #1]
172704:20221106:083819.807 server #19 started [history syncer #2]
172705:20221106:083819.808 server #20 started [history syncer #3]
172706:20221106:083819.810 server #21 started [history syncer #4]
172707:20221106:083819.823 server #22 started [escalator #1]
172708:20221106:083819.827 server #23 started [proxy poller #1]
172709:20221106:083819.830 server #24 started [self-monitoring #1]
172710:20221106:083819.831 server #25 started [task manager #1]
172711:20221106:083819.836 server #26 started [poller #1]
172712:20221106:083819.839 server #27 started [poller #2]
172713:20221106:083819.841 server #28 started [poller #3]
172721:20221106:083819.857 server #30 started [poller #5]
172722:20221106:083819.868 server #31 started [unreachable poller #1]
172723:20221106:083819.870 server #32 started [trapper #1]
172724:20221106:083819.872 server #33 started [trapper #2]
172725:20221106:083819.875 server #34 started [trapper #3]
172729:20221106:083819.890 server #35 started [trapper #4]
172720:20221106:083819.895 server #29 started [poller #4]
172730:20221106:083819.897 server #36 started [trapper #5]
172731:20221106:083819.910 server #37 started [icmp pinger #1]
172732:20221106:083819.920 server #38 started [alert syncer #1]
172733:20221106:083819.924 server #39 started [history poller #1]
172734:20221106:083819.927 server #40 started [history poller #2]
172735:20221106:083819.929 server #41 started [history poller #3]
172736:20221106:083819.932 server #42 started [history poller #4]
172745:20221106:083819.952 server #44 started [availability manager #1]
172746:20221106:083819.958 server #45 started [trigger housekeeper #1]
172747:20221106:083819.965 server #46 started [odbc poller #1]
172744:20221106:083819.991 server #43 started [history poller #5]
я не уверен что он установлен (в DevOps не очень пока варюсь)
вот такие шаги делал, но потом вместо Apache поставил nginx
установил mysql-server и запустил
mysqld.service - MySQL 8.0 database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2022-11-01 09:07:35 UTC; 3 days ago
Main PID: 16220 (mysqld)
Status: "Server is operational"
Tasks: 39 (limit: 4931)
Memory: 140.3M
CGroup: /system.slice/mysqld.service
└─16220 /usr/libexec/mysqld --basedir=/usr
В файле vim /etc/my.cnf.d/mysql-server.cnf
такие базовые настройки
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
log-error=/var/log/mysql/mysqld.log
pid-file=/run/mysqld/mysqld.pid
установил фронт
dnf install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-sql-scripts zabbix-selinux-policy zabbix-agent
потом создал юзера
mysql> create database zabbix character set utf8mb4 collate utf8mb4_bin;
mysql> create user zabbix@localhost identified by 'zabbix';
mysql> grant all privileges on zabbix.* to zabbix@localhost;
скопировал schema and data
zcat /usr/share/zabbix-sql-scripts/mysql/server.sql.gz | mysql --default-character-set=utf8mb4 -uzabbix -p zabbix
в файле /etc/zabbix/zabbix_server.conf прописал пароль для юзера zabbix
Ну а теперь открывайте логи nginx'a, логи php-fpm и смотрите, что там не так. Кстати, если nginx, то почему ставили zabbix-apache-conf, а не zabbix-nginx-conf?
Устанавливать надо не "по инструкции", а осознавая, что происходит - тогда и возникающие проблемы сможете самостоятельно решить. В данном случае, видимо, что-то с веб-сервером или РНР, смотрите настройки и логи.