Error: cannot rollback - no transaction is active

1

Using Insync package 1.3.3.36056-wheezy on Debian SID, I get the error:

Error: cannot rollback - no transaction is active

I tried using auditd for the library.zip and executables insync and insync-headless in /usr/bin but the command ausearch returns nothing:

-> % sudo ausearch -f /usr/bin/insync-headless -k insync-headless > insync-headless.zip.audit

-> % sudo ausearch -f /usr/bin/insync -k insync > insync.zip.audit

-> % sudo ausearch -f /usr/lib/insync/library.zip -k insync-lib > insync-library.zip.audit

And this is my /etc/audit/audit.rules

# This file contains the auditctl rules that are loaded
# whenever the audit daemon is started via the initscripts.
# The rules are simply the parameters that would be passed
# to auditctl.

# First rule - delete all
-D

# Increase the buffers to survive stress events.
# Make this bigger for busy systems
-b 320

# Feel free to add below this line. See auditctl man page
-w /usr/lib/insync/library.zip -p warx -k insync-lib
-w /usr/bin/insync -p warx -k insync-bin
-w /usr/bin/insync-headless -p warx -k insync-headless

You can download all the logs and my full Database from /home here:

[link removed]

I already purge twice insync from my system and each time I removed manually every single file found that could exists after the purge in / that contains anything with insync after every purge, so I do not think that the problem is on my side

This is the million times that insync fails for something, so what the fuck is the problem now?

2

Tagging @lpugoy our engineer. He’ll get back to you soon.

Thank you.

3

and now my question is… How soon is soon?

4

@flipefr: Apologies for not replying sooner. I have removed the link you posted because it’s publicly accessible. This link gives information on how you can share files in Google Drive with specific people: https://support.google.com/drive/answer/2494886?hl=en.

Unfortunately the client db for flipefr@gmail.com was corrupted and can’t be recovered, so you would need to re-add it. To lessen the chances of this happening in the future, you could try passing the --synchronous-full flag when running Insync (insync start --synchronous-full). Please see ‘insync start -h’ for details.

To remove the account please delete the file ~/.config/Insync/dbs/gd2-117469396628075914794.db. After restarting Insync you can re-add it by clicking on the tray icon -> Add a Google account.

When re-adding your account you should be able to reuse your old Insync folder. If you encounter any issues please let us know.

5

Working again and starting from the scratch, lets see how it goes