Opsview odw not updating

Most often it is due to a connection issue to the backend historical database, crashed database tables, core scheduling/check execution issues, or lack of resources (causing orphaned checks).The typical workflow can be explained as follows: Nagios core schedules a check, and once the check is run the output is returned and the ndomod NEB module pushes the check result to the ndo2db daemon by placing it in the kernel message queue. 위에서 제가 말씀드린 prefork 설정에 문제가 좀 있네요 를 참고하셔서 좀 수정을 하셔야 제대로 동작합니다.Cleanup via daily housekeeping Added multiline plugin output to notification emails Link between object in status pages to events view and notifications view Added acknowledgement for single host or service check_snmp_sysinfo returns CRITICAL if agent does not respond (was returning WARNING) Added new application monitors for Alfresco, JBoss, Atlassian, Puppet, VMWare ESX, Foundry, Wordpress and Jasper Reports Updated initial database configuration to have two keywords: opsview and opsview-components Enable SNMPv3 support in MRTG - must have at least MRTG version 2.15.0 Added flap detection checkbox to host edit configuration page Added /rrdfetch?Thus, there are a number of things that can interfere with updating the "Last Check" time on the XI UI.The troubleshooting step is to verify if the checks are actually getting scheduled and executed.

opsview odw not updating-26opsview odw not updating-46opsview odw not updating-85

For example, tag the new Windows Server 2008 Hosts with #windowsservers, which will allow Windows Administrators to view them within Opsview Monitor.

If the Core interface displays accurate "Last Check" times, proceed to Step 2 below.

If the Core interface is experiencing the same issues as the XI interface, follow Step 1 below.

If you believe this is an error, check the HTTP server authentication requirements for accessing this CGI and check the authorization options in your CGI configuration file. nagios agent의 장점은 snmp로는 커버하기 힘든 어떤 값이든 커스트마이징해서 모니터링 할 수 있다는 것이죠. 단 그 기본 구조를 잡는데 좀 시간이 걸리고 노력이 필요하지만 그건 충분히 감수할 만하다고 봅니다. This documents the major changes between releases 3.7.0 29th April 2010 FEATURE: Notification profiles - a contact can have multiple profiles to fine tune your notification requirements Extended notification methods - can now create your own notification methods, with per contact variables New plugin, check_opsview_keyword, to show summarised state of keywords New Alert Every Failure option, which respects the re-notification interval.

해결책 : 아직 알수 없음, 깔끔한 상태에서 opsview를 재설치해볼것 에러 : Connection refused or timed out 해결책 : 방화벽(iptables, tcp wrapper) 정책에 차단되고 있지 않는지 확인한다. Linux의 경우 opsview에서 제공하는 opsview-agent 패키지를 사용해도 되고 아니면 각 리눅스 배포본에서 제공하는 nagios agent 패키지를 깔아 써도 됩니다. Useful for passive alerts New execution dependency, so checks are not run if the dependency has failed.