Thank you. I am working on this with Zabbix developers. — Juraj Lutter <otis%NetBSD.org@localhost> pkgsrc committer > On 19 Aug 2020, at 11:20, Yuuki Enomoto <uki%e-yuuki.org@localhost> wrote: > > In my environment (NetBSD 9 stable/amd64), backtrace hasn't been shown. > I installed latest wip/zabbix50-server package (7f5ef15f). But I've > never seen backtrace like it. > > This is full zabbix_server.log: > > 27272:20200819:180801.330 Starting Zabbix Server. Zabbix 5.0.2 (revision 352ca05870). > 27272:20200819:180801.330 ****** Enabled features ****** > 27272:20200819:180801.330 SNMP monitoring: YES > 27272:20200819:180801.330 IPMI monitoring: NO > 27272:20200819:180801.330 Web monitoring: YES > 27272:20200819:180801.330 VMware monitoring: YES > 27272:20200819:180801.330 SMTP authentication: YES > 27272:20200819:180801.330 ODBC: NO > 27272:20200819:180801.330 SSH support: YES > 27272:20200819:180801.330 IPv6 support: YES > 27272:20200819:180801.330 TLS support: YES > 27272:20200819:180801.330 ****************************** > 27272:20200819:180801.330 using configuration file: /usr/pkg/etc/zabbix_server.conf > 27272:20200819:180801.337 current database version (mandatory/optional): 05000000/05000001 > 27272:20200819:180801.337 required mandatory version: 05000000 > 27272:20200819:180801.347 database is not upgraded to use double precision values > 27272:20200819:180801.353 server #0 started [main process] > 27383:20200819:180801.354 server #1 started [configuration syncer #1] > 27413:20200819:180801.463 server #2 started [housekeeper #1] > 25124:20200819:180801.464 server #5 started [discoverer #1] > 27733:20200819:180801.465 server #6 started [history syncer #1] > 27908:20200819:180801.465 server #8 started [history syncer #3] > 3023:20200819:180801.466 server #14 started [poller #1] > 27418:20200819:180801.466 server #13 started [task manager #1] > 27534:20200819:180801.467 server #3 started [timer #1] > 27894:20200819:180801.483 server #18 started [poller #5] > 27547:20200819:180801.483 server #9 started [history syncer #4] > 1838:20200819:180801.483 server #16 started [poller #3] > 28121:20200819:180801.483 server #20 started [trapper #1] > 26976:20200819:180801.525 server #12 started [self-monitoring #1] > 24640:20200819:180801.525 server #23 started [trapper #4] > 24253:20200819:180801.525 server #30 started [preprocessing manager #1] > 25715:20200819:180801.528 server #15 started [poller #2] > 27728:20200819:180801.528 server #36 started [lld worker #2] > 25041:20200819:180801.528 server #25 started [icmp pinger #1] > 25376:20200819:180801.529 server #11 started [proxy poller #1] > 27272:20200819:180801.529 One child process died (PID:25041,exitcode/signal:4). Exiting ... > 27484:20200819:180801.529 server #4 started [http poller #1] > 28044:20200819:180801.530 server #35 started [lld worker #1] > 27955:20200819:180801.530 server #21 started [trapper #2] > 27277:20200819:180801.531 server #7 started [history syncer #2] > 27951:20200819:180801.531 server #24 started [trapper #5] > 27850:20200819:180801.532 server #17 started [poller #4] > 14279:20200819:180801.532 server #27 started [alerter #1] > 27753:20200819:180801.582 server #19 started [unreachable poller #1] > 27425:20200819:180801.582 server #22 started [trapper #3] > 28070:20200819:180801.582 server #26 started [alert manager #1] > 27602:20200819:180801.583 server #37 started [alert syncer #1] > 27929:20200819:180801.583 server #28 started [alerter #2] > 27480:20200819:180801.583 server #10 started [escalator #1] > 25980:20200819:180801.584 server #29 started [alerter #3] > 27870:20200819:180801.584 server #34 started [lld manager #1] > 27272:20200819:180801.635 syncing trend data... > 27272:20200819:180801.635 syncing trend data done > 27272:20200819:180801.635 cannot remove shared memory for self-monitoring collector: [22] Invalid argument > 27272:20200819:180801.636 Zabbix Server stopped. Zabbix 5.0.2 (revision 352ca05870). > > Thank you, > > On Tue, Aug 18, 2020 at 07:59:03PM +0200, Juraj Lutter wrote: >> This error message is only a side effect of the crash. >> >> The actual backtrace is: >> >> 58083:20200818:175513.525 18: /opt/local/sbin/zabbix_server'zbx_backtrace+0x3e [0x593e5e] >> 58083:20200818:175513.525 17: /opt/local/sbin/zabbix_server'zbx_log_fatal_info+0x29d [0x59420d] >> 58083:20200818:175513.525 16: /opt/local/sbin/zabbix_server'fatal_signal_handler+0x1e [0x5946be] >> 58083:20200818:175513.525 15: /lib/amd64/libc.so.1'__sighndlr+0x6 [0xfffffc7fef110676] >> 58083:20200818:175513.525 14: /lib/amd64/libc.so.1'call_user_handler+0x1db [0xfffffc7fef102fcb] >> 58083:20200818:175513.525 13: /opt/local/sbin/zabbix_server'duk_heap_strtable_intern+0x49 [0x4dba39] >> 58083:20200818:175513.525 12: /opt/local/sbin/zabbix_server'duk_heap_strtable_intern_checked+0x15 [0x4dc545] >> 58083:20200818:175513.525 11: /opt/local/sbin/zabbix_server'duk_push_lstring+0x2c [0x4dc59c] >> 58083:20200818:175513.525 10: /opt/local/sbin/zabbix_server'duk__load_func+0x2ab [0x4ef75b] >> 58083:20200818:175513.526 9: /opt/local/sbin/zabbix_server'duk_load_function+0x43 [0x4efa93] >> 58083:20200818:175513.526 8: /opt/local/sbin/zabbix_server'zbx_es_execute+0x18f [0x4cb73f] >> 58083:20200818:175513.526 7: /opt/local/sbin/zabbix_server'zbx_item_preproc+0xb34 [0x4ca5c4] >> 58083:20200818:175513.526 6: /opt/local/sbin/zabbix_server'preprocessing_worker_thread+0x605 [0x4c5e25] >> 58083:20200818:175513.526 5: /opt/local/sbin/zabbix_server'zbx_thread_start+0x2a [0x59e53a] >> 58083:20200818:175513.526 4: /opt/local/sbin/zabbix_server'MAIN_ZABBIX_ENTRY+0x73c [0x47de0c] >> 58083:20200818:175513.526 3: /opt/local/sbin/zabbix_server'daemon_start+0x1b2 [0x593c12] >> 58083:20200818:175513.526 2: /opt/local/sbin/zabbix_server'main+0x426 [0x47e5c6] >> 58083:20200818:175513.526 1: /opt/local/sbin/zabbix_server'_start_crt+0x83 [0x47d103] >> 58083:20200818:175513.526 0: /opt/local/sbin/zabbix_server'_start+0x18 [0x47d068] >> >> and program counter is 4dba39, that is, it crashed in function duk_heap_strtable_intern(), in this case. >> >> >> The reason is unknown yet. >> >> Could you also share your backtrace, eventually? >> >> Thanks. >> >> — >> Juraj Lutter <otis%NetBSD.org@localhost> >> pkgsrc committer >> >>> On 18 Aug 2020, at 19:07, Juraj Lutter <otis%NetBSD.org@localhost> wrote: >>> >>> Only a quick update: >>> >>> The same error also happens on SmartOS: >>> >>> cannot remove shared memory for self-monitoring collector: [22] Invalid argument >>> >>> — >>> Juraj Lutter <otis%NetBSD.org@localhost> >>> pkgsrc committer >>> >>>> On 18 Aug 2020, at 17:14, Juraj Lutter <otis%NetBSD.org@localhost> wrote: >>>> >>>> Hi, >>>> >>>>> On 17 Aug 2020, at 14:52, Yuuki Enomoto <uki%e-yuuki.org@localhost> wrote: >>>>> >>>>> Hello, >>>>> >>> >> > > -- > Yuuki Enomoto <uki%e-yuuki.org@localhost> > B684 4BF2 9CD4 961F 510A 8121 7B4D FF44 2348 20B8
Attachment:
signature.asc
Description: Message signed with OpenPGP