Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 1.8.10
    • Fix Version/s: None
    • Component/s: Server (S)
    • Labels:
    • Environment:
      SuSE Linux Enterprise Server 10 SP4

      Description

      After an upgrade to the most recent stable version (1.8.10), zabbix_server process begun to crash several times during the last 24 hours. I attached the zabbix_server log and the dump of the zabbix_server binary.

      1. zabbix_server.dump.bz2
        4.15 MB
        Jerome Doucerain
      2. zabbix_server.log.20120224jd
        12 kB
        Jerome Doucerain

        Activity

        Hide
        Alexei Vladishev added a comment -

        Apologies for the long delay. Please tell me where where you are with this issue. Have you tried the latest 1.8.14, which I believe contains fixes for a couple of rare crash related issues.

        Show
        Alexei Vladishev added a comment - Apologies for the long delay. Please tell me where where you are with this issue. Have you tried the latest 1.8.14, which I believe contains fixes for a couple of rare crash related issues.
        Hide
        Jerome Doucerain added a comment -

        No problem for the delay. We did 2 things to stabilize the environnement. First we moved the zabbix server VM to a less busy physical server. Second for particular reasons we had to have the zabbix server answering on 2 differents TCP ports. The first TCP port was the regular 10051 which was handled directly by the zabbix_server process, and we also had the 10053 port handled by xinetd and which was forwarded to 10051 port. We worked at our setup to simplify things and managed to remove the tcp forwarding done by xinetd. So far the crash occurences seemed to disappear. We let 1.8.10 in place.
        Thanks

        Show
        Jerome Doucerain added a comment - No problem for the delay. We did 2 things to stabilize the environnement. First we moved the zabbix server VM to a less busy physical server. Second for particular reasons we had to have the zabbix server answering on 2 differents TCP ports. The first TCP port was the regular 10051 which was handled directly by the zabbix_server process, and we also had the 10053 port handled by xinetd and which was forwarded to 10051 port. We worked at our setup to simplify things and managed to remove the tcp forwarding done by xinetd. So far the crash occurences seemed to disappear. We let 1.8.10 in place. Thanks
        Hide
        Alexei Vladishev added a comment -

        Jerome, thanks for the follow up. I am closing it.

        Show
        Alexei Vladishev added a comment - Jerome, thanks for the follow up. I am closing it.

          People

          • Assignee:
            Unassigned
            Reporter:
            Jerome Doucerain
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: