[ZBX-12581] Got signal [signal:11(SIGSEGV),reason:1,refaddr:(nil)]. Crashing ... Created: 2017 Aug 23 Updated: 2024 Apr 10 Resolved: 2017 Aug 24 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 3.4.0 |
Fix Version/s: | 3.4.1rc1, 3.4 (plan) |
Type: | Problem report | Priority: | Blocker |
Reporter: | azhrusc | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() ![]() |
||||||||
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | Sprint 15 | ||||||||
Story Points: | 1 |
Description |
Unable to start zabbix-server after upgrade from 3.2.7 to 3.4.0 (using rpm's on centos 7.3.1611) |
Comments |
Comment by Vladislavs Sokurenko [ 2017 Aug 23 ] |
Thanks for the report, I don't see no crash in the log, could you please double check |
Comment by azhrusc [ 2017 Aug 23 ] |
Oops sorry cut the wrong stuff out, uploaded a new version vso thanks, could you please also increase debug level for configuration syncer and attach log ?
./sbin/zabbix_server -R log_level_increase="configuration syncer"
|
Comment by Vladislavs Sokurenko [ 2017 Aug 23 ] |
I am sorry, which database are you using, is it MySQL ? |
Comment by azhrusc [ 2017 Aug 23 ] |
he's looking for a pid-file, obviously there is no one..? -bash-4.2$ ./sbin/zabbix_server -R log_level_increase="configuration syncer" zabbix_server [10422]: cannot open PID file [/var/run/zabbix/zabbix_server.pid]: [2] No such file or directory Please try
zabbix_server -c /usr/local/etc/zabbix_server.conf -R log_level_increase="configuration syncer"
|
Comment by azhrusc [ 2017 Aug 23 ] |
we are using postgresql, version 9.5 |
Comment by azhrusc [ 2017 Aug 23 ] |
zabbix=# \d+ operations Table "public.operations" Column | Type | Modifiers | Storage | Stats target | Description ---------------+------------------------+-----------------------------------------+----------+--------------+------------- operationid | bigint | not null | plain | | actionid | bigint | not null | plain | | operationtype | integer | not null default 0 | plain | | esc_period | character varying(255) | not null default '0'::character varying | extended | | esc_step_from | integer | not null default 1 | plain | | esc_step_to | integer | not null default 1 | plain | | evaltype | integer | not null default 0 | plain | | recovery | integer | not null default 0 | plain | | Indexes: "operations_pkey" PRIMARY KEY, btree (operationid) "operations_1" btree (actionid) Foreign-key constraints: "c_operations_1" FOREIGN KEY (actionid) REFERENCES actions(actionid) ON DELETE CASCADE Referenced by: TABLE "opcommand" CONSTRAINT "c_opcommand_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opcommand_grp" CONSTRAINT "c_opcommand_grp_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opcommand_hst" CONSTRAINT "c_opcommand_hst_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opconditions" CONSTRAINT "c_opconditions_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opgroup" CONSTRAINT "c_opgroup_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opinventory" CONSTRAINT "c_opinventory_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opmessage" CONSTRAINT "c_opmessage_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opmessage_grp" CONSTRAINT "c_opmessage_grp_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "opmessage_usr" CONSTRAINT "c_opmessage_usr_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE TABLE "optemplate" CONSTRAINT "c_optemplate_1" FOREIGN KEY (operationid) REFERENCES operations(operationid) ON DELETE CASCADE |
Comment by Glebs Ivanovskis (Inactive) [ 2017 Aug 23 ] |
Would you be so kind to run this query? select a.actionid,o.recovery from actions a left join operations o on a.actionid=o.actionid where a.status=0 group by a.actionid,o.recovery order by a.actionid; |
Comment by Andris Zeila [ 2017 Aug 24 ] |
There should not be actions without operations, but still crashing is not good. Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-12581 For now as a workaround you can find the actions without operations (for example with: select a.actionid,a.name from actions a where not exists (select NULL from operations o where o.actionid=a.actionid); ) and either disable, remove or fix them. |
Comment by Viktors Tjarve [ 2017 Aug 24 ] |
Successfully tested. |
Comment by Andris Zeila [ 2017 Aug 24 ] |
Released in:
|
Comment by Glebs Ivanovskis (Inactive) [ 2017 Aug 24 ] |
Backtrace from attached zabbix_server.log.gz 16976:20170823:155109.388 === Backtrace: === 16976:20170823:155109.389 11: /usr/sbin/zabbix_server(zbx_log_fatal_info+0x13c) [0x7fa3a394a250] 16976:20170823:155109.389 10: /usr/sbin/zabbix_server(+0xe9665) [0x7fa3a394a665] 16976:20170823:155109.389 9: /lib64/libc.so.6(+0x35250) [0x7fa3a0374250] 16976:20170823:155109.389 8: /lib64/libc.so.6(+0x39d47) [0x7fa3a0378d47] 16976:20170823:155109.389 7: /lib64/libc.so.6(atoi+0x10) [0x7fa3a0375750] 16976:20170823:155109.389 6: /usr/sbin/zabbix_server(zbx_dbsync_compare_action_ops+0x9d) [0x7fa3a393b171] 16976:20170823:155109.389 5: /usr/sbin/zabbix_server(DCsync_configuration+0x97e) [0x7fa3a39285f8] 16976:20170823:155109.389 4: /usr/sbin/zabbix_server(MAIN_ZABBIX_ENTRY+0x586) [0x7fa3a38a0b3f] 16976:20170823:155109.389 3: /usr/sbin/zabbix_server(daemon_start+0x325) [0x7fa3a3949996] 16976:20170823:155109.389 2: /usr/sbin/zabbix_server(main+0x317) [0x7fa3a38a05b7] 16976:20170823:155109.389 1: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa3a0360b35] 16976:20170823:155109.389 0: /usr/sbin/zabbix_server(+0x338c9) [0x7fa3a38948c9] |