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
{{ message }}
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.
d.get_server_list()
DB_SQLError: Failed to query TANGO database (error=Lost connection to MySQL server during query)
The query was: SELECT DISTINCT server FROM device WHERE server LIKE "%" ORDER BY server
(For more detailed information type: tango_error)
If i'm right in assuming that d is a instance of the class tango.Database, this is because the mysql service container as become unavailable (at least temporarily).
I'm able to reproduce the error by removing the mysql service or killing the mysql service container (with docker kill on the container).
If using the SIP demo docker compose stack, removing the service can be done with:
does not seem to reproduce the issue, so this does not look like mysql timeout error (unless there is an additional timeout setting i'm missing). Note the the default for both of these settings is 28800s == 8h
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Using the itango3 client
d.get_server_list()
DB_SQLError: Failed to query TANGO database (error=Lost connection to MySQL server during query)
The query was: SELECT DISTINCT server FROM device WHERE server LIKE "%" ORDER BY server
(For more detailed information type: tango_error)
In [9]: d.get_server_list()
Out[9]: DbDatum(name = 'server', value_string = ['DataBaseds/2', 'processing_block_ds/1', 'sdp_master_ds/1', 'subarray_ds/1', 'TangoAccessControl/1', 'TangoTest/test'])
To Reproduce
Leave the tango-db service idle for some ill-defined time!
Expected behavior
No error
Screenshots &/or terminal output
If applicable, add screenshots or terminal output to help explain the problem.
Context
Please add as much context as possible to help narrow down the problem.
The text was updated successfully, but these errors were encountered: