I see the following error when issuing a backup job:
2019-06-30 15:13:02 GMT [ERR] [ 9129] Stuck thread detected 2019-06-30 15:13:02 GMT [ERR] [ 9129] Error while joining backup thread (error 110: Connection timed out)
A backup is in fact a scan job. To understand the functionality of scans in general, refer to the FAQ on Scans article.
The error is expected to be seen in 2 situations:
- The executed backup job was exited manually (ctrl+c) which would result in timing out of the connection. The active scan job on the node(s) would eventually time out. If necessary, an explicit
killof the job might be needed.
- If the error is seen on fresh execution of asbackup, it could mean that all the current scan-threads are busy processing ongoing and/or higher priority scan jobs. In this situation, a potential workaround would be to issue the asbackup at a higher priority (using ‘-f’ or ‘–priority’ option in asbackup) or to increase the number of scan-threads. Refer to Manage Scans page to understand scan priority.
asbackup stuck thread