Code:
CentOS Linux release 7.1.1503 (Core) zabbix.x86_64 2.4.5-1.el7 @zabbix zabbix-release.noarch 2.4-1.el7 installed zabbix-server.x86_64 2.4.5-1.el7 @zabbix zabbix-server-mysql.x86_64 2.4.5-1.el7 @zabbix zabbix-web.noarch 2.4.5-1.el7 @zabbix zabbix-web-pgsql.noarch 2.4.5-1.el7 @zabbix
Having troubles starting zabbix-server on a fresh install:
Starting service:
Code:
/bin/systemctl start zabbix-server.service Job for zabbix-server.service failed. See 'systemctl status zabbix-server.service' and 'journalctl -xn' for details.
Code:
zabbix-server.service - Zabbix Server Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled) Active: failed (Result: start-limit) since Thu 2015-06-04 15:22:06 CDT; 32s ago Process: 3724 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=killed, signal=SEGV) Jun 04 15:22:06 examplehostname systemd[1]: zabbix-server.service: control process exited, code=killed status=11 Jun 04 15:22:06 examplehostname systemd[1]: Failed to start Zabbix Server. Jun 04 15:22:06 examplehostname systemd[1]: Unit zabbix-server.service entered failed state. Jun 04 15:22:06 examplehostname systemd[1]: zabbix-server.service holdoff time over, scheduling restart. Jun 04 15:22:06 examplehostname systemd[1]: Stopping Zabbix Server... Jun 04 15:22:06 examplehostname systemd[1]: Starting Zabbix Server... Jun 04 15:22:06 examplehostname systemd[1]: zabbix-server.service start request repeated too quickly, refusing to start. Jun 04 15:22:06 examplehostname systemd[1]: Failed to start Zabbix Server. Jun 04 15:22:06 examplehostname systemd[1]: Unit zabbix-server.service entered failed state.
Code:
3723:20150604:152206.442 Please consider attaching a disassembly listing to your bug report. 3723:20150604:152206.442 This listing can be produced with, e.g., objdump -DSswx zabbix_server. 3723:20150604:152206.442 ================================ 3727:20150604:152206.532 Starting Zabbix Server. Zabbix 2.4.5 (revision 53282). 3727:20150604:152206.532 ****** Enabled features ****** 3727:20150604:152206.532 SNMP monitoring: YES 3727:20150604:152206.532 IPMI monitoring: YES 3727:20150604:152206.532 WEB monitoring: YES 3727:20150604:152206.532 VMware monitoring: YES 3727:20150604:152206.532 Jabber notifications: YES 3727:20150604:152206.532 Ez Texting notifications: YES 3727:20150604:152206.532 ODBC: YES 3727:20150604:152206.532 SSH2 support: YES 3727:20150604:152206.532 IPv6 support: YES 3727:20150604:152206.532 ****************************** 3727:20150604:152206.532 using configuration file: /etc/zabbix/zabbix_server.conf 3727:20150604:152206.539 current database version (mandatory/optional): 02040000/02040000 3727:20150604:152206.539 required mandatory version: 02040000 3727:20150604:152206.547 listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[-]:10051] 3727:20150604:152206.548 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x18]. Crashing ...
tcp 0 0 0.0.0.0:10051 0.0.0.0:* LISTEN
Note* if I pkill zabbix this stops showing up in netstat -ltn, only to reappear once I attempt to start it again.
After some googling i'm still not sure why it won't fully start. Any help is appreciated, thanks!
Comment