[ZBX-5031] zabbix java gateway appears to crash zabbix server in 2.0.0rc5 Created: 2012 May 21  Updated: 2017 May 30  Resolved: 2012 Jul 23

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Java gateway (J), Server (S)
Affects Version/s: 2.0.0rc5
Fix Version/s: 2.0.2rc2, 2.1.0

Type: Incident report Priority: Major
Reporter: Patrick O'Brien Assignee: Unassigned
Resolution: Fixed Votes: 1
Labels: crash, jmx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

os: Scientific Linux release 6.0 (Carbon)
kernel: 2.6.32-71.el6.x86_64
virtual hardware: KVM, [email protected], 2GB Memory
hypervisor hardware: Dell PowerEdge M610, [email protected], 48GB Memory, 18 guests total


Attachments: Text File zabbix_server.log     File zabbix_server.log-2.0.0-official     File zabbix_server.objdump.tgz    
Issue Links:
Duplicate
is duplicated by ZBX-5206 Zabbix server constantly crash after ... Closed
is duplicated by ZBX-5297 Adding two JMX interfaces to monitore... Closed
is duplicated by ZBX-5350 Zabbix server silently crashed Closed

 Description   

I looked back through the bug history and couldn't find anything related to this. After a few seconds of running zabbix server with the java gateway enabled, zabbix server crashes.

Attached is the log file for zabbix_server from a crash, as well as the objdump of zabbix_server, as requested in the crash log.



 Comments   
Comment by Alexei Vladishev [ 2012 May 23 ]

Thanks for the details, we are working on it. Meanwhile, if possible, try to use the official 2.0.0 and report back if it works.

Comment by Patrick O'Brien [ 2012 May 24 ]

Hey Alexei,

The official 2.0.0 version worked a bit better (and by better I mean it ran longer before crashing) than rc5, although we still saw some crashes. I ran zabbix_server in debug mode, although it doesn't appear that added any additional information from the crash. Attached is the log for the latest crash.

Here are our configure options:
%configure \
--with-mysql \
--with-libcurl \
--with-openipmi \
--with-jabber \
--enable-server \
--enable-proxy \
--enable-agent \
--enable-java \
--with-net-snmp \
--prefix=%{_sysconfdir} \
--exec-prefix=%{_prefix} \
--bindir=%{_bindir} \
--sbindir=%{_sbindir} \
--mandir=%{_mandir} \
--libdir=%{_libdir} \
--sysconfdir=%{_sysconfdir}

Comment by Patrick O'Brien [ 2012 May 30 ]

Hey Alexander,

Let me know if there's any more information you want/need for this issue and I'll gladly get it to you.

Comment by Ricardo Reyes [ 2012 Jun 26 ]

It's happening to me too with Zabbix 2.0.0, monitoring a tomcat server through a proxy. As soon as the proxy sends data to the server, the server process crashes. The problem stopped only when I removed all JMX items from every host.

My server version:

Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: Starting Zabbix Server. Zabbix 2.0.0 (revision 27675).
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: ****** Enabled features ******
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: SNMP monitoring: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: IPMI monitoring: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: WEB monitoring: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: Jabber notifications: NO
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: Ez Texting notifications: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: ODBC: NO
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: SSH2 support: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: IPv6 support: YES
Jun 26 12:03:12 PHSRVBACKUP Zabbix server[31905]: ******************************

Comment by richlv [ 2012 Jul 09 ]

another jmx related crash : ZBX-5297

Comment by Oleksii Zagorskyi [ 2012 Jul 19 ]

Same crash here:

8685:20120718:110600.375 item [dmz01:jmx["java.lang:type=Memory","HeapMemoryUsage.used"]] became not supported: Connection
refused to host: 192.168.0.100; nested exception is:
java.net.ConnectException: Connection refused
8685:20120718:110600.479 Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ...
8685:20120718:110600.479 ====== Fatal information: ======
...
8685:20120718:110600.479 === Backtrace: ===
8685:20120718:110600.480 12: /opt/zabbix/sbin/zabbix_server(print_fatal_info+0x277) [0x448017]
8685:20120718:110600.480 11: /opt/zabbix/sbin/zabbix_server() [0x44750c]
8685:20120718:110600.480 10: /lib64/libc.so.6() [0x37e2832900]
8685:20120718:110600.480 9: /lib64/libc.so.6() [0x37e2924cba]
8685:20120718:110600.480 8: /opt/zabbix/sbin/zabbix_server() [0x43bcb2]
8685:20120718:110600.480 7: /opt/zabbix/sbin/zabbix_server(DCconfig_set_trigger_value+0x5f) [0x43bd2f]
8685:20120718:110600.480 6: /opt/zabbix/sbin/zabbix_server(DCflush_nextchecks+0x338) [0x43a008]
8685:20120718:110600.480 5: /opt/zabbix/sbin/zabbix_server(DCsync_history+0x13dc) [0x43920c]
8685:20120718:110600.480 4: /opt/zabbix/sbin/zabbix_server(main_dbsyncer_loop+0xe7) [0x4127c7]
8685:20120718:110600.480 3: /opt/zabbix/sbin/zabbix_server(MAIN_ZABBIX_ENTRY+0xa26) [0x411a96]
8685:20120718:110600.480 2: /opt/zabbix/sbin/zabbix_server(daemon_start+0x22f) [0x44724f]
8685:20120718:110600.480 1: /lib64/libc.so.6(__libc_start_main+0xfd) [0x37e281ecdd]
8685:20120718:110600.480 0: /opt/zabbix/sbin/zabbix_server() [0x40d5d9]
...
8657:20120718:110600.485 One child process died (PID:8685,exitcode/signal:255). Exiting ...
8657:20120718:110602.488 syncing history data...
8657:20120718:110602.495 syncing history data done
8657:20120718:110602.495 syncing trends data...
8657:20120718:110602.592 syncing trends data done
8657:20120718:110602.592 Zabbix Server stopped. Zabbix 2.0.1 (revision 28455).

Comment by Alexander Vladishev [ 2012 Jul 23 ]

Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-5031

Comment by dimir [ 2012 Jul 24 ]

Successfully tested.

Comment by Alexander Vladishev [ 2012 Jul 24 ]

Fixed in pre-2.0.2 r29130 and pre-2.1.0 (beta) r29131

Generated at Wed Jan 08 08:22:58 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.