Backend manager queue runner did not stop

Support
1

“Backend manager queue runner did not stop”

I recently updated the Duplicati version in one of our servers from 2.1.0.5_stable_2025-03-04 to 2.1.2.0_beta_2025-08-20. I was hoping that this new build solved another problem I was having (where the tool seemed to crash somehow, and the tray icon would disappear when hovering).

However, this new build seem to introduce a Warning, which says “Backup manager queue runner did not stop”. I was able to reproduce this, here’s more information about the setup:

  • Job runs on a Windows Server 2019 machine;
  • Destination backend is an FTP server;
  • Source files are ~200-500MB only
  • No warnings when:
    a. There are no changes to source files
    b. Changes are small (tested with a ~3KB file)
    c. Backend is a different SFTP server (instead of the regular FTP one)

I believe it’s likely this is not an issue, but I would prefer not to have this Warning, as it generates some commotion when some people look at the resulting DupReport e-mail…

So, is it an issue? Is it possible to fix it through some kind of configuration?

Thanks in advance!

P.S.: And thanks for the great tool (this is my first time posting here)!

2

Update: I have noticed that the Warning is not showing up on Saturdays for the past 30 days, but it does on the other days of the week since I installed it. It looks a lot to be related to some kind of congestion on the path up to the destination FTP machine, but I’ll have to keep looking as I can’t find any clues.

So does anyone have an idea on how to avoid this warning without changing the code? I think that’s probably just some timer that has to be tweaked. I’ll also keep looking at things like the FTP server config and pending sessions, for example.

3

Welcome to the forum @RodT

  --suppress-warnings (String): Suppress specific warnings
    Suppress warnings and log them as information instead. Use this if you
    need to silence specific warnings. This option accepts a comma separated
    list of warning IDs.

Maybe this one second timer, but this could use some dev help:

1 Like
4

Thanks, this solved it for me. The exact string I used was --suppress-warnings=BackendManagerShutdown. Not sure if there’s a list of the warnings we can suppress somewhere, just took this from the code you also quoted in your reply.

I am curious about the 1 second delay limit, is there a reasoning behind this value? Maybe one of the devs can shed some light on this.