Hello:
We have checked Zabbix 2.2.6 and server does not start.
We returned to more stable version 2.2.3.
We have this issue since version 2.2.4.
Zabbix server does not start because crashed.
Even though version 2.2.3 also is not stable because, though it starts normally, it crashed when server fails to acquire some items.
We have compiled Zabbix source in SLES 11 SP3 with this commad:
CFLAGS="-O2" \
CXX=gcc \
CXXFLAGS="-O2 -mtune=nocona -felide-constructors -fno-exceptions -fno-rtti" \
./configure --enable-server --enable-agent --with-mysql --with-libcurl --sysconfdir="/etc/zabbix"
And next I have attached first lines from log:
18308:20140912:134049.390 Starting Zabbix Server. Zabbix 2.2.6 (revision 48483).
18308:20140912:134049.390 ****** Enabled features ******
18308:20140912:134049.390 SNMP monitoring: NO
18308:20140912:134049.390 IPMI monitoring: NO
18308:20140912:134049.390 WEB monitoring: YES
18308:20140912:134049.390 VMware monitoring: NO
18308:20140912:134049.390 Jabber notifications: NO
18308:20140912:134049.390 Ez Texting notifications: YES
18308:20140912:134049.390 ODBC: NO
18308:20140912:134049.390 SSH2 support: NO
18308:20140912:134049.390 IPv6 support: NO
18308:20140912:134049.390 ******************************
18308:20140912:134049.390 using configuration file: /etc/zabbix/zabbix_server.conf
18308:20140912:134049.396 current database version (mandatory/optional): 02020000/02020001
18308:20140912:134049.396 required mandatory version: 02020000
18308:20140912:134049.440 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...
18308:20140912:134049.440 ====== Fatal information: ======
18308:20140912:134049.440 Program counter: 0x7fecf188cee2
18308:20140912:134049.440 === Registers: ===
18308:20140912:134049.440 r8 = 0 = 0 = 0
18308:20140912:134049.440 r9 = a = 10 = 10
18308:20140912:134049.440 r10 = 0 = 0 = 0
18308:20140912:134049.440 r11 = 1999999999999999 = 1844674407370955161 = 1844674407370955161
18308:20140912:134049.440 r12 = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 r13 = 7feced0a42b8 = 140655565882040 = 140655565882040
18308:20140912:134049.440 r14 = 7fecf2ce3168 = 140655662608744 = 140655662608744
18308:20140912:134049.440 r15 = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 rdi = 0 = 0 = 0
18308:20140912:134049.440 rsi = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 rbp = 7fff71c0faa0 = 140735101860512 = 140735101860512
18308:20140912:134049.440 rbx = 0 = 0 = 0
18308:20140912:134049.440 rdx = 0 = 0 = 0
18308:20140912:134049.440 rax = 0 = 0 = 0
Regards!
We have checked Zabbix 2.2.6 and server does not start.
We returned to more stable version 2.2.3.
We have this issue since version 2.2.4.
Zabbix server does not start because crashed.
Even though version 2.2.3 also is not stable because, though it starts normally, it crashed when server fails to acquire some items.
We have compiled Zabbix source in SLES 11 SP3 with this commad:
CFLAGS="-O2" \
CXX=gcc \
CXXFLAGS="-O2 -mtune=nocona -felide-constructors -fno-exceptions -fno-rtti" \
./configure --enable-server --enable-agent --with-mysql --with-libcurl --sysconfdir="/etc/zabbix"
And next I have attached first lines from log:
18308:20140912:134049.390 Starting Zabbix Server. Zabbix 2.2.6 (revision 48483).
18308:20140912:134049.390 ****** Enabled features ******
18308:20140912:134049.390 SNMP monitoring: NO
18308:20140912:134049.390 IPMI monitoring: NO
18308:20140912:134049.390 WEB monitoring: YES
18308:20140912:134049.390 VMware monitoring: NO
18308:20140912:134049.390 Jabber notifications: NO
18308:20140912:134049.390 Ez Texting notifications: YES
18308:20140912:134049.390 ODBC: NO
18308:20140912:134049.390 SSH2 support: NO
18308:20140912:134049.390 IPv6 support: NO
18308:20140912:134049.390 ******************************
18308:20140912:134049.390 using configuration file: /etc/zabbix/zabbix_server.conf
18308:20140912:134049.396 current database version (mandatory/optional): 02020000/02020001
18308:20140912:134049.396 required mandatory version: 02020000
18308:20140912:134049.440 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...18308:20140912:134049.440 ====== Fatal information: ======
18308:20140912:134049.440 Program counter: 0x7fecf188cee2
18308:20140912:134049.440 === Registers: ===
18308:20140912:134049.440 r8 = 0 = 0 = 0
18308:20140912:134049.440 r9 = a = 10 = 10
18308:20140912:134049.440 r10 = 0 = 0 = 0
18308:20140912:134049.440 r11 = 1999999999999999 = 1844674407370955161 = 1844674407370955161
18308:20140912:134049.440 r12 = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 r13 = 7feced0a42b8 = 140655565882040 = 140655565882040
18308:20140912:134049.440 r14 = 7fecf2ce3168 = 140655662608744 = 140655662608744
18308:20140912:134049.440 r15 = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 rdi = 0 = 0 = 0
18308:20140912:134049.440 rsi = fffffffffffffffc = 18446744073709551612 = -4
18308:20140912:134049.440 rbp = 7fff71c0faa0 = 140735101860512 = 140735101860512
18308:20140912:134049.440 rbx = 0 = 0 = 0
18308:20140912:134049.440 rdx = 0 = 0 = 0
18308:20140912:134049.440 rax = 0 = 0 = 0
Regards!