nick n.

Results 215 comments of nick n.

lets see, running 2.085001 atm and have this on the inventory page. ![Image](https://github.com/user-attachments/assets/159553da-2481-460e-840c-a6bed75ffcad) ![Image](https://github.com/user-attachments/assets/0ce7c871-edca-4a5d-9551-a3a77b6fadc1) running a query on the device table for class "snmp::info" gives these: ip | creation |...

hm; for some reason my expire job is no longer running via the scheduler, which alrdy explains a bit of why those devices didn't go away by themselves. ``` 41778374...

> We have the same issue. Haven't found the source yet. Occasionally I delete the incorrect devices from the database with the SQL `delete from device where model = ''...

> hm; for some reason my expire job is no longer running via the scheduler, which alrdy explains a bit of why those devices didn't go away by themselves. >...

> That's a fair hunch, [@inphobia](https://github.com/inphobia) ! > > (assuming we can't just slow down net-snmp with longer timeouts...) Would it help to have some setting in Netdisco that aborts...