Hello, Am Freitag, 4. November 2022, 01:12:24 CET schrieb Joe Salmeri:
Today I updated from TW 20220908 to 20221101 and SMB no longer works [...] I believe the problem is related to apparmour changes for samba but I am unsure how to resolve the issue.
Check your /var/log/audit/audit.log for lines containing DENIED. If AppArmor really denies something, you'll have such lines. If you don't find any DENIED lines, the issue is most likely not related to AppArmor. If it turns out to be a problem with AppArmor, you can switch the affected profiles to complain mode (allow everything, but log what would be denied): aa-complain /etc/apparmor.d/usr.sbin.smbd (same for nmbd and winbindd) Note: In complain mode, log lines will have ALLOWED instead of DENIED. If your issue is really related to AppArmor, please open a bugreport and attach your audit.log. Oh, and don't even try Seife's idea to zypper rm apparmor - I can guarantee you that this won't work (Seife, try yourself if you don't believe me ;-) BTW: Samba also logs to /var/log/samba/ - maybe you can find some hints there.
Here are the messages that are appearing for the smb service. [...] Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + silentexit 'smb.conf is older than the AppArmor profile sniplet' Nov 03 19:59:44 update-apparmor-samba-profile[9984]: + exit 0 [...] I suspect that the problem it is because it is complaining about smb.conf being different than what apparmour has but that config has not been changed since I originally set it up.
The messages you quoted just mean that the AppArmor profile sniplet is newer than your smb.conf, and that means there's no need to update it. Since the script is lazy, it just exits in this case. Regards, Christian Boltz -- A Perl program is correct if it gets the job done before your boss fires you. -- Larry Wall