Ad Widget

Collapse

Zabbix 4.4 / Centos 7minimal - page doesn't load

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • acatic1
    Member
    • Oct 2019
    • 38

    #1

    Zabbix 4.4 / Centos 7minimal - page doesn't load

    Novice Linux user, first-time Zabbix user.
    I've gotten through a few humps already trying to get the initial installation straight. Now, I'm at a point where it appears to be installed, except that the admin page does not load.
    Looking at the log, the services appear to be started. (See image attached) However, going to http://[ipaddress]/zabbix gives nothing. The IP is correct.
    I have restarted the VM, and waited ~15 minutes in case it's slow to load, but no luck.
    It's in a VM, with default Centos7 specs (1vCPU, 2GB vRAM, 16GB vdisk).
    Thank you in advance for any guidance.
  • acatic1
    Member
    • Oct 2019
    • 38

    #2
    /etc/var/log/zabbix_server.log:


    zabbix_server [17624]: Error waiting for process with PID 17662: [10] No child processes
    17624:20191013:220603.973 syncing trend data...
    17624:20191013:220603.973 syncing trend data done
    17624:20191013:220603.973 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17671:20191013:220614.195 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17671:20191013:220614.195 ****** Enabled features ******
    17671:20191013:220614.195 SNMP monitoring: YES
    17671:20191013:220614.195 IPMI monitoring: YES
    17671:20191013:220614.195 Web monitoring: YES
    17671:20191013:220614.195 VMware monitoring: YES
    17671:20191013:220614.195 SMTP authentication: YES
    17671:20191013:220614.195 ODBC: YES
    17671:20191013:220614.195 SSH2 support: YES
    17671:20191013:220614.195 IPv6 support: YES
    17671:20191013:220614.195 TLS support: YES
    17671:20191013:220614.195 ******************************
    17671:20191013:220614.195 using configuration file: /etc/zabbix/zabbix_server.conf
    17671:20191013:220614.197 current database version (mandatory/optional): 04040000/04040000
    17671:20191013:220614.197 required mandatory version: 04040000
    17671:20191013:220614.210 server #0 started [main process]
    17702:20191013:220614.216 server #27 started [alerter #1]
    17704:20191013:220614.216 server #29 started [alerter #3]
    17710:20191013:220614.216 server #35 started [lld worker #1]
    17688:20191013:220614.217 server #13 started [task manager #1]
    17689:20191013:220614.217 server #14 started [poller #1]
    17691:20191013:220614.227 server #16 started [poller #3]
    17694:20191013:220614.238 server #19 started [unreachable poller #1]
    17697:20191013:220614.248 server #22 started [trapper #3]
    17698:20191013:220614.250 server #23 started [trapper #4]
    17712:20191013:220614.252 server #37 started [alert syncer #1]
    17687:20191013:220614.252 server #12 started [self-monitoring #1]
    17685:20191013:220614.252 server #10 started [escalator #1]
    17696:20191013:220614.253 server #21 started [trapper #2]
    17709:20191013:220614.255 server #34 started [lld manager #1]
    17709:20191013:220614.255 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [13] Permission denied.
    17671:20191013:220614.256 One child process died (PID:17709,exitcode/signal:1). Exiting ...
    zabbix_server [17671]: Error waiting for process with PID 17709: [10] No child processes
    17671:20191013:220614.262 syncing trend data...
    17671:20191013:220614.262 syncing trend data done
    17671:20191013:220614.262 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17724:20191013:220624.443 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17724:20191013:220624.443 ****** Enabled features ******
    17724:20191013:220624.443 SNMP monitoring: YES
    17724:20191013:220624.443 IPMI monitoring: YES
    17724:20191013:220624.443 Web monitoring: YES
    17724:20191013:220624.443 VMware monitoring: YES
    17724:20191013:220624.443 SMTP authentication: YES
    17724:20191013:220624.443 ODBC: YES
    17724:20191013:220624.443 SSH2 support: YES
    17724:20191013:220624.443 IPv6 support: YES
    17724:20191013:220624.443 TLS support: YES
    17724:20191013:220624.443 ******************************
    17724:20191013:220624.443 using configuration file: /etc/zabbix/zabbix_server.conf
    17724:20191013:220624.445 current database version (mandatory/optional): 04040000/04040000
    17724:20191013:220624.445 required mandatory version: 04040000
    17724:20191013:220624.458 server #0 started [main process]
    17756:20191013:220624.464 server #28 started [alerter #2]
    17758:20191013:220624.464 server #30 started [preprocessing manager #1]
    17758:20191013:220624.464 cannot start preprocessing service: Cannot bind socket to "/var/run/zabbix/zabbix_server_preprocessing.sock": [13] Permission denied.
    17724:20191013:220624.464 One child process died (PID:17758,exitcode/signal:1). Exiting ...
    zabbix_server [17724]: Error waiting for process with PID 17758: [10] No child processes
    17724:20191013:220624.470 syncing trend data...
    17724:20191013:220624.471 syncing trend data done
    17724:20191013:220624.471 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17774:20191013:220634.692 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17774:20191013:220634.693 ****** Enabled features ******
    17774:20191013:220634.693 SNMP monitoring: YES
    17774:20191013:220634.693 IPMI monitoring: YES
    17774:20191013:220634.693 Web monitoring: YES
    17774:20191013:220634.693 VMware monitoring: YES
    17774:20191013:220634.693 SMTP authentication: YES
    17774:20191013:220634.693 ODBC: YES
    17774:20191013:220634.693 SSH2 support: YES
    17774:20191013:220634.693 IPv6 support: YES
    17774:20191013:220634.693 TLS support: YES
    17774:20191013:220634.693 ******************************
    17774:20191013:220634.693 using configuration file: /etc/zabbix/zabbix_server.conf
    17774:20191013:220634.695 current database version (mandatory/optional): 04040000/04040000
    17774:20191013:220634.695 required mandatory version: 04040000
    17774:20191013:220634.708 server #0 started [main process]
    17807:20191013:220634.714 server #29 started [alerter #3]
    17814:20191013:220634.714 server #36 started [lld worker #2]
    17812:20191013:220634.714 server #34 started [lld manager #1]
    17812:20191013:220634.714 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [13] Permission denied.
    17774:20191013:220634.715 One child process died (PID:17812,exitcode/signal:1). Exiting ...
    zabbix_server [17774]: Error waiting for process with PID 17812: [10] No child processes
    17774:20191013:220634.721 syncing trend data...
    17774:20191013:220634.721 syncing trend data done
    17774:20191013:220634.721 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17821:20191013:220644.943 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17821:20191013:220644.943 ****** Enabled features ******
    17821:20191013:220644.943 SNMP monitoring: YES
    17821:20191013:220644.943 IPMI monitoring: YES
    17821:20191013:220644.943 Web monitoring: YES
    17821:20191013:220644.943 VMware monitoring: YES
    17821:20191013:220644.943 SMTP authentication: YES
    17821:20191013:220644.943 ODBC: YES
    17821:20191013:220644.943 SSH2 support: YES
    17821:20191013:220644.943 IPv6 support: YES
    17821:20191013:220644.943 TLS support: YES
    17821:20191013:220644.943 ******************************
    17821:20191013:220644.943 using configuration file: /etc/zabbix/zabbix_server.conf
    17821:20191013:220644.945 current database version (mandatory/optional): 04040000/04040000
    17821:20191013:220644.945 required mandatory version: 04040000
    17821:20191013:220644.958 server #0 started [main process]
    17854:20191013:220644.963 server #29 started [alerter #3]
    17862:20191013:220644.964 server #37 started [alert syncer #1]
    17859:20191013:220644.964 server #34 started [lld manager #1]
    17859:20191013:220644.964 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [13] Permission denied.
    17821:20191013:220644.965 One child process died (PID:17859,exitcode/signal:1). Exiting ...
    zabbix_server [17821]: Error waiting for process with PID 17859: [10] No child processes
    17821:20191013:220644.971 syncing trend data...
    17821:20191013:220644.971 syncing trend data done
    17821:20191013:220644.971 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17868:20191013:220655.193 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17868:20191013:220655.193 ****** Enabled features ******
    17868:20191013:220655.193 SNMP monitoring: YES
    17868:20191013:220655.193 IPMI monitoring: YES
    17868:20191013:220655.193 Web monitoring: YES
    17868:20191013:220655.193 VMware monitoring: YES
    17868:20191013:220655.193 SMTP authentication: YES
    17868:20191013:220655.193 ODBC: YES
    17868:20191013:220655.193 SSH2 support: YES
    17868:20191013:220655.193 IPv6 support: YES
    17868:20191013:220655.193 TLS support: YES
    17868:20191013:220655.193 ******************************
    17868:20191013:220655.193 using configuration file: /etc/zabbix/zabbix_server.conf
    17868:20191013:220655.195 current database version (mandatory/optional): 04040000/04040000
    17868:20191013:220655.195 required mandatory version: 04040000
    17868:20191013:220655.208 server #0 started [main process]
    17901:20191013:220655.214 server #29 started [alerter #3]
    17909:20191013:220655.214 server #37 started [alert syncer #1]
    17906:20191013:220655.214 server #34 started [lld manager #1]
    17906:20191013:220655.215 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [13] Permission denied.
    17868:20191013:220655.215 One child process died (PID:17906,exitcode/signal:1). Exiting ...
    zabbix_server [17868]: Error waiting for process with PID 17906: [10] No child processes
    17868:20191013:220655.221 syncing trend data...
    17868:20191013:220655.222 syncing trend data done
    17868:20191013:220655.222 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17915:20191013:220705.442 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17915:20191013:220705.442 ****** Enabled features ******
    17915:20191013:220705.442 SNMP monitoring: YES
    17915:20191013:220705.442 IPMI monitoring: YES
    17915:20191013:220705.442 Web monitoring: YES
    17915:20191013:220705.442 VMware monitoring: YES
    17915:20191013:220705.442 SMTP authentication: YES
    17915:20191013:220705.442 ODBC: YES
    17915:20191013:220705.442 SSH2 support: YES
    17915:20191013:220705.442 IPv6 support: YES
    17915:20191013:220705.442 TLS support: YES
    17915:20191013:220705.442 ******************************
    17915:20191013:220705.442 using configuration file: /etc/zabbix/zabbix_server.conf
    17915:20191013:220705.445 current database version (mandatory/optional): 04040000/04040000
    17915:20191013:220705.445 required mandatory version: 04040000
    17915:20191013:220705.458 server #0 started [main process]
    17948:20191013:220705.464 server #29 started [alerter #3]
    17956:20191013:220705.464 server #37 started [alert syncer #1]
    17953:20191013:220705.464 server #34 started [lld manager #1]
    17953:20191013:220705.464 cannot start LLD manager service: Cannot bind socket to "/var/run/zabbix/zabbix_server_lld.sock": [13] Permission denied.
    17915:20191013:220705.465 One child process died (PID:17953,exitcode/signal:1). Exiting ...
    zabbix_server [17915]: Error waiting for process with PID 17953: [10] No child processes
    17915:20191013:220705.471 syncing trend data...
    17915:20191013:220705.471 syncing trend data done
    17915:20191013:220705.471 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    6645:20191013:233208.822 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    6645:20191013:233208.822 ****** Enabled features ******
    6645:20191013:233208.822 SNMP monitoring: YES
    6645:20191013:233208.822 IPMI monitoring: YES
    6645:20191013:233208.823 Web monitoring: YES
    6645:20191013:233208.823 VMware monitoring: YES
    6645:20191013:233208.823 SMTP authentication: YES
    6645:20191013:233208.823 ODBC: YES
    6645:20191013:233208.823 SSH2 support: YES
    6645:20191013:233208.823 IPv6 support: YES
    6645:20191013:233208.823 TLS support: YES
    6645:20191013:233208.823 ******************************
    6645:20191013:233208.823 using configuration file: /etc/zabbix/zabbix_server.conf
    6645:20191013:233208.902 current database version (mandatory/optional): 04040000/04040000
    6645:20191013:233208.902 required mandatory version: 04040000
    6645:20191013:233209.361 server #0 started [main process]
    6678:20191013:233209.372 server #29 started [alerter #3]
    6683:20191013:233209.372 server #34 started [lld manager #1]
    6662:20191013:233209.373 server #13 started [task manager #1]
    6664:20191013:233209.373 server #15 started [poller #2]
    6665:20191013:233209.375 server #16 started [poller #3]
    6667:20191013:233209.377 server #18 started [poller #5]
    6670:20191013:233209.379 server #21 started [trapper #2]
    6673:20191013:233209.381 server #24 started [trapper #5]
    6674:20191013:233209.383 server #25 started [icmp pinger #1]
    6684:20191013:233209.383 server #35 started [lld worker #1]
    6663:20191013:233209.383 server #14 started [poller #1]
    6659:20191013:233209.385 server #10 started [escalator #1]
    6672:20191013:233209.386 server #23 started [trapper #4]
    6685:20191013:233209.388 server #36 started [lld worker #2]
    6654:20191013:233209.388 server #5 started [discoverer #1]
    6655:20191013:233209.390 server #6 started [history syncer #1]
    6675:20191013:233209.390 server #26 started [alert manager #1]
    6651:20191013:233209.391 server #2 started [housekeeper #1]
    6652:20191013:233209.391 server #3 started [timer #1]
    6656:20191013:233209.391 server #7 started [history syncer #2]
    6657:20191013:233209.391 server #8 started [history syncer #3]
    6658:20191013:233209.392 server #9 started [history syncer #4]
    6661:20191013:233209.392 server #12 started [self-monitoring #1]
    6666:20191013:233209.392 server #17 started [poller #4]
    6668:20191013:233209.394 server #19 started [unreachable poller #1]
    6671:20191013:233209.395 server #22 started [trapper #3]
    6676:20191013:233209.397 server #27 started [alerter #1]
    6677:20191013:233209.397 server #28 started [alerter #2]
    6679:20191013:233209.397 server #30 started [preprocessing manager #1]
    6653:20191013:233209.398 server #4 started [http poller #1]
    6660:20191013:233209.398 server #11 started [proxy poller #1]
    6650:20191013:233209.399 server #1 started [configuration syncer #1]
    6669:20191013:233209.400 server #20 started [trapper #1]
    6686:20191013:233209.402 server #37 started [alert syncer #1]
    6680:20191013:233209.472 server #31 started [preprocessing worker #1]
    6682:20191013:233209.483 server #33 started [preprocessing worker #3]
    6681:20191013:233209.488 server #32 started [preprocessing worker #2]
    6667:20191013:233210.681 Zabbix agent item "system.cpu.load[all,avg1]" on host "Zabbix server" failed: first network error, wait for 15 seconds
    6668:20191013:233225.654 Zabbix agent item "system.cpu.util[,user]" on host "Zabbix server" failed: another network error, wait for 15 seconds
    6668:20191013:233240.658 Zabbix agent item "vfs.file.contents[/proc/diskstats]" on host "Zabbix server" failed: another network error, wait for 15 seconds
    6658:20191013:233242.414 item "Zabbix server:zabbix[process,ipmi poller,avg,busy]" became not supported: No "ipmi poller" processes started.
    6657:20191013:233243.414 item "Zabbix server:zabbix[process,java poller,avg,busy]" became not supported: No "java poller" processes started.
    6658:20191013:233248.417 item "Zabbix server:zabbix[process,snmp trapper,avg,busy]" became not supported: No "snmp trapper" processes started.
    6658:20191013:233248.417 item "Zabbix server:zabbix[process,ipmi manager,avg,busy]" became not supported: No "ipmi manager" processes started.
    6655:20191013:233249.418 item "Zabbix server:zabbix[process,vmware collector,avg,busy]" became not supported: No "vmware collector" processes started.
    6668:20191013:233255.662 temporarily disabling Zabbix agent checks on host "Zabbix server": host unavailable
    6658:20191013:233256.423 item "Zabbix server:zabbix[vmware,buffer,pused]" became not supported: No "vmware collector" processes started.
    6645:20191013:233320.222 Got signal [signal:15(SIGTERM),sender_pid:6739,sender_uid:0,re ason:0]. Exiting ...
    6655:20191013:233320.223 syncing history data in progress...
    6655:20191013:233320.223 syncing history data done
    6645:20191013:233320.261 syncing trend data...
    6645:20191013:233320.304 syncing trend data done
    6645:20191013:233320.304 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    6754:20191013:233320.314 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    6754:20191013:233320.314 ****** Enabled features ******
    6754:20191013:233320.314 SNMP monitoring: YES
    6754:20191013:233320.314 IPMI monitoring: YES
    6754:20191013:233320.314 Web monitoring: YES
    6754:20191013:233320.314 VMware monitoring: YES
    6754:20191013:233320.314 SMTP authentication: YES
    6754:20191013:233320.314 ODBC: YES
    6754:20191013:233320.314 SSH2 support: YES
    6754:20191013:233320.314 IPv6 support: YES
    6754:20191013:233320.314 TLS support: YES
    6754:20191013:233320.314 ******************************
    6754:20191013:233320.314 using configuration file: /etc/zabbix/zabbix_server.conf
    6754:20191013:233320.317 current database version (mandatory/optional): 04040000/04040000
    6754:20191013:233320.317 required mandatory version: 04040000
    6754:20191013:233320.330 server #0 started [main process]
    6787:20191013:233320.336 server #29 started [alerter #3]
    6795:20191013:233320.336 server #37 started [alert syncer #1]
    6792:20191013:233320.336 server #34 started [lld manager #1]
    6771:20191013:233320.337 server #13 started [task manager #1]
    6773:20191013:233320.337 server #15 started [poller #2]
    6774:20191013:233320.347 server #16 started [poller #3]
    6776:20191013:233320.358 server #18 started [poller #5]
    6779:20191013:233320.368 server #21 started [trapper #2]
    6782:20191013:233320.370 server #24 started [trapper #5]
    6783:20191013:233320.371 server #25 started [icmp pinger #1]
    6793:20191013:233320.372 server #35 started [lld worker #1]
    6772:20191013:233320.372 server #14 started [poller #1]
    6768:20191013:233320.382 server #10 started [escalator #1]
    6781:20191013:233320.384 server #23 started [trapper #4]
    6794:20191013:233320.385 server #36 started [lld worker #2]
    6764:20191013:233320.385 server #6 started [history syncer #1]
    6784:20191013:233320.385 server #26 started [alert manager #1]
    6760:20191013:233320.386 server #2 started [housekeeper #1]
    6761:20191013:233320.386 server #3 started [timer #1]
    6762:20191013:233320.386 server #4 started [http poller #1]
    6765:20191013:233320.386 server #7 started [history syncer #2]
    6766:20191013:233320.386 server #8 started [history syncer #3]
    6767:20191013:233320.387 server #9 started [history syncer #4]
    6770:20191013:233320.387 server #12 started [self-monitoring #1]
    6775:20191013:233320.387 server #17 started [poller #4]
    6777:20191013:233320.398 server #19 started [unreachable poller #1]
    6780:20191013:233320.408 server #22 started [trapper #3]
    6785:20191013:233320.409 server #27 started [alerter #1]
    6786:20191013:233320.409 server #28 started [alerter #2]
    6788:20191013:233320.409 server #30 started [preprocessing manager #1]
    6763:20191013:233320.410 server #5 started [discoverer #1]
    6769:20191013:233320.420 server #11 started [proxy poller #1]
    6759:20191013:233320.421 server #1 started [configuration syncer #1]
    6778:20191013:233320.421 server #20 started [trapper #1]
    6789:20191013:233321.037 server #31 started [preprocessing worker #1]
    6791:20191013:233321.073 server #33 started [preprocessing worker #3]
    6790:20191013:233321.086 server #32 started [preprocessing worker #2]
    6777:20191013:233355.435 enabling Zabbix agent checks on host "Zabbix server": host became available
    6765:20191013:233522.535 item "Zabbix server:vfs.dev.read.await[sda]" became not supported: Cannot evaluate expression: "Cannot evaluate function "last()": not enough data.".
    6764:20191013:233523.536 item "Zabbix server:vfs.dev.write.await[sda]" became not supported: Cannot evaluate expression: "Cannot evaluate function "last()": not enough data.".
    6765:20191013:234222.841 item "Zabbix server:vfs.dev.read.await[sda]" became supported
    6764:20191013:234223.842 item "Zabbix server:vfs.dev.write.await[sda]" became supported
    6754:20191013:235648.953 Got signal [signal:15(SIGTERM),sender_pid:6956,sender_uid:0,re ason:0]. Exiting ...
    6764:20191013:235648.953 syncing history data in progress...
    6764:20191013:235648.953 [Z3005] query failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [begin;]
    6764:20191013:235648.953 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    6764:20191013:235648.953 database is down: reconnecting in 10 seconds
    6795:20191013:235648.956 [Z3005] query failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [begin;]
    6795:20191013:235648.956 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    6795:20191013:235648.956 database is down: reconnecting in 10 seconds
    6771:20191013:235648.966 [Z3005] query failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) [select taskid,type,clock,ttl from task where status in (1,2) order by taskid]
    ..........
    6148:20191014:000219.144 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    6148:20191014:000219.163 ****** Enabled features ******
    6148:20191014:000219.163 SNMP monitoring: YES
    6148:20191014:000219.163 IPMI monitoring: YES
    6148:20191014:000219.163 Web monitoring: YES
    6148:20191014:000219.163 VMware monitoring: YES
    6148:20191014:000219.163 SMTP authentication: YES
    6148:20191014:000219.163 ODBC: YES
    6148:20191014:000219.163 SSH2 support: YES
    6148:20191014:000219.163 IPv6 support: YES
    6148:20191014:000219.163 TLS support: YES
    6148:20191014:000219.163 ******************************
    6148:20191014:000219.163 using configuration file: /etc/zabbix/zabbix_server.conf
    6148:20191014:000219.514 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    6148:20191014:000219.514 database is down: reconnecting in 10 seconds
    6148:20191014:000229.575 database connection re-established
    6148:20191014:000229.586 current database version (mandatory/optional): 04040000/04040000
    6148:20191014:000229.586 required mandatory version: 04040000
    6148:20191014:000230.047 server #0 started [main process]
    6675:20191014:000230.055 server #29 started [alerter #3]
    6683:20191014:000230.055 server #37 started [alert syncer #1]
    6661:20191014:000230.056 server #15 started [poller #2]
    6662:20191014:000230.056 server #16 started [poller #3]
    6664:20191014:000230.056 server #18 started [poller #5]
    6667:20191014:000230.056 server #21 started [trapper #2]
    6670:20191014:000230.058 server #24 started [trapper #5]
    6671:20191014:000230.060 server #25 started [icmp pinger #1]
    6660:20191014:000230.060 server #14 started [poller #1]
    6669:20191014:000230.061 server #23 started [trapper #4]
    6651:20191014:000230.062 server #5 started [discoverer #1]
    6652:20191014:000230.062 server #6 started [history syncer #1]
    6672:20191014:000230.063 server #26 started [alert manager #1]
    6648:20191014:000230.063 server #2 started [housekeeper #1]
    6649:20191014:000230.063 server #3 started [timer #1]
    6650:20191014:000230.063 server #4 started [http poller #1]
    6653:20191014:000230.064 server #7 started [history syncer #2]
    6654:20191014:000230.064 server #8 started [history syncer #3]
    6655:20191014:000230.064 server #9 started [history syncer #4]
    6663:20191014:000230.064 server #17 started [poller #4]
    6665:20191014:000230.064 server #19 started [unreachable poller #1]
    6668:20191014:000230.064 server #22 started [trapper #3]
    6673:20191014:000230.066 server #27 started [alerter #1]
    6674:20191014:000230.066 server #28 started [alerter #2]
    6647:20191014:000230.066 server #1 started [configuration syncer #1]
    6666:20191014:000230.066 server #20 started [trapper #1]
    6657:20191014:000230.068 server #11 started [proxy poller #1]
    6658:20191014:000230.069 server #12 started [self-monitoring #1]
    6659:20191014:000230.069 server #13 started [task manager #1]
    6676:20191014:000230.071 server #30 started [preprocessing manager #1]
    6678:20191014:000230.071 server #32 started [preprocessing worker #2]
    6656:20191014:000230.071 server #10 started [escalator #1]
    6680:20191014:000230.072 server #34 started [lld manager #1]
    6682:20191014:000230.073 server #36 started [lld worker #2]
    6681:20191014:000230.073 server #35 started [lld worker #1]
    6679:20191014:000230.171 server #33 started [preprocessing worker #3]
    6677:20191014:000230.171 server #31 started [preprocessing worker #1]
    6648:20191014:003230.334 executing housekeeper
    6648:20191014:003230.387 housekeeper [deleted 0 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.053261 sec, idle for 1 hour(s)]
    6148:20191014:004041.586 Got signal [signal:15(SIGTERM),sender_pid:7175,sender_uid:0,re ason:0]. Exiting ...
    6652:20191014:004041.586 syncing history data in progress...
    6652:20191014:004041.600 syncing history data... 100.000000%
    6652:20191014:004041.600 syncing history data done
    6148:20191014:004041.614 syncing trend data...
    6148:20191014:004041.618 syncing trend data done
    6148:20191014:004041.618 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    7191:20191014:004041.634 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    7191:20191014:004041.634 ****** Enabled features ******
    7191:20191014:004041.634 SNMP monitoring: YES
    7191:20191014:004041.634 IPMI monitoring: YES
    7191:20191014:004041.634 Web monitoring: YES
    7191:20191014:004041.634 VMware monitoring: YES
    7191:20191014:004041.634 SMTP authentication: YES
    7191:20191014:004041.634 ODBC: YES
    7191:20191014:004041.634 SSH2 support: YES
    7191:20191014:004041.634 IPv6 support: YES
    7191:20191014:004041.634 TLS support: YES
    7191:20191014:004041.634 ******************************
    7191:20191014:004041.634 using configuration file: /etc/zabbix/zabbix_server.conf
    7191:20191014:004041.636 current database version (mandatory/optional): 04040000/04040000
    7191:20191014:004041.636 required mandatory version: 04040000
    7191:20191014:004041.651 server #0 started [main process]
    7224:20191014:004041.657 server #29 started [alerter #3]
    7232:20191014:004041.658 server #37 started [alert syncer #1]
    7229:20191014:004041.658 server #34 started [lld manager #1]
    7208:20191014:004041.658 server #13 started [task manager #1]
    7210:20191014:004041.658 server #15 started [poller #2]
    7211:20191014:004041.669 server #16 started [poller #3]
    7213:20191014:004041.683 server #18 started [poller #5]
    7216:20191014:004041.704 server #21 started [trapper #2]
    7219:20191014:004041.706 server #24 started [trapper #5]
    7220:20191014:004041.707 server #25 started [icmp pinger #1]
    7230:20191014:004041.708 server #35 started [lld worker #1]
    7209:20191014:004041.708 server #14 started [poller #1]
    7205:20191014:004041.718 server #10 started [escalator #1]
    7218:20191014:004041.719 server #23 started [trapper #4]
    7231:20191014:004041.720 server #36 started [lld worker #2]
    7200:20191014:004041.721 server #5 started [discoverer #1]
    7201:20191014:004041.731 server #6 started [history syncer #1]
    7221:20191014:004041.731 server #26 started [alert manager #1]
    7197:20191014:004041.731 server #2 started [housekeeper #1]
    7198:20191014:004041.731 server #3 started [timer #1]
    7202:20191014:004041.732 server #7 started [history syncer #2]
    7203:20191014:004041.732 server #8 started [history syncer #3]
    7204:20191014:004041.732 server #9 started [history syncer #4]
    7207:20191014:004041.732 server #12 started [self-monitoring #1]
    7212:20191014:004041.732 server #17 started [poller #4]
    7214:20191014:004041.743 server #19 started [unreachable poller #1]
    7217:20191014:004041.753 server #22 started [trapper #3]
    7222:20191014:004041.755 server #27 started [alerter #1]
    7223:20191014:004041.755 server #28 started [alerter #2]
    7225:20191014:004041.755 server #30 started [preprocessing manager #1]
    7199:20191014:004041.755 server #4 started [http poller #1]
    7206:20191014:004041.755 server #11 started [proxy poller #1]
    7196:20191014:004041.757 server #1 started [configuration syncer #1]
    7215:20191014:004041.757 server #20 started [trapper #1]
    7226:20191014:004042.059 server #31 started [preprocessing worker #1]
    7228:20191014:004042.108 server #33 started [preprocessing worker #3]
    7227:20191014:004042.121 server #32 started [preprocessing worker #2]
    7191:20191014:004113.845 Got signal [signal:15(SIGTERM),sender_pid:7278,sender_uid:0,re ason:0]. Exiting ...
    7201:20191014:004113.845 syncing history data in progress...
    7201:20191014:004113.845 syncing history data done
    7191:20191014:004113.858 [Z3001] connection to database 'zabbix' failed: [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 104
    7191:20191014:004113.858 Cannot connect to the database. Exiting...
    6022:20191014:004141.387 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    6022:20191014:004141.388 ****** Enabled features ******
    6022:20191014:004141.388 SNMP monitoring: YES
    6022:20191014:004141.388 IPMI monitoring: YES
    6022:20191014:004141.388 Web monitoring: YES
    6022:20191014:004141.388 VMware monitoring: YES
    6022:20191014:004141.388 SMTP authentication: YES
    6022:20191014:004141.388 ODBC: YES
    6022:20191014:004141.388 SSH2 support: YES
    6022:20191014:004141.388 IPv6 support: YES
    6022:20191014:004141.388 TLS support: YES
    6022:20191014:004141.388 ******************************
    6022:20191014:004141.388 using configuration file: /etc/zabbix/zabbix_server.conf
    6022:20191014:004141.613 [Z3001] connection to database 'zabbix' failed: [2002] Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    6022:20191014:004141.613 database is down: reconnecting in 10 seconds
    6022:20191014:004151.666 database connection re-established
    6022:20191014:004151.677 current database version (mandatory/optional): 04040000/04040000
    6022:20191014:004151.677 required mandatory version: 04040000
    6022:20191014:004152.139 server #0 started [main process]
    6679:20191014:004152.147 server #29 started [alerter #3]
    6687:20191014:004152.147 server #37 started [alert syncer #1]
    6665:20191014:004152.148 server #15 started [poller #2]
    6666:20191014:004152.148 server #16 started [poller #3]
    6668:20191014:004152.148 server #18 started [poller #5]
    6671:20191014:004152.148 server #21 started [trapper #2]
    6674:20191014:004152.150 server #24 started [trapper #5]
    6675:20191014:004152.151 server #25 started [icmp pinger #1]
    6664:20191014:004152.152 server #14 started [poller #1]
    6673:20191014:004152.152 server #23 started [trapper #4]
    6655:20191014:004152.153 server #5 started [discoverer #1]
    6656:20191014:004152.153 server #6 started [history syncer #1]
    6676:20191014:004152.153 server #26 started [alert manager #1]
    6651:20191014:004152.154 server #1 started [configuration syncer #1]
    6652:20191014:004152.154 server #2 started [housekeeper #1]
    6653:20191014:004152.154 server #3 started [timer #1]
    6657:20191014:004152.155 server #7 started [history syncer #2]
    6658:20191014:004152.155 server #8 started [history syncer #3]
    6659:20191014:004152.155 server #9 started [history syncer #4]
    6667:20191014:004152.155 server #17 started [poller #4]
    6669:20191014:004152.155 server #19 started [unreachable poller #1]
    6672:20191014:004152.155 server #22 started [trapper #3]
    6677:20191014:004152.157 server #27 started [alerter #1]
    6678:20191014:004152.157 server #28 started [alerter #2]
    6654:20191014:004152.157 server #4 started [http poller #1]
    6670:20191014:004152.157 server #20 started [trapper #1]
    6660:20191014:004152.166 server #10 started [escalator #1]
    6661:20191014:004152.167 server #11 started [proxy poller #1]
    6662:20191014:004152.169 server #12 started [self-monitoring #1]
    6663:20191014:004152.169 server #13 started [task manager #1]
    6680:20191014:004152.173 server #30 started [preprocessing manager #1]
    6681:20191014:004152.173 server #31 started [preprocessing worker #1]
    6683:20191014:004152.173 server #33 started [preprocessing worker #3]
    6682:20191014:004152.173 server #32 started [preprocessing worker #2]
    6684:20191014:004152.173 server #34 started [lld manager #1]
    6686:20191014:004152.173 server #36 started [lld worker #2]
    6685:20191014:004152.174 server #35 started [lld worker #1]
    6652:20191014:011152.420 executing housekeeper
    6652:20191014:011152.446 housekeeper [deleted 32 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.025206 sec, idle for 1 hour(s)]
    6022:20191014:012943.244 Got signal [signal:15(SIGTERM),sender_pid:17372,sender_uid:0,r eason:0]. Exiting ...
    6656:20191014:012943.244 syncing history data in progress...
    6656:20191014:012943.244 syncing history data done
    6022:20191014:012943.261 syncing trend data...
    6022:20191014:012943.272 syncing trend data done
    6022:20191014:012943.273 Zabbix Server stopped. Zabbix 4.4.0 (revision cfac660b25).
    17388:20191014:012943.294 Starting Zabbix Server. Zabbix 4.4.0 (revision cfac660b25).
    17388:20191014:012943.294 ****** Enabled features ******
    17388:20191014:012943.294 SNMP monitoring: YES
    17388:20191014:012943.294 IPMI monitoring: YES
    17388:20191014:012943.294 Web monitoring: YES
    17388:20191014:012943.294 VMware monitoring: YES
    17388:20191014:012943.294 SMTP authentication: YES
    17388:20191014:012943.294 ODBC: YES
    17388:20191014:012943.294 SSH2 support: YES
    17388:20191014:012943.294 IPv6 support: YES
    17388:20191014:012943.294 TLS support: YES
    17388:20191014:012943.294 ******************************
    17388:20191014:012943.294 using configuration file: /etc/zabbix/zabbix_server.conf
    17388:20191014:012943.297 current database version (mandatory/optional): 04040000/04040000
    17388:20191014:012943.297 required mandatory version: 04040000
    17388:20191014:012943.311 server #0 started [main process]
    17421:20191014:012943.317 server #29 started [alerter #3]
    17429:20191014:012943.317 server #37 started [alert syncer #1]
    17426:20191014:012943.318 server #34 started [lld manager #1]
    17405:20191014:012943.318 server #13 started [task manager #1]
    17407:20191014:012943.318 server #15 started [poller #2]
    17408:20191014:012943.328 server #16 started [poller #3]
    17410:20191014:012943.339 server #18 started [poller #5]
    17413:20191014:012943.349 server #21 started [trapper #2]
    17416:20191014:012943.350 server #24 started [trapper #5]
    17417:20191014:012943.352 server #25 started [icmp pinger #1]
    17427:20191014:012943.352 server #35 started [lld worker #1]
    17406:20191014:012943.352 server #14 started [poller #1]
    17402:20191014:012943.367 server #10 started [escalator #1]
    17415:20191014:012943.368 server #23 started [trapper #4]
    17428:20191014:012943.370 server #36 started [lld worker #2]
    17397:20191014:012943.370 server #5 started [discoverer #1]
    17398:20191014:012943.391 server #6 started [history syncer #1]
    17418:20191014:012943.391 server #26 started [alert manager #1]
    17393:20191014:012943.392 server #1 started [configuration syncer #1]
    17394:20191014:012943.392 server #2 started [housekeeper #1]
    17395:20191014:012943.392 server #3 started [timer #1]
    17399:20191014:012943.392 server #7 started [history syncer #2]
    17400:20191014:012943.392 server #8 started [history syncer #3]
    17401:20191014:012943.393 server #9 started [history syncer #4]
    17404:20191014:012943.393 server #12 started [self-monitoring #1]
    17409:20191014:012943.393 server #17 started [poller #4]
    17411:20191014:012943.403 server #19 started [unreachable poller #1]
    17414:20191014:012943.413 server #22 started [trapper #3]
    17419:20191014:012943.415 server #27 started [alerter #1]
    17420:20191014:012943.415 server #28 started [alerter #2]
    17422:20191014:012943.415 server #30 started [preprocessing manager #1]
    17396:20191014:012943.415 server #4 started [http poller #1]
    17403:20191014:012943.415 server #11 started [proxy poller #1]
    17412:20191014:012943.417 server #20 started [trapper #1]
    17423:20191014:012944.019 server #31 started [preprocessing worker #1]
    17425:20191014:012944.053 server #33 started [preprocessing worker #3]
    17424:20191014:012944.071 server #32 started [preprocessing worker #2]
    17394:20191014:015943.653 executing housekeeper
    17394:20191014:015943.659 housekeeper [deleted 47 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.005087 sec, idle for 1 hour(s)]
    17394:20191014:025944.195 executing housekeeper
    17394:20191014:025944.208 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.012839 sec, idle for 1 hour(s)]
    17394:20191014:035944.735 executing housekeeper
    17394:20191014:035944.738 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.002698 sec, idle for 1 hour(s)]
    17394:20191014:045945.281 executing housekeeper
    17394:20191014:045945.285 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.002926 sec, idle for 1 hour(s)]
    17394:20191014:055945.814 executing housekeeper
    17394:20191014:055945.817 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.002674 sec, idle for 1 hour(s)]
    17394:20191014:065946.365 executing housekeeper
    17394:20191014:065946.373 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.007608 sec, idle for 1 hour(s)]
    17394:20191014:075946.914 executing housekeeper
    17394:20191014:075946.918 housekeeper [deleted 60 hist/trends, 0 items/triggers, 0 events, 0 problems, 0 sessions, 0 alarms, 0 audit, 0 records in 0.003279 sec, idle for 1 hour(s)]

    Comment

    • acatic1
      Member
      • Oct 2019
      • 38

      #3
      It's on a flat network. The Zabbix server can ping others, and others can ping it. I can access its files remotely.

      Comment

      • acatic1
        Member
        • Oct 2019
        • 38

        #4
        Attaching zabbix_server.conf file as txt
        Attached Files

        Comment

        • acatic1
          Member
          • Oct 2019
          • 38

          #5
          Never mind! I didn't notice till now that the timezone line actually had a comment hash that needed to be removed, and I also didn't realize that CentOS itself had to have its firewall edited; I thought it referred to a dedicated firewall unit and not to systems on the same network. Sorry for bother. Hopefully this helps someone.

          Comment

          Working...