Replies: 5 comments 3 replies
-
Uh, I'm probably running into the same or similar issue as this: |
Beta Was this translation helpful? Give feedback.
-
OK, so I can run it by restricting Gunicorn workers and background workers both to 1 (now on version 0.9.1, will try going back up to 0.9.2). Then it finally manages to start up and Inventree is usable again. Could it be that the reason why I cannot start Inventree with more workers is that it is trying to make backup during startup of the server, preventing proper startup, running out of time and then it all runs in a circle? Now that it started up, it generated backup 3 times in a row until it finally decided it has enough backups... |
Beta Was this translation helpful? Give feedback.
-
OK, so after shutdown, going up to 0.9.2 and new startup, it's not doing the backups again this time. An idea that comes to mind: The backup task should be postponed until some uptime of Inventree server is reached so as not to block proper startup of the server by the backup. For anyone else running into this issue on slow processors like the Atom N2800:
Not sure what the timeout means since workers still seem to get killed after 30 seconds according to log. |
Beta Was this translation helpful? Give feedback.
-
Also one problem from older versions happened to me again - the left navigation bar in Part view went missing and System Information was unavailable until I logged out, cleared cookies and site data and logged in again. |
Beta Was this translation helpful? Give feedback.
-
Please file problems as bugs - discussions are very hard to follow with several responses. |
Beta Was this translation helpful? Give feedback.
-
Hi, I have been using Inventree for quite a while in a docker-compose configuration.
Now, I have upgraded from 0.8.3 to 0.9.2. However, I cannot start the server at all. It keeps on spawning workers and killing them and creating SQL backups every 2 minutes (exactly, so probably not a coincidence). The SQL backup keeps all my 4 cores on a server loaded to 100% and it's not able to do anything else. Is this expected behaviour of the new backup system or did I do anything wrong?

Beta Was this translation helpful? Give feedback.
All reactions