Hi,
> I guess we’re facing a PostgreSQL grouping issue here. Does the host ubnt
> have 4 unhandled services?
I had the wrong number before.
ubnt (ubiquiti router (debian/vyatta)): 4 unhandled, 5 configured
tofu (tp-link managed switch): 11 unhandled, 3 configured
pogo (debian linux vm, icinga2 master): 1 unhandled, 12 configured
I don't recall what happened with pogo. I have a functional SNMP uptime check
for both ubnt and tofu. I tried adding eleven more SNMP OID checks (ram, swap,
load, disk) to see what works. Four of those failed for ubnt. All eleven failed
for tofu.
I disabled (commented out) the eleven checks for now, but the unhandled service
warnings remain after restart. If this is a possible bug, I'll gladly help
track it down. If it's something dumb I did, I can wipe the database.
Sample SNMP check:
apply Service "uptime" {
import "generic-service"
check_command = "snmp"
vars.snmp_oid = "1.3.6.1.2.1.1.3.0"
assign where host.vars.snmp_community != ""
}
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
