We've loaded zabbix-server (version 2.4.5, downloaded from baseurl=http://repo.zabbix.com/zabbix/2.4/rhel/7/x86_64/)
onto a redhat 7 server. When we start the zabbix_server, we get:
sudo systemctl start zabbix-server
Job for zabbix-server.service failed. See 'systemctl status zabbix-server.service' and 'journalctl -xn' for details.
journalctl -xn returns: zabbix-server.service start request repeated too quickly, refusing to start. request repeated too quickly, refusing to start.
Failed to start Zabbix Server.
Buried an insane amount of messages (including a memory map) is the following:
listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[-]:10051]
3425:20150501:141259.457 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x18]. Crashing ...
I made sure there were no other zabbix servers running (although all I did was kill the ones left in the process table from the prior failed run, I didn't reboot the server to free up any ports)..
Any help will be appreciated.
Paul Mitchell
onto a redhat 7 server. When we start the zabbix_server, we get:
sudo systemctl start zabbix-server
Job for zabbix-server.service failed. See 'systemctl status zabbix-server.service' and 'journalctl -xn' for details.
journalctl -xn returns: zabbix-server.service start request repeated too quickly, refusing to start. request repeated too quickly, refusing to start.
Failed to start Zabbix Server.
Buried an insane amount of messages (including a memory map) is the following:
listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[-]:10051]
3425:20150501:141259.457 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x18]. Crashing ...
I made sure there were no other zabbix servers running (although all I did was kill the ones left in the process table from the prior failed run, I didn't reboot the server to free up any ports)..
Any help will be appreciated.
Paul Mitchell
Comment