Logging msyncd requires privileged access

[direc85]

I'm currently debugging making a backup of my device to my Nextcloud server, and I tried to enable msyncd logging:

systemctl --user stop msyncd
killall msyncd
devel-su
MSYNCD_LOGGING_LEVEL=8 msyncd 2>&1 | tee -a msyncd.log

I got these results:

** (process:11987): WARNING **: 14:09:49.650: Could not stat accounts privilege directory
[W] unknown:0 - Manager could not be created. DB is locked

** (process:11987): CRITICAL **: 14:09:49.698: ag_manager_list: assertion 'AG_IS_MANAGER (manager)' failed
[W] unknown:0 - Profile not found

When I tried to make a backup, creating the backup failed immediately. I then tried running it as defaultuser:privileged like this:

sudo -E -g privileged MSYNCD_LOGGING_LEVEL=8 msyncd 2>&1 | tee -a msyncd.log

This resulted in no rows being printed - a good sign. I then tried to create a backup, which started, and eventually failed with a bunch of debug output (and hopefully something to help with my issue).

I'm not sure if using sudo is the preferred tool to use for this, but it let msync start as correct user and group, which seems to be required for this guide to work.

[CLAassistant]

All committers have signed the CLA.

[Thaodan]

Use devel-su -p to get a privileged shell, you don't need sudo.
Besides you can systemctl --user edit <service> to amend this into the service:

[Service]
Environment=MSYNCD_LOGGING_LEVEL=8

Then close the editor and restart the service.
Using the latter approach the testing is more reliable and close to the real environment.

devel-su -p was mentioned but not explained previously I see. systemctl edit was neither. I think
for the latter we should mention it under tips and tricks butter refer to the manpages for further explanation.

[rainemak]

Yeap, "devel-su -p" it should be.