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

Server crash. [signal:11(SIGSEGV),reason:1,refaddr:0x0] - in "zabbix trapper"

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.2rc1, 2.3.0
    • Component/s: Server (S)
    • Labels:
    • Environment:

      Description

      7225:20140104:111350.830 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x0]. Crashing ...
      7225:20140104:111350.830 ====== Fatal information: ======
      7225:20140104:111350.830 program counter not available for this architecture
      7225:20140104:111350.830 === Registers: ===
      7225:20140104:111350.830 register dump not available for this architecture
      7225:20140104:111350.830 === Backtrace: ===
      7225:20140104:111350.830 backtrace not available for this platform
      7225:20140104:111350.830 === Memory map: ===
      7225:20140104:111350.843 memory map not available for this platform
      7225:20140104:111350.844 ================================
      7180:20140104:111350.885 One child process died (PID:7225,exitcode/signal:65280). Exiting ...
      7180:20140104:111352.895 syncing history data...
      7180:20140104:111352.944 syncing history data done
      7180:20140104:111352.944 syncing trends data...
      7180:20140104:111355.495 syncing trends data done
      7180:20140104:111355.495 Zabbix Server stopped. Zabbix 2.2.1 (revision 40808).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                s.vekli@hitel.ru Vekli Sergey
              • Votes:
                1 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: