Nagios Support Forum

Also it seems the match type of numeric is not appropriate for an operating state value such as running(2). Can't set a threshold for that. But if I try changing match value to string it doesn't change the thresholds field format. Seems like I would need a match type that listed good, warning, criti...

So following this fix I ran the same job and it does show a selection table of 261 OIDs but it gives this boatload of errors first: warning Invalid warning numeric range for OID (jnxOperatingContentsIndex.1.1.0.0) warning Invalid critical numeric range for OID (jnxOperatingContentsIndex.1.1.0.0) war...

The log file looks pretty straightforward. attached No OIDs show up in the selection tables.

Dave

Where are the walk jobs actually retained, or would a cut/paste of what shows in the job view suffice ... redacting the creds?

Thanks,

Dave

Some more information.... I noticed if I click the re-run job control under SNMP Walk Jobs for that job the submit form is corrupted. The device address field has my filter OID instead of the device address, and the filter OID field is empty. Can't just click submit to rerun the job because the auth...

Can there be a link on the controls for SNMP Walk Jobs list to start the SNMP Walk Wizard OID selection? ie rather than have to go back to find the SNMP Walk wizard and select the SNMP Walk job from the pulldown simply start the OID selection with the controls on the listed job.

I've loaded the MIBs and resolved MIB errors in the file viewer and it looks like they're translating.
...but no rows in the select table
Dave

I'm running the latest available I believe. 2026R1.2.

Thanks,

Dave

I'm trying to use SNMP walk wizard to monitor components such as fans and power supplies. I limited the OIDs with a filter and the job seems to have 261 OIDs found. Screenshot 2026-03-23 111623.png But when I click next button no OIDs show up in the tables to select. Does the wizard only handle cert...

Awesome! That seems to have corrected the issue. Got another likely DB related issue. Although the DB repair came back with no hard errors, when I look at service status in the GUI I have somehow managed to get this one entry at the top of the list that has a blank hostname and service name of '0'. ...