Rmt mirroring doesn't work from rmt-server-mirror.timer

Dear forum members,

When entering

rmt-cli mirror

from the commandline, our rmt server (called ‘rmt-ng’, on sles15sp6) mirrors all our repos without complaint. But it fails to run from the timer service, and I get errors like this in the systemlog:

2025-03-10T14:55:14.810769+01:00 rmt-ng rmt-cli[23427]: WARN: Repository ‘SLE-Module-Python3-15-SP6-Updates’ (6663): Error while mirroring repository: Could not create local directory /usr/share/rmt/public/repo/SUSE/Updates/SLE-Module-Python3/15-SP6/x86_64/update/ with error: File exists @ dir_s_mkdir - /usr/share/rmt/public/repo.

and later:

2025-03-10T14:55:14.810843+01:00 rmt-ng rmt-cli[23427]: WARN: Mirroring completed with errors.
2025-03-10T14:55:14.818757+01:00 rmt-ng systemd[1]: rmt-server-mirror.service: Main process exited, code=exited, status=1/FAILURE
2025-03-10T14:55:14.818814+01:00 rmt-ng systemd[1]: rmt-server-mirror.service: Failed with result ‘exit-code’.

Unsurprisingly, that directory does indeed exist. But why would that be an error? It was put there by the manual mirror action… For now, I just do the mirroring by hand every now and then, but it sure would be nice to get this automated. So any help is greatly appreciated!

gerard

Note those are warnings not errors - does the timer service mirror other packages without errors?

If you’re mirroring by hand do the permissions match those of the auto-mirrored files/directories?

Warnings indeed, but those were the only errors I could find. The warnings come for every mirrored product. When done by hand the permissions are 644 for the rpm files. I believe that is the same as when run from the timer service, but I’m not totally sure, since last week I changed them to 660 to see if that would make a difference (It didn’t.)
Thanks for your answer!