Ad Widget

Collapse

Исчезновение элементов данных с карты

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Dusty
    Member
    • Dec 2010
    • 70

    #1

    Исчезновение элементов данных с карты

    Столкнулся со странным (для меня) поведением заббикса:

    Нарисовал карту сети, где присутствуют данные как с хостов (железо HP, ОС Windows), так и с iLO4 этих хостов.

    При перезагрузке хоста iLO что-то такое отвечает заббиксу, что несколько элементов (items) переходят в состояние "not supported", через некоторое время в "became supported". Всё бы ничего, однако при переходе в "not supported" элемент с карты удаляется.

    На картинке таким образом пропали "Logical Drives" в левой части экрана.

    Как бороться, куда бежать - непонятно.

    Никто не сталкивался?
    Attached Files
  • Dusty
    Member
    • Dec 2010
    • 70

    #2
    Продолжаю

    Собственно бодался с ошибками в iLO4, соответственно его перезагружал. В логе увидел следующее:

    9668:20161227:140259.796 Zabbix agent item "perf_counter[\2\250]" on host "HOST" failed: first network error, wait for 15 seconds
    9670:20161227:140318.923 Zabbix agent item "system.cpu.load[percpu,avg15]" on host "HOST" failed: another network error, wait for 15 seconds
    9670:20161227:140337.927 Zabbix agent item "service.info[ddpvssvc,]" on host "HOST" failed: another network error, wait for 15 seconds
    9670:20161227:140356.932 temporarily disabling Zabbix agent checks on host "HOST": host unavailable
    9691:20161227:140718.539 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.0]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.539 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.1]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.539 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.2]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.539 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.3]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.4]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.5]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvReadsSec[0.6]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.0]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.1]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.2]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.3]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.4]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.5]" became not supported: No Such Instance currently exists at this OID
    9691:20161227:140718.540 item "iLO-HOST:cpqDaPhyDrvWritesSec[0.6]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaCntlrBoardCondition[0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaCntlrCondition[0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaAccelBattery[0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaAccelCondition[0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaAccelStatus[0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.1]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.2]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.3]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.4]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.948 item "iLO-HOST:cpqDaPhyDrvCondition[0.5]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvCondition[0.6]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.1]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.2]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.3]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.4]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.5]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvReads[0.6]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.0]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.1]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.2]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.3]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.4]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.5]" became not supported: No Such Instance currently exists at this OID
    9690:20161227:141117.949 item "iLO-HOST:cpqDaPhyDrvWrites[0.6]" became not supported: No Such Instance currently exists at this OID
    После перезагрузки:

    9670:20161227:141736.202 enabling Zabbix agent checks on host "HOST": host became available
    9688:20161227:142118.063 item "iLO-HOST:cpqDaCntlrBoardCondition[0]" became supported
    9688:20161227:142118.063 item "iLO-HOST:cpqDaCntlrCondition[0]" became supported
    9688:20161227:142118.063 item "iLO-HOST:cpqDaAccelBattery[0]" became supported
    9688:20161227:142118.063 item "iLO-HOST:cpqDaAccelCondition[0]" became supported
    9688:20161227:142118.063 item "iLO-HOST:cpqDaAccelStatus[0]" became supported
    Ну и те айтемы, которые перезагрузки стали "became supported" остались. Остальные удалились.

    Как бороться?

    Comment

    • Kos
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Aug 2015
      • 3404

      #3
      Удалились, случайно, не те ли, которые обнаруживаются через low-level discovering?

      Comment

      • Dusty
        Member
        • Dec 2010
        • 70

        #4
        Originally posted by kos
        Удалились, случайно, не те ли, которые обнаруживаются через low-level discovering?
        Именно те ли. Да. А в эту сторону я не думал. Их закреплять как-то надо? Или клонировать видимо, а дискаверинг отключать?

        Comment

        • Kos
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Aug 2015
          • 3404

          #5
          Думаю, достаточно в правилах дискаверинга выставить ненулевое время жизни. Т.е. убирать необнаруживаемые объекты не сразу, а хотя бы на следующий день (а за это время, если это был случайный сбой, они обнаружатся снова).

          Comment

          • Dusty
            Member
            • Dec 2010
            • 70

            #6
            Originally posted by kos
            Думаю, достаточно в правилах дискаверинга выставить ненулевое время жизни. Т.е. убирать необнаруживаемые объекты не сразу, а хотя бы на следующий день (а за это время, если это был случайный сбой, они обнаружатся снова).
            Большое спасибо за совет, сейчас попробую применить.

            Comment

            Working...