dai

Hi there, The bug has been fixed (see https://bugzilla.samba.org/show_bug.cgi?id=15210) and, fwiw, samba 4.17.5-1 fixes it on Archlinux. It's now up to Unraid to ship the update

Hello, I'm having the very same issue with a complete different setup: ArchLinux + smbd. My guess is that this issue has been introduced with the release of samba 4.17 (most probably .0 see changelog: https://www.samba.org/samba/history/samba-4.17.0.html) and should be treated upstream. Yet I can't see a bug report regarding it, so I fear we will have to wait a bit to see it fixed. There is now a bug report you can follow (or even upvote): https://bugzilla.samba.org/show_bug.cgi?id=15210 IMHO, turning `logging` to `0` masks the issue, it doesn't fix it. It's like taking a pain killer to cure a cancer.