Rclone seems to keep running after backup ends

[19wolf]

I've noticed since I started using Rustic, I have a lot of leftover rcloneorig processes. It seems like every time a backup runs, the rclone process doesn't get closed afterwards.

19wolf      5733  3.5  0.1 1284416 49796 ?       Sl   20:22   0:00 rcloneorig --config ~/.rclone.conf serve restic --stdio --b2-hard-delete GoogleDrive:restic
19wolf      8356  0.0  0.1 1286080 61220 ?       Sl   Sep13   0:11 rcloneorig --config ~/.rclone.conf serve restic GoogleDrive:restic --addr localhost:0
19wolf      9513  0.0  0.2 1353844 100768 ?      Sl   02:18   1:02 rcloneorig --config ~/.rclone.conf serve restic GoogleDrive:restic --addr localhost:0
19wolf     16279  0.0  0.1 1285184 52564 ?       Sl   Sep13   0:07 rcloneorig --config ~/.rclone.conf serve restic GoogleDrive:restic --addr localhost:0
19wolf     20556  0.0  0.1 1284928 54792 ?       Sl   Sep13   0:07 rcloneorig --config ~/.rclone.conf serve restic GoogleDrive:restic --addr localhost:0
19wolf     22057  0.0  0.1 1285440 57584 ?       Sl   Sep13   0:12 rcloneorig --config ~/.rclone.conf serve restic GoogleDrive:restic --addr localhost:0

[simonsan]

We are in the middle of preparing a new release for rustic, we will get back when we have finished that. In the meantime, can you please give a bit more information, e.g. uname -a output, rustic --version output and other helpful information?

Thank you!

[19wolf]

Linux NepheleTower 6.1.49-Unraid #1 SMP PREEMPT_DYNAMIC Wed Aug 30 09:42:35 PDT 2023 x86_64 AMD Ryzen 5 2600 Six-Core Processor AuthenticAMD GNU/Linux
rustic v0.5.4

[aawsome]

The spawned thread which just catches rclone stderr output and prints it as a INFO log could be the problem.. I'll test if we can change something there..

[aawsome]

I think this was it. Fix is already on the way!