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
On slower machines, Netbox startup time can be long e.g. 10 minutes in my experience. This causes the compose to end early, saying Netbox failed to start. It failed within the given health window, but starts eventually.
The problem from this is that worker and housekeeping isn't started because compose terminates before netbox became healthy (requirement for housekeeping and worker to start). This causes some issues e.g. doesnt allow to run Netbox jobs.
I propose to add some wiki info to remove health check from compose, and instead add restart: always for housekeeping and worker, rather than depends on: netbox: condition: service_healthy if running on a slow machine. Or to manually start worker and housekeeping, although the first idea may be better as it requires less user interaction.
Edit: Even on a higher-end CPU on docker desktop, the migrations didnt make it in the specified waiting time
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
On slower machines, Netbox startup time can be long e.g. 10 minutes in my experience. This causes the compose to end early, saying Netbox failed to start. It failed within the given health window, but starts eventually.
The problem from this is that worker and housekeeping isn't started because compose terminates before netbox became healthy (requirement for housekeeping and worker to start). This causes some issues e.g. doesnt allow to run Netbox jobs.
I propose to add some wiki info to remove health check from compose, and instead add
restart: always
for housekeeping and worker, rather thandepends on: netbox: condition: service_healthy
if running on a slow machine. Or to manually start worker and housekeeping, although the first idea may be better as it requires less user interaction.Edit: Even on a higher-end CPU on docker desktop, the migrations didnt make it in the specified waiting time
Beta Was this translation helpful? Give feedback.
All reactions