OperationalError encountered twice. Never seen before on my setup- what's going on? #5021
Replies: 2 comments 4 replies
-
In both cases the database connection is failing due to a timeout error. Maybe the server is resource constrained? Or, there are not enough worker connections available and the database is temporarily overloaded? The URL in your second example looks strange - is that an "expected" URL in your setup? |
Beta Was this translation helpful? Give feedback.
-
Thank you for the explanations. @SchrodingersGat @matmair. I've taken both of those extra steps to beef up my account security. Can these errors interfere with the functionality of my InvenTree database in any way, or is it just one of those inescapable security risks that I just need to deal with? |
Beta Was this translation helpful? Give feedback.
-
Hi everyone-
I'm currently running InvenTree 0.11.0. Full copy/pasted details:
Version Information:
InvenTree-Version: 0.11.0
Django Version: 3.2.18
Database: postgresql
Debug-Mode: False
Deployed using Docker: False
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]
I have it running on a DigitalOcean Droplet. I've encountered an error that I've never seen before:
Error 1 details
Error 2 details
Both errors occurred when my InvenTree system was NOT in use, which makes it all the more unusual. Once on June 7th, and another time on June 11th. As of now my InvenTree system is working without issue but since this is a live system running for a business I would like to figure out what is causing these OperationalErrors.
Any guesses as to what could be happening and what I can do to fix/prevent it from re-occurring?
Beta Was this translation helpful? Give feedback.
All reactions