Hello Lucas, thank you for the detailed description - it did work now.
Result: In 2:4.7.6+dfsg~ubuntu-0ubuntu2.23test~ppa1 the error is not present or at least currently not triggerable. I think it is not present, because it began with the later versions. So I upgraded again back to 2:4.7.6+dfsg~ubuntu-0ubuntu2.28. Now it becomes strange: Currently (2.28) the error ist not triggerable too. Before the down- and upgrade it war triggerable with every /usr/bin/smbcontrol winbindd reload-config. But: In the past the error didn't happen on every logrotate calling /usr/bin/smbcontrol winbindd reload-config too, but on some. So I can only wait if or when it happens again in 2.28. Logrotate runs on each Sunday. Between 2.23 and 2.28 there was the big security fix CVE-2020-25717. Can there be a reason for this behaviour? I'm sorry, that I can't give you an expicit result. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25717 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960821 Title: Winbind can no more connect to Windows domain after reload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1960821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
