Duplicacy on Linux creates a large number of DBus processes

Support
#1

Hello,

We are running Duplicacy Web Edition as a systemd service on a RHEL 8 server.

We have a number of jobs that back up data on the machine to external S3-compatible storage. These jobs run hourly.

Over time the number of DBus processes under /system.slice/duplicacy.service grows very large, which consumes a large amount of memory and has some other nasty side-effects.

● duplicacy.service - Duplicacy backup
   Loaded: loaded (/etc/systemd/system/duplicacy.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2024-10-25 11:17:42 BST; 2s ago
 Main PID: 508725 (dwe_main)
    Tasks: 21621 (limit: 202731)
   Memory: 3.4G
   CGroup: /system.slice/duplicacy.service
           ├─  90543 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ├─ 150977 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ├─ 326124 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ├─ 452203 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ├─ 508725 /usr/local/sbin/dwe_main
           ├─ 564205 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ├─ 751337 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session

...
# systemctl status duplicacy.service | grep -c dbus
3758

We can recover the memory by killing and restarting the Duplicacy service (as mentioned in this post Linux: autostart - #2 by vegivamp) but that is not ideal.

What causes this and is there something we can do to prevent it happening?

Thanks,
John

#2

I’m not sure why there were so many dbus daemons. The only place where the web GUI opens a dbus session is to read the master password from the keyring at startup, and after that it should not deal with dbus at all.

You can run dbus-monitor interface=org.freedesktop.Secret.Service to watch for new dbus sessions. In my test only one session was opened at the beginning.

#3

We’ve upgraded to Duplicacy web edition 1.8.0 and so far we haven’t seen a proliferation of dbus procesess

$ systemctl status duplicacy.service 
?? duplicacy.service - Duplicacy backup
   Loaded: loaded (/etc/systemd/system/duplicacy.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2024-10-25 13:35:35 BST; 3 days ago
 Main PID: 517546 (dwe_main)
    Tasks: 24 (limit: 202731)
   Memory: 9.2G
   CGroup: /system.slice/duplicacy.service
           ????517546 /usr/local/sbin/dwe_main
           ????517555 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
           ????517559 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets

Oct 25 13:35:35 pbcl-svr7.pebblebay.com systemd[1]: Started Duplicacy backup.
Oct 25 13:35:35 pbcl-svr7.pebblebay.com dbus-daemon[517555]: [session uid=0 pid=517553] Activating service name='org.freedesktop.secre>
Oct 25 13:35:35 pbcl-svr7.pebblebay.com org.freedesktop.secrets[517555]: GNOME_KEYRING_CONTROL=/root/.cache/keyring-F3RTV2
Oct 25 13:35:35 pbcl-svr7.pebblebay.com dbus-daemon[517555]: [session uid=0 pid=517553] Successfully activated service 'org.freedeskto>
Oct 25 13:35:35 pbcl-svr7.pebblebay.com dwe_main[517546]: Log directory set to /var/run/duplicacy/logs
Oct 25 13:35:35 pbcl-svr7.pebblebay.com dwe_main[517546]: Duplicacy Web Edition 1.8.0 (B47138)
Oct 25 13:35:35 pbcl-svr7.pebblebay.com dwe_main[517546]: Starting the web server at http://127.0.0.1:3875

I’ve start the dbus-monitor as suggested but I haven’t seen any new instances.
I’ll keep an eye on it though.