[opensuse-factory] samba smb error after 12.3 to 13.1 upgrade
Hi After a distro upgrade 12.3 to 13.1 samba file server we have these errors: No builtin backend found, trying to load plugin No builtin nor plugin backend for tdbsam found I've tried deleting the tdb's and rejoining the domain but nothing. Any ideas anyone? Thanks, Lynn [global] workgroup = HH3 realm = HH3.SITE security = ADS kerberos method = system keytab username map = /home/lynn/smbmap log level = 3 [users] path = /home/users read only = No [profiles] path = /home/profiles read only = No store dos attributes = Yes create mask = 0600 directory mask = 0700 browseable = No guest ok = No printable = No profile acls = Yes csc policy = disable -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Donnerstag, 17. Oktober 2013 schrieb lynn:
After a distro upgrade 12.3 to 13.1 samba file server we have these errors: No builtin backend found, trying to load plugin No builtin nor plugin backend for tdbsam found
It could be caused by the AppArmor profile, see https://bugzilla.novell.com/show_bug.cgi?id=846054 and https://bugzilla.novell.com/show_bug.cgi?id=845867 Packages with an updated profile were accepted today for 13.1 and Factory - updating to the latest apparmor-profiles package (which mentions the above bugs in the changelog) and running "rcapparmor reload" afterwards[1] should help ;-) If the updated package was not published yet, you can use the apparmor- profiles package from security:apparmor. Regards, Christian Boltz [1] reloading the profiles in %post is on my TODO list ;-) -- I live in Canada with plenty of experience with both. U.S. and UK English are close enough that there's not much difficulty in understanding the other. The main problem is getting the people in England to actually speak English. ;-) [James Knott in opensuse-factory] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2013-10-17 at 19:49 +0200, Christian Boltz wrote:
Hello,
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
After a distro upgrade 12.3 to 13.1 samba file server we have these errors: No builtin backend found, trying to load plugin No builtin nor plugin backend for tdbsam found
It could be caused by the AppArmor profile, see https://bugzilla.novell.com/show_bug.cgi?id=846054 and https://bugzilla.novell.com/show_bug.cgi?id=845867
Packages with an updated profile were accepted today for 13.1 and Factory - updating to the latest apparmor-profiles package (which mentions the above bugs in the changelog) and running "rcapparmor reload" afterwards[1] should help ;-)
If the updated package was not published yet, you can use the apparmor- profiles package from security:apparmor.
Hi Thanks, yes, it is apparmor. Stopping it resolves the issue and smbd fires up OK. However, I already have the latest apparmor package 2.8.2-4.3.1 according to Yast at least. Is there a workaround? Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Donnerstag, 17. Oktober 2013 schrieb lynn:
Thanks, yes, it is apparmor. Stopping it resolves the issue and smbd fires up OK. However, I already have the latest apparmor package 2.8.2-4.3.1 according to Yast at least.
It looks like the updated package was not published yet. You should have # rpm -q --changelog apparmor-profiles |head -n4 * Tue Oct 15 2013 opensuse@cboltz.de - add apparmor-profiles-samba4.diff - various profile additions for samba 4.x (bnc#845867, bnc#846054) - update usr.sbin.winbindd for samba 4.x (bnc#845867, bnc#846054)
Is there a workaround?
Install the apparmor-profiles package from the security:apparmor repo and reload the profiles with "rcapparmor reload". Regards, Christian Boltz -- Achja - deine Fragen sehen wirklich aus wie bei vielen: schwarz, Buchstaben auf weissem Grund..... Aber der Inhalt!!! [Marc-Oliver Roos in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, 2013-10-17 at 23:01 +0200, Christian Boltz wrote:
Hello,
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
Thanks, yes, it is apparmor. Stopping it resolves the issue and smbd fires up OK. However, I already have the latest apparmor package 2.8.2-4.3.1 according to Yast at least.
It looks like the updated package was not published yet.
You should have
# rpm -q --changelog apparmor-profiles |head -n4 * Tue Oct 15 2013 opensuse@cboltz.de - add apparmor-profiles-samba4.diff - various profile additions for samba 4.x (bnc#845867, bnc#846054) - update usr.sbin.winbindd for samba 4.x (bnc#845867, bnc#846054)
Is there a workaround?
Install the apparmor-profiles package from the security:apparmor repo and reload the profiles with "rcapparmor reload".
Hi I have this: # rpm -q --changelog apparmor-profiles |head -n4 * Sun Sep 29 2013 opensuse@cboltz.de - update apparmor-init.py-gsoc.diff to the final GSoC apparmor/__init__.py * Fri Sep 20 2013 opensuse@cboltz.de That's not it I don't think. Will the patch(es) get into 13.1 without need for the security repo if I keep zypper dup'ing? Also, there is another error: Oct 17 23:25:46 altea smbd[546]: [2013/10/17 23:25:46.809451, 0] ../source3/printing/nt_printing.c:164(nt_printing_init) Oct 17 23:25:46 altea smbd[546]: nt_printing_init: error checking published printers: WERR_ACCESS_DENIED Thanks for your help, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Donnerstag, 17. Oktober 2013 schrieb lynn:
On Thu, 2013-10-17 at 23:01 +0200, Christian Boltz wrote:
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
I have this:
# rpm -q --changelog apparmor-profiles |head -n4 * Sun Sep 29 2013 opensuse@cboltz.de - update apparmor-init.py-gsoc.diff to the final GSoC
Will the patch(es) get into 13.1 without need for the security repo if I keep zypper dup'ing?
Sorry, your mail got burried under lots of other mails ;-) The good news is that the fixes are included in the 13.1 repo in the meantime, so yes, you'll get it (or already have it) with zypper dup.
Also, there is another error:
Oct 17 23:25:46 altea smbd[546]: [2013/10/17 23:25:46.809451, 0] ../source3/printing/nt_printing.c:164(nt_printing_init) Oct 17 23:25:46 altea smbd[546]: nt_printing_init: error checking published printers: WERR_ACCESS_DENIED
If you still see this with the latest apparmor profiles, please send me the relevant lines of your /var/log/audit/audit.log (or open a bugreport) Regards, Christian Boltz -- Microsoft is not the Answer - Microsoft is the Question, and the Answer is no ! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2013-11-01 at 00:46 +0100, Christian Boltz wrote:
Hello,
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
On Thu, 2013-10-17 at 23:01 +0200, Christian Boltz wrote:
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
I have this:
# rpm -q --changelog apparmor-profiles |head -n4 * Sun Sep 29 2013 opensuse@cboltz.de - update apparmor-init.py-gsoc.diff to the final GSoC
Will the patch(es) get into 13.1 without need for the security repo if I keep zypper dup'ing?
Sorry, your mail got burried under lots of other mails ;-)
The good news is that the fixes are included in the 13.1 repo in the meantime, so yes, you'll get it (or already have it) with zypper dup.
Also, there is another error:
Oct 17 23:25:46 altea smbd[546]: [2013/10/17 23:25:46.809451, 0] ../source3/printing/nt_printing.c:164(nt_printing_init) Oct 17 23:25:46 altea smbd[546]: nt_printing_init: error checking published printers: WERR_ACCESS_DENIED
If you still see this with the latest apparmor profiles, please send me the relevant lines of your /var/log/audit/audit.log (or open a bugreport)
Hi Thanks for the effort. The error message has gone. Will you close: https://bugzilla.novell.com/show_bug.cgi?id=846586 as resolved? L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Freitag, 1. November 2013 schrieb lynn:
Thanks for the effort. The error message has gone. Will you close: https://bugzilla.novell.com/show_bug.cgi?id=846586 as resolved?
Not yet - I'm still waiting for Lars' feedback (about other samba- related profile additions). @Lars: ping ;-) Regards, Christian Boltz -- "Bei mir" läuft KDE gar nicht. Völlig korrekt. Logisch. Aber sinnfrei. [David Haller in opensuse-de] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 2013-11-01 at 15:49 +0100, Christian Boltz wrote:
Hello,
Am Freitag, 1. November 2013 schrieb lynn:
Thanks for the effort. The error message has gone. Will you close: https://bugzilla.novell.com/show_bug.cgi?id=846586 as resolved?
Not yet - I'm still waiting for Lars' feedback (about other samba- related profile additions).
@Lars: ping ;-)
Hi OK. Would it be possible to include the kerberos and sssd files in the profile whilst the bugzilla is still open? Good opportunity? http://lists.opensuse.org/opensuse-factory/2013-11/msg00019.html Thanks, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Thu, Oct 17, 2013 at 07:24:05PM +0200, lynn wrote:
After a distro upgrade 12.3 to 13.1 samba file server we have these errors: No builtin backend found, trying to load plugin No builtin nor plugin backend for tdbsam found
I've tried deleting the tdb's and rejoining the domain but nothing.
Any ideas anyone?
Are all Samba packages from the same repository and are they on the same release level? rpm -qi ... If you use for example network:samba:STABLE on top of 13.1 you must configure a higher priority for network:samba:STABLE - 80 for example compared to the default 99 - and then update via zypper dup --from network:samba:STABLE I've seen this one time and in that case it was caused by a mix of packages from two different repositories which had the identical, default priority. We might address this on two independent levels: a) (re)introduce a requirement to %version-%relase instead to version of all Requires. b) For winbind we might have to consider a general solution independent from RPM anhow. Cf https://bugzilla.novell.com/show_bug.cgi?id=726937 Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Hello, Am Donnerstag, 17. Oktober 2013 schrieb Lars Müller:
b) For winbind we might have to consider a general solution independent from RPM anhow. Cf https://bugzilla.novell.com/show_bug.cgi?id=726937
"Access denied" :-( Can you make the bug public, or at least provide a short summary? Regards, Christian Boltz -- [Newbie] und wenn wir wollen, daß er ein brauchbarer Regular wird, dann müssen wir uns den korrekt konfigurieren. Nun leider/zum Glück handelt es um einen Menschen. Da ist es nicht mit "vi /etc/sysconfig/grosshirn" und "rcgehirn reload" getan. [Kristian Koehntopp in suse-linux] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, On Thu, Oct 17, 2013 at 11:07:33PM +0200, Christian Boltz wrote:
Am Donnerstag, 17. Oktober 2013 schrieb Lars Müller:
b) For winbind we might have to consider a general solution independent from RPM anhow. Cf https://bugzilla.novell.com/show_bug.cgi?id=726937
"Access denied" :-(
Can you make the bug public, or at least provide a short summary?
The winbindd API version number isn't available from the log. Right now we don't have this information available and still consider how to address this. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
participants (3)
-
Christian Boltz
-
Lars Müller
-
lynn