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

One child process died

    XMLWordPrintable

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Critical
    • Resolution: Cannot Reproduce
    • Affects Version/s: 3.0.1, 3.0.2
    • Fix Version/s: None
    • Component/s: Proxy (P), Server (S)
    • Labels:
      None
    • Environment:
      FreeBSD 10.1

      Description

         872:20160412:171816.128 Starting Zabbix Server. Zabbix 3.0.1 (revision 58734).
         872:20160412:171816.128 ****** Enabled features ******
         872:20160412:171816.128 SNMP monitoring:           YES
         872:20160412:171816.128 IPMI monitoring:           YES
         872:20160412:171816.128 Web monitoring:            YES
         872:20160412:171816.128 VMware monitoring:          NO
         872:20160412:171816.128 SMTP authentication:       YES
         872:20160412:171816.128 Jabber notifications:      YES
         872:20160412:171816.128 Ez Texting notifications:  YES
         872:20160412:171816.128 ODBC:                      YES
         872:20160412:171816.128 SSH2 support:              YES
         872:20160412:171816.128 IPv6 support:              YES
         872:20160412:171816.128 TLS support:               YES
         872:20160412:171816.128 ******************************
         872:20160412:171816.128 using configuration file: /usr/local/etc/zabbix3/zabbix_server.conf
         872:20160412:171816.143 current database version (mandatory/optional): 03000000/03000000
         872:20160412:171816.143 required mandatory version: 03000000
         872:20160412:171816.157 server #0 started [main process]
         873:20160412:171816.164 server #1 started [configuration syncer #1]
         874:20160412:171816.164 server #2 started [db watchdog #1]
         881:20160412:171816.165 server #9 started [trapper #1]
         882:20160412:171816.168 server #10 started [trapper #2]
         883:20160412:171816.169 server #11 started [trapper #3]
         884:20160412:171816.170 server #12 started [trapper #4]
         885:20160412:171816.172 server #13 started [trapper #5]
         887:20160412:171816.174 server #15 started [alerter #1]
         888:20160412:171816.178 server #16 started [housekeeper #1]
         889:20160412:171816.178 server #17 started [timer #1]
         890:20160412:171816.178 server #18 started [http poller #1]
         892:20160412:171816.180 server #20 started [history syncer #1]
         893:20160412:171816.180 server #21 started [history syncer #2]
         894:20160412:171816.180 server #22 started [history syncer #3]
         895:20160412:171816.181 server #23 started [history syncer #4]
         896:20160412:171816.181 server #24 started [escalator #1]
         897:20160412:171816.181 server #25 started [proxy poller #1]
         872:20160412:171816.188 One child process died (PID:875,exitcode/signal:4). Exiting ...
         898:20160412:171816.189 server #26 started [self-monitoring #1]
         872:20160412:171818.217 syncing history data...
         872:20160412:171818.217 syncing history data done
         872:20160412:171818.217 syncing trends data...
         872:20160412:171818.218 syncing trends data done
         872:20160412:171818.218 Zabbix Server stopped. Zabbix 3.0.1 (revision 58734).
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              tbiryukov Biryukov Timofey
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: