You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deleting a netbox the table ipdevpoll_job_log seems to be locked for updates. As every ipdevpoll job wants to update this table they all is kept waiting when the delete takes a long time.
Observing this again now. It seems that what may actually be happening here is that while PostgreSQL is running cascading deletes, ipdevpoll still doesn't know that the netbox in question is being deleted, so the jobs related to this device are still running. Any attempt to insert an ipdevpoll_job_log entry related to this netbox will be blocked by PostgreSQL, eventually causing all available database connections in an ipdevpoll process to be blocked.
One suggested solution would be to introduce a deletion flag on netbox, which would cause ipdevpoll to stop working on it. This overlaps with one of the discussed solutions for #1313.
When deleting a netbox the table
ipdevpoll_job_log
seems to be locked for updates. As every ipdevpoll job wants to update this table they all is kept waiting when the delete takes a long time.Related reference in local ticket system:
https://rt.uninett.no/Ticket/Display.html?id=115204
Imported from Launchpad using lp2gh.
The text was updated successfully, but these errors were encountered: