Using insync-headless you have a couple of actions like get_actions_required, get_errors, get_sync_progress and get_status that enables you to check what is going on with Insync at a high level. I use these commands regularly when working with Insync on a headless box.
I would however like to know how to check what is happening with Insync at a lower level as well, when none of the above commands are able to resolve why Insync is seemingly just hanging in a paused state for days and not doing anything else?
I have copies of the various .db files from the faulty server, amongst others the logs.db file as well. Is this the correct place to check what is happening with Insync at this very moment? As Insync does not add any log entries to native Linux logging journals it is assumed that this is the only place one can look for its up-to-the-second state information?
As these are DB tables, I am also assuming that the latest log entries will appear in the last rows of the events_log table? Your time stamps that you are using are gibberish so its difficult to find the correct time entry by looking at those Is there a way to decode these to confirm time entries?
The last row is showing client_run as the thread name, yet when get_status is queried is shows as paused?