New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Internal Server Error" - When attempting to access 'Sensors' page. #236
Comments
A database lock error occurs when a process is writing to the SQL database file and requires exclusive access to it. This normally takes a fraction of a second and the database is then able to be opened by other processes. |
Your daemon log indicates this error happened once. The next daemon restart it did not happen (i.e. the issue was not present). Are you saying you can only not access the Sensor page? |
Looking at your HTTP log, the issue appears to be the code not recognizing any DS18B20 sensor(s) you previously added. Looking into the offending code and working on a fix. |
I just committed a fix for this issue and released v5.0.22. Update and let me know if the issue persists. Thanks for the bug report. |
Hi Kyle, That's correct; Only the sensor page is affected. It seems I missed a chunk of my Daemon log when pasting it into the txt file. I can confirm it was occurring more than once. Thanks for the fix, I'll update when I get home and let you know how it goes. |
Issue resolved! |
Mycodo Issue Report:
Problem Description
Please list:
"Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application."
Errors
"ERROR - Error raised in session_scope. Session will be rolled back: db_uri='sqlite:////home/pi/Mycodo/mycodo/../databases/mycodo.db', error='(sqlite3.OperationalError) database is locked [SQL: u'SELECT alembic_version.version_num AS alembic_version_version_num \nFROM alembic_version\n LIMIT ? OFFSET ?'] [parameters: (1, 0)]'"
LOG_Http.txt
LOG_Daemon.txt
Rebooting does not resolve.
This is a recent fresh install (2-3 days old)
The text was updated successfully, but these errors were encountered: