[ZBX-23333] Configuration syncer SQL failed Created: 2023 Aug 29  Updated: 2024 Apr 10  Resolved: 2023 Aug 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 7.0.0alpha4
Fix Version/s: 7.0.0alpha5, 7.0 (plan)

Type: Problem report Priority: Critical
Reporter: Edgar Akhmetshin Assignee: Vladislavs Sokurenko
Resolution: Workaround proposed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team A
Sprint: Support backlog

 Description   

Steps to reproduce:

  1. install using docker (trunk branch)

Result:

  307:20230829:175928.010 server #75 started [snmp poller #1]
   306:20230829:175928.014 thread started
   307:20230829:175928.015 thread started
   305:20230829:175928.015 thread started
Bad operator (INTEGER): At line 73 in /var/lib/mibs/ietf/SNMPv2-PDU
Bad operator (INTEGER): At line 73 in /var/lib/mibs/ietf/SNMPv2-PDU
   239:20230829:175928.222 [1] thread started [preprocessing worker #1]
   239:20230829:175928.222 [2] thread started [preprocessing worker #2]
   239:20230829:175928.222 [3] thread started [preprocessing worker #3]
   246:20230829:175928.224 thread started [discovery worker #1]
   246:20230829:175928.224 thread started [discovery worker #2]
   246:20230829:175928.224 thread started [discovery worker #4]
   246:20230829:175928.224 thread started [discovery worker #5]
   246:20230829:175928.224 thread started [discovery worker #3]
zabbix_server [234]: ERROR [file and function: <dbconfig.c,zbx_dc_sync_configuration>, revision:7855d6f, line:7762] Something impossible has just happened.
   234:20230829:175937.847 === Backtrace: ===
   234:20230829:175937.848 9: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](zbx_backtrace+0x52) [0x55f9f609b882]
   234:20230829:175937.848 8: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](zbx_dc_sync_configuration+0x15bc) [0x55f9f5f54b1c]
   234:20230829:175937.848 7: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](dbconfig_thread+0x34a) [0x55f9f5e059ea]
   234:20230829:175937.848 6: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](zbx_thread_start+0x24) [0x55f9f5fd4f24]
   234:20230829:175937.848 5: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](+0x9b8e6) [0x55f9f5e038e6]
   234:20230829:175937.848 4: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](MAIN_ZABBIX_ENTRY+0xeef) [0x55f9f5e04e8f]
   234:20230829:175937.848 3: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](main+0x2c5) [0x55f9f5df9825]
   234:20230829:175937.848 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f2d9be49d90]
   234:20230829:175937.848 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f2d9be49e40]
   234:20230829:175937.848 0: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.022718 sec, syncing configuration](_start+0x25) [0x55f9f5e00865]
zabbix_server [234]: ERROR [file and function: <dbconfig.c,zbx_dc_sync_configuration>, revision:7855d6f, line:7762] Something impossible has just happened.
   234:20230829:175947.862 === Backtrace: ===
   234:20230829:175947.862 9: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](zbx_backtrace+0x52) [0x55f9f609b882]
   234:20230829:175947.862 8: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](zbx_dc_sync_configuration+0x15bc) [0x55f9f5f54b1c]
   234:20230829:175947.862 7: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](dbconfig_thread+0x34a) [0x55f9f5e059ea]
   234:20230829:175947.862 6: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](zbx_thread_start+0x24) [0x55f9f5fd4f24]
   234:20230829:175947.862 5: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](+0x9b8e6) [0x55f9f5e038e6]
   234:20230829:175947.862 4: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](MAIN_ZABBIX_ENTRY+0xeef) [0x55f9f5e04e8f]
   234:20230829:175947.862 3: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](main+0x2c5) [0x55f9f5df9825]
   234:20230829:175947.862 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f2d9be49d90]
   234:20230829:175947.862 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f2d9be49e40]
   234:20230829:175947.862 0: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.013146 sec, syncing configuration](_start+0x25) [0x55f9f5e00865]
zabbix_server [234]: ERROR [file and function: <dbconfig.c,zbx_dc_sync_configuration>, revision:7855d6f, line:7762] Something impossible has just happened.
   234:20230829:175957.876 === Backtrace: ===
   234:20230829:175957.877 9: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](zbx_backtrace+0x52) [0x55f9f609b882]
   234:20230829:175957.877 8: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](zbx_dc_sync_configuration+0x15bc) [0x55f9f5f54b1c]
   234:20230829:175957.877 7: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](dbconfig_thread+0x34a) [0x55f9f5e059ea]
   234:20230829:175957.877 6: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](zbx_thread_start+0x24) [0x55f9f5fd4f24]
   234:20230829:175957.877 5: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](+0x9b8e6) [0x55f9f5e038e6]
   234:20230829:175957.877 4: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](MAIN_ZABBIX_ENTRY+0xeef) [0x55f9f5e04e8f]
   234:20230829:175957.877 3: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](main+0x2c5) [0x55f9f5df9825]
   234:20230829:175957.877 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f2d9be49d90]
   234:20230829:175957.877 1: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f2d9be49e40]
   234:20230829:175957.877 0: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012077 sec, syncing configuration](_start+0x25) [0x55f9f5e00865]
zabbix_server [234]: ERROR [file and function: <dbconfig.c,zbx_dc_sync_configuration>, revision:7855d6f, line:7762] Something impossible has just happened.
   234:20230829:180007.898 === Backtrace: ===
   234:20230829:180007.899 9: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](zbx_backtrace+0x52) [0x55f9f609b882]
   234:20230829:180007.899 8: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](zbx_dc_sync_configuration+0x15bc) [0x55f9f5f54b1c]
   234:20230829:180007.899 7: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](dbconfig_thread+0x34a) [0x55f9f5e059ea]
   234:20230829:180007.899 6: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](zbx_thread_start+0x24) [0x55f9f5fd4f24]
   234:20230829:180007.899 5: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](+0x9b8e6) [0x55f9f5e038e6]
   234:20230829:180007.899 4: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](MAIN_ZABBIX_ENTRY+0xeef) [0x55f9f5e04e8f]
   234:20230829:180007.899 3: /usr/sbin/zabbix_server: configuration syncer [synced configuration in 0.012475 sec, syncing configuration](main+0x2c5) [0x55f9f5df9825]
   234:20230829:180007.899 2: /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f2d9be49d90]

Expected:
No errors.

 Comments   
Comment by Vladislavs Sokurenko [ 2023 Aug 29 ]

It's not crash, it reports that some query failed, please increase go level at least for configuration syncer and provide log

Comment by Vladislavs Sokurenko [ 2023 Aug 29 ] 
235:20230829:194841.456 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  column p.operating_mode does not exist
LINE 1: select p.proxyid,p.name,p.operating_mode,p.tls_connect,p.tls...
                                ^
 [select p.proxyid,p.name,p.operating_mode,p.tls_connect,p.tls_accept,p.tls_issuer,p.tls_subject,p.tls_psk_identity,p.tls_psk,p.allowed_addresses,p.address,p.port,pr.lastaccess from proxy p join proxy_rtdata pr on p.proxyid=pr.proxyid]
zabbix_server [235]: ERROR [file and function: <dbconfig.c,zbx_dc_sync_configuration>, revision:7855d6f, line:7762] Something impossible has just happened.
Comment by Vladislavs Sokurenko [ 2023 Aug 29 ]

Manually renaming field with name mode in proxy table to operating_mode should fix the issue, CLOSING issue as it only happen when updating to master before it is released and in that case it is suggested to manually rename proxy.mode field to proxy.operating_mode

Generated at Sat Apr 19 00:06:36 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.