Ad Widget

Collapse

Weird crash on Zabbix22 FreeBSD 10 port

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JohnnySSH
    Junior Member
    • Sep 2014
    • 6

    #1

    Weird crash on Zabbix22 FreeBSD 10 port

    Hi,

    I installed Zabbix 2.2 on FreeBSD 10.0 RELEASE x64.

    It was running fine until I enabled email. After the server sent one email using a Trigger and Action I created it some how managed to segfault and now I'm unable to start it again....? I've also done a full update too of installed packages/libraries.

    Here is the output from the log:

    Code:
      3286:20140917:230404.186 server #35 started [history syncer #6]
      3222:20140917:230404.189 server #0 started [main process]
      3296:20140917:230404.191 server #39 started [proxy poller #1]
      3299:20140917:230404.192 server #40 started [self-monitoring #1]
      3289:20140917:230404.194 server #37 started [history syncer #8]
      3279:20140917:230404.195 server #29 started [discoverer #1]
      3279:20140917:230404.225 cannot link template: template with item key "sysName" already linked to the host
      3279:20140917:230404.230 cannot link template: template with item key "sysName" already linked to the host
      3267:20140917:230404.297 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x40]. Crashing ...
      3267:20140917:230404.297 ====== Fatal information: ======
      3267:20140917:230404.297 program counter not available for this architecture
      3267:20140917:230404.297 === Registers: ===
      3267:20140917:230404.297 register dump not available for this architecture
      3267:20140917:230404.297 === Backtrace: ===
      3267:20140917:230404.297 1: 0x45549b <print_fatal_info+0x7b> at /usr/local/sbin/zabbix_server
      3267:20140917:230404.297 0: 0x4558fc <zbx_set_common_signal_handlers+0x2fc> at /usr/local/sbin/zabbix_server
      3267:20140917:230404.297 === Memory map: ===
      3267:20140917:230404.297 memory map not available for this platform
      3267:20140917:230404.297 ================================
      3222:20140917:230404.298 One child process died (PID:3267,exitcode/signal:65280). Exiting ...
      3222:20140917:230406.323 syncing history data...
      3222:20140917:230406.323 syncing history data done
      3222:20140917:230406.323 syncing trends data...
      3222:20140917:230406.323 syncing trends data done
      3222:20140917:230406.323 Zabbix Server stopped. Zabbix 2.2.5 (revision 47411).
    Would anyone be able to offer any assistance?

    Actually things were just getting juicy as I had just configured the ZAX/Pubnub alerting system, though it didn't work.

    Really hoping that I can get this back up and running again as in the few days I had it running it was really good, though learning curve for creating events etc... might have been a bit steepish but all good fun

    Thanks.
  • JohnnySSH
    Junior Member
    • Sep 2014
    • 6

    #2
    Digging around a bit it seems that this is directly related to this bug:



    basically the issue is somewhere to do with the "Jabber" plugin.

    Just to post a quick diff of the Makefile:

    Code:
    OPTIONSFILE=    ${PORT_DBDIR}/${PORTNAME}${PKGNAMESUFFIX}/opt   OPTIONSFILE=    ${PORT_DBDIR}/${PORTNAME}${PKGNAMESUFFIX}/opt
    
    OPTIONS_DEFINE= IPV6 FPING CURL LDAP IPMI SSH NMAP JAVAGW LIB | OPTIONS_DEFINE= IPV6 FPING JABBER CURL LDAP IPMI SSH NMAP JAV
    OPTIONS_DEFAULT=        MYSQL IPV6 FPING CURL UNIXODBC        | OPTIONS_DEFAULT=        MYSQL IPV6 FPING JABBER CURL UNIXODBC
    OPTIONS_SUB=    yes                                             OPTIONS_SUB=    yes
    Compiling without Jabber support makes the system work again, though the credit goes to the link provided as it's mentioned there.

    Comment

    Working...