Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-4726

One child process died (PID:18548,exitcode/signal:1).

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • None
    • 1.8.10
    • Server (S)
    • Zabbix 1.8.10
      DB2 V9.7.5 64Bit
      Centos6 64Bit

      18547:20120302:091448.594 Starting Zabbix Server. Zabbix 1.8.10 (revision 24303).
      18547:20120302:091448.594 ****** Enabled features ******
      18547:20120302:091448.594 SNMP monitoring: YES
      18547:20120302:091448.594 IPMI monitoring: NO
      18547:20120302:091448.594 WEB monitoring: YES
      18547:20120302:091448.594 Jabber notifications: NO
      18547:20120302:091448.594 Ez Texting notifications: YES
      18547:20120302:091448.594 ODBC: NO
      18547:20120302:091448.594 SSH2 support: YES
      18547:20120302:091448.594 IPv6 support: YES
      18547:20120302:091448.594 ******************************
      18547:20120302:091448.594 In DBconnect() flag:0
      18547:20120302:091448.655 One child process died (PID:18548,exitcode/signal:1). Exiting ...
      18547:20120302:091448.655 zbx_on_exit() called
      18547:20120302:091450.655 In DBconnect() flag:1
      18547:20120302:091450.672 query [txnlev:0] [set current schema='zabbix']
      18547:20120302:091450.672 End of DBconnect():0
      18547:20120302:091450.672 In free_database_cache()
      18547:20120302:091450.673 In DCsync_all()
      18547:20120302:091450.673 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x90]. Crashing ...

            Unassigned Unassigned
            byteschubser Uwe Kiewel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: