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

One child process died (PID:8437,exitcode/signal:255)

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Cannot Reproduce
    • Icon: Critical Critical
    • None
    • 1.8.16
    • Server (S)
    • Zabbix 1.8.10
      Oracle Database 11g Enterprise Edition Release 11.2.0.3.0
      CentOS release 5.7 32Bit

      8437:20130919:085322.127 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x7549544d]. Crashing ...
      8437:20130919:085322.127 ====== Fatal information: ======
      (...)
      8437:20130919:085322.128 === Backtrace: ===
      8437:20130919:085322.129 3: /amb/local/zabbix/sbin/zabbix_server(print_fatal_info+0x310) [0x8088770]
      8437:20130919:085322.129 2: /amb/local/zabbix/sbin/zabbix_server [0x8087d64]
      8437:20130919:085322.129 1: [0xc86440]
      8437:20130919:085322.129 0: [0x6f31535a]
      (...)
      8371:20130919:085322.153 One child process died (PID:8437,exitcode/signal:255). Exiting ...
      8371:20130919:085324.288 syncing history data...
      8371:20130919:085327.292 syncing history data done
      8371:20130919:085327.292 syncing trends data...
      8371:20130919:085421.769 syncing trends data done
      8371:20130919:085421.773 Zabbix Server stopped. Zabbix 1.8.10 (revision 24303).

        1. Log_erro_20130919.txt
          17 kB

            Unassigned Unassigned
            alereis Alexandro Reis Silva
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: