Issue with device inventory after upgrade

We just upgraded our environment to 2024.2.1 to address some issue and have found since the upgrade, 2 of our 60+ devices have stopped successfully running inventory on the nightly inventory job. Instead in the logs I get "ERROR Start job timeout" and nothing further. Is there a way to enable more logging to find the issue? We are able to poll these devices without problem and I can MIB walk them quickly as well. Just would like some help pointing me in the right direction for some decent logging for this.

Find more posts tagged with

ncm troubleshooting

Logs

timeout

inventory

Accepted answers

All comments

mesverrum

havent seen that problem in particular, but you might try repairing/reinstalling the modules on the server. Most of the data in the inventory reports doesnt come from SNMP, so mib walk itsn't really relevant to the topic, but if you are able to the collect backups then that tells us the ssh creds are legit and it might come down to some quirk of the job scheduler and a reinstall might clean those up.

vinay.by

To get past this - create a new job and run it. Let me know if the new job works or do you see a new error.

__PRESENT__PRESENT__PRESENT

__PRESENT__PRESENT

mharvey

created a new job and added just one of the two devices, and still same issue. SNMP timeout.

vinay.by

I give up , not sure if its a generic issue or much bigger one, I had the same issue but that was in 2023.4.2 and post creation of new job i hit another error "violation primary key constraint SolarWinds" (there is a workaround for this issue) and i was told its permanently fixed on the latest version.

__PRESENT__PRESENT

mharvey

yeah we had that on that upgrade and creating a new job fixed it. This one though has me stumped. I just wish there was a better log or more logging to be able to look at.

PatrickRG

We're on 2024.4.1 now and have the same problem. It is only two nodes out of over four hundred for us but it is consistently the same two, consequently in the same location, that show "ERROR Start job timeout." I did recreate the job with the same results.