João Soares

This would be a great feature to have, a min/max VLAN ID, so we can programmatically get the next available VLAN ID

Hi @bryanculver, thanks for the fast reply. I haven't tried it since I was not 100% sure of the possible impact of this change. I'm still not, but I'll try...

@bryanculver, it still failed but the output has changed With CONN_MAX_AGE at 0, will Nautobot/Django reuse the same DB connection during the same job execution? Or will it create a...

Hi, I have 'bypassed' this issue by updating JobResult every 30 minutes, but since you have tagged this issue with a bug, I'm happy to help if I can :)

@jathanism I haven't configured SSL on the database connectivity. I have a simple Postgres database with the most basic/default configs. Unless there is a default I'm not aware of, but...

I'm running RHEL 7 (with RedHat's software collections). Postgres 13.7 Doesn't look like I'm running SSL from this output: ``` psql --username nautobot --password --host nautobot-db-01 nautobot Password: psql (13.7)...

Update: I am still running version 1.4.2. Is the fix available in a later version already? I just had this happen on a scheduled job. As soon as the scheduled...

Unfortunately it still happened on v1.4.5 I had 3 scheduled jobs. One at 20:00, one at 21:00 and one at 23:00. The first 2 ran without issues and I got...

@bryanculver I did restart all workers + scheduler after upgrading to 1.4.5, so I hope that did the trick. If I remove `CONN_MAX_AGE` entirely, won't it behave the same since...

Unfortunately I'm getting the same problem even with `CONN_MAX_AGE` back to 300 (and after restarting `nautobot`, `nautobot-worker` and `nautobot-scheduler`). My scheduled jobs are not even running anymore. Every time my...