Sometimes the database connection unexpectedly closes, and this causes the app to stop.
I am not sure that it is a timeout issue, because it happens only a couple of minutes after syncing the data.
Here is a snippet from log, the last time it happened.
May 11 10:18:22 dc-tools uv[741528]: ic| host: 'ohv-17.geog.ucsb.edu'
May 11 10:18:22 dc-tools uv[741528]: ic| filesystem.host.name: 'ohv-17.geog.ucsb.edu'
May 11 10:18:22 dc-tools uv[741528]: ic| filesystem.path: 'raid/r.r'
May 11 10:18:22 dc-tools uv[741528]: ic| '-----'
May 11 10:18:34 dc-tools uv[741528]: ic| 'update sync status'
May 11 10:20:27 dc-tools uv[741530]: ERROR:zabmap_api.api:Error fetching hosts: connection already closed
May 11 10:20:27 dc-tools uv[741532]: ERROR:zabmap_api.api:Error fetching hosts: connection already closed
If we can't find/fix the underlying problem, we should mitigate the results. A.T.M the server breaks when this happens.
Sometimes the database connection unexpectedly closes, and this causes the app to stop.
I am not sure that it is a timeout issue, because it happens only a couple of minutes after syncing the data.
Here is a snippet from log, the last time it happened.
If we can't find/fix the underlying problem, we should mitigate the results. A.T.M the server breaks when this happens.