provide more detail on failure during extraction

systemd / casync

Content-Addressable Data Synchronization Tool

1.51k stars 117 forks source link

provide more detail on failure during extraction #44

Open chergert opened 7 years ago

chergert commented 7 years ago

I get this when trying to run an extract of a rather large set of ISOs (some 30gb).

Failed to run synchronizer: Operation not permitted

Given the number of syscalls, I'd rather not trouble shoot with strace :)

Additionally, it might be nice if it could continue trying to extract further files (which might succeed) even though this one particular file failed.

fsateler commented 7 years ago

This problem is not specific to extraction. I tried to create an OS tree archive as normal user and it failed with the same error message. Finding why did this fail took a while (because some files in /etc are not world readable), but casync should definitely print who caused the failure.

jakicoll commented 10 months ago

I stumpled upon this today, also getting

Failed to run synchronizer: No such process

As already said, the output of strace is quite overwhelming and some more context would make error message really helpful.

What I did figure out: It happens when a file you extract is owned by some user not existing on the system you are extracting on. At least either running casync --without=user-names or creating that user both fixed it for me.