[ZBX-8177] Zabbix_proxy fails with signal SIGFPE while starting Created: 2014 May 06  Updated: 2017 May 30  Resolved: 2014 May 07

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P)
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Wojciech Korzenny Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: crash, proxy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS:
Red Hat Enterprise Linux Server release 6.4 (Santiago)
x86_64, 2.6.32-358.el6.x86_64

Installed packages:

#rpm -qa | grep zabb
zabbix-proxy-mysql-2.2.2-1.el6.x86_64
zabbix-2.2.2-1.el6.x86_64
zabbix-proxy-2.2.2-1.el6.x86_64

  1. zabbix_proxy -V
    Zabbix proxy v2.2.2 (revision 42525) (12 February 2014)
    Compilation time: Feb 15 2014 16:31:32
  1. grep -v "$|#" /etc/zabbix/zabbix_proxy.conf

Server=zabbix_host
Hostname=proxy_server
LogFile=/apps/zabbix/zabbix_proxy.log
LogFileSize=0
PidFile=/apps/zabbix/zabbix_proxy.pid
DBHost=dbhost
DBName=zabbix
DBUser=zabbix
DBPassword=zabbix
DBSocket=/var/lib/mysql/mysql.sock
StartPollers=50
StartPollersUnreachable=10
StartTrappers=15
StartPingers=1
StartDiscoverers=2
JavaGateway=localhost
JavaGatewayPort=10052
StartJavaPollers=4
CacheSize=512M

Attachments: File objdump_zabbix_proxy.log.gz     Text File zabbix_proxy.log    
Issue Links:
Duplicate
duplicates ZBX-8102 zabbix_proxy crash - sigfpe Closed
is duplicated by ZBX-8494 Proxy crashes if started with server ... Closed

 Description   

Zabbix_proxy fails with error:

29305:20140505:061759.508 Starting Zabbix Proxy (active) [vplab082.dev.sabre.com]. Zabbix 2.2.2 (revision 42525).
29305:20140505:061759.509 **** Enabled features ****
29305:20140505:061759.509 SNMP monitoring: YES
29305:20140505:061759.509 IPMI monitoring: YES
29305:20140505:061759.509 WEB monitoring: YES
29305:20140505:061759.509 VMware monitoring: YES
29305:20140505:061759.509 ODBC: YES
29305:20140505:061759.509 SSH2 support: YES
29305:20140505:061759.509 IPv6 support: YES
29305:20140505:061759.509 **************************
29305:20140505:061759.509 using configuration file: /etc/zabbix/zabbix_proxy.conf
29305:20140505:061759.521 current database version (mandatory/optional): 02020000/02020000
29305:20140505:061759.521 required mandatory version: 02020000
29305:20140505:061804.859 Got signal [signal:8(SIGFPE),reason:1,refaddr:0x44be7d]. Crashing ...

Same behavior for 2.2.1 release.

Logs in attachment:

  • zabbix_proxy.log - zabbix proxy log
  • objdump_zabbix_proxy.log.gz (output from command: objdump -DSswx /usr/sbin/zabbix_proxy)

 Comments   
Comment by Aleksandrs Saveljevs [ 2014 May 06 ]

Looks the same as ZBX-8102. Is the database parameter correct?

Comment by Wojciech Korzenny [ 2014 May 06 ]

They are correct. When they are not corrent, I got an exception for example:

[Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix2'@'zabbix_proxy' (using password: YES)
18139:20140506:064537.511 Database is down.

Parameter DBHost=dbhost definitely points to local db (dedicated for zabbix proxy) not for zabbix-server db.

What's more - backtrace in log is different (shorter) than reported in ZBX-8102:

29305:20140505:061804.860 === Backtrace: ===
29305:20140505:061804.861 9: zabbix_proxy(print_fatal_info+0x280) [0x459220]
29305:20140505:061804.861 8: zabbix_proxy() [0x45994c]
29305:20140505:061804.861 7: /lib64/libc.so.6() [0x32ed832920]
29305:20140505:061804.861 6: zabbix_proxy() [0x44be7d]
29305:20140505:061804.861 5: zabbix_proxy(DCsync_configuration+0x1687) [0x44e117]
29305:20140505:061804.861 4: zabbix_proxy(MAIN_ZABBIX_ENTRY+0x1de) [0x412d6e]
29305:20140505:061804.861 3: zabbix_proxy(daemon_start+0x1cd) [0x45862d]
29305:20140505:061804.861 2: zabbix_proxy(main+0x2f6) [0x413906]
29305:20140505:061804.861 1: /lib64/libc.so.6(__libc_start_main+0xfd) [0x32ed81ecdd]
29305:20140505:061804.861 0: zabbix_proxy() [0x412499]

Comment by richlv [ 2014 May 07 ]

what asaveljevs meant, is that really a proxy database, not having any data from the server dataset ?
how exactly was the database created ?

Comment by Wojciech Korzenny [ 2014 May 07 ]

DB that proxy uses is a copy of database that zabbix server used before.

Is it a db that I should use or I ought to create clean database created by script schema.sql?

Comment by Aleksandrs Saveljevs [ 2014 May 07 ]

Yes, you should create a clean database using schema.sql. Scripts images.sql and data.sql should not be imported.

Comment by richlv [ 2014 May 07 ]

right. proxies should not be pointed at server db.
closing.

Generated at Thu Jun 05 22:10:55 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.