Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
-> $ systemctl restart smb.service
Starting Samba SMB Daemon... [2022/06/08 19:17:32.937351, 0, pid=49122] ../../source3/smbd/server.c:1741(main) smbd version 4.16.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2022/06/08 19:17:32.960756, 0, pid=49122] ../../lib/util/fault.c:172(smb_panic_log) =============================================================== [2022/06/08 19:17:32.960925, 0, pid=49122] ../../lib/util/fault.c:176(smb_panic_log) INTERNAL ERROR: Signal 6: Aborted in pid 49122 (4.16.1) [2022/06/08 19:17:32.960981, 0, pid=49122] ../../lib/util/fault.c:181(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2022/06/08 19:17:32.961022, 0, pid=49122] ../../lib/util/fault.c:182(smb_panic_log) =============================================================== [2022/06/08 19:17:32.961056, 0, pid=49122] ../../lib/util/fault.c:184(smb_panic_log) PANIC (pid 49122): Signal 6: Aborted in 4.16.1 [2022/06/08 19:17:32.961647, 0, pid=49122] ../../lib/util/fault.c:288(log_stack_trace) BACKTRACE: 15 stack frames: #0 /lib64/libsamba-util.so.0(log_stack_trace+0x34) [0x7f41bbc0c7c4] #1 /lib64/libsamba-util.so.0(smb_panic+0xd) [0x7f41bbc0ca1d] #2 /lib64/libsamba-util.so.0(+0xeab9) [0x7f41bbc0cab9] #3 /lib64/libpthread.so.0(+0x12ce0) [0x7f41bb83bce0] #4 /lib64/libc.so.6(gsignal+0x10f) [0x7f41bb2a4a4f] #5 /lib64/libc.so.6(abort+0x127) [0x7f41bb277db5] #6 /lib64/libtalloc.so.2(+0x2f40) [0x7f41a34a7f40] #7 /lib64/libtalloc.so.2(+0x336c) [0x7f41a34a836c] #8 /usr/lib64/samba/pdb/ipasam.so(+0x11c2f) [0x7f41a38e7c2f] #9 /lib64/libsamba-passdb.so.0(make_pdb_method_name+0xb2) [0x7f41bbdae2f2] #10 /lib64/libsamba-passdb.so.0(+0x1d604) [0x7f41bbdae604] #11 /lib64/libsamba-passdb.so.0(initialize_password_db+0x1d) [0x7f41bbdb096d] #12 /usr/sbin/smbd(main+0x5d9) [0x55c945bbcf09] #13 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f41bb290ca3] #14 /usr/sbin/smbd(_start+0x2e) [0x55c945bbe6de] [2022/06/08 19:17:32.962008, 0, pid=49122] ../../source3/lib/dumpcore.c:318(dump_core) coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smb.service: Main process exited, code=dumped, status=6/ABRT smb.service: Failed with result 'core-dump'. Failed to start Samba SMB Daemon.
many thanks, L.
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
What bug report? Can you point to it?
The only problem I know about is a missing SELinux policy extension for samba-dcerpcd daemon which prevent ipasam module from loading. samba-dcerpcd got a new SELinux context which is not allowed to do anything that ipasam is supposed to do: read /etc/krb5.conf, initialize openssl configuration, communicate with LDAP server, etc.
This is handled in https://bugzilla.redhat.com/show_bug.cgi?id=2096521 for RHEL 9.1 (C9S) and in https://bugzilla.redhat.com/show_bug.cgi?id=2096825 for RHEL 8.7 (C8S).
A workaround is to put SELinux into permissive mode until SELinux folks would produce a fix -- or apply a local policy extension described in the bugzillas.
-> $ systemctl restart smb.service
Starting Samba SMB Daemon... [2022/06/08 19:17:32.937351, 0, pid=49122] ../../source3/smbd/server.c:1741(main) smbd version 4.16.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2022/06/08 19:17:32.960756, 0, pid=49122] ../../lib/util/fault.c:172(smb_panic_log) =============================================================== [2022/06/08 19:17:32.960925, 0, pid=49122] ../../lib/util/fault.c:176(smb_panic_log) INTERNAL ERROR: Signal 6: Aborted in pid 49122 (4.16.1) [2022/06/08 19:17:32.960981, 0, pid=49122] ../../lib/util/fault.c:181(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2022/06/08 19:17:32.961022, 0, pid=49122] ../../lib/util/fault.c:182(smb_panic_log) =============================================================== [2022/06/08 19:17:32.961056, 0, pid=49122] ../../lib/util/fault.c:184(smb_panic_log) PANIC (pid 49122): Signal 6: Aborted in 4.16.1 [2022/06/08 19:17:32.961647, 0, pid=49122] ../../lib/util/fault.c:288(log_stack_trace) BACKTRACE: 15 stack frames: #0 /lib64/libsamba-util.so.0(log_stack_trace+0x34) [0x7f41bbc0c7c4] #1 /lib64/libsamba-util.so.0(smb_panic+0xd) [0x7f41bbc0ca1d] #2 /lib64/libsamba-util.so.0(+0xeab9) [0x7f41bbc0cab9] #3 /lib64/libpthread.so.0(+0x12ce0) [0x7f41bb83bce0] #4 /lib64/libc.so.6(gsignal+0x10f) [0x7f41bb2a4a4f] #5 /lib64/libc.so.6(abort+0x127) [0x7f41bb277db5] #6 /lib64/libtalloc.so.2(+0x2f40) [0x7f41a34a7f40] #7 /lib64/libtalloc.so.2(+0x336c) [0x7f41a34a836c] #8 /usr/lib64/samba/pdb/ipasam.so(+0x11c2f) [0x7f41a38e7c2f] #9 /lib64/libsamba-passdb.so.0(make_pdb_method_name+0xb2) [0x7f41bbdae2f2] #10 /lib64/libsamba-passdb.so.0(+0x1d604) [0x7f41bbdae604] #11 /lib64/libsamba-passdb.so.0(initialize_password_db+0x1d) [0x7f41bbdb096d] #12 /usr/sbin/smbd(main+0x5d9) [0x55c945bbcf09] #13 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f41bb290ca3] #14 /usr/sbin/smbd(_start+0x2e) [0x55c945bbe6de] [2022/06/08 19:17:32.962008, 0, pid=49122] ../../source3/lib/dumpcore.c:318(dump_core) coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smb.service: Main process exited, code=dumped, status=6/ABRT smb.service: Failed with result 'core-dump'. Failed to start Samba SMB Daemon.
many thanks, L. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 15/06/2022 08:58, Alexander Bokovoy wrote:
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
What bug report? Can you point to it?
The only problem I know about is a missing SELinux policy extension for samba-dcerpcd daemon which prevent ipasam module from loading. samba-dcerpcd got a new SELinux context which is not allowed to do anything that ipasam is supposed to do: read /etc/krb5.conf, initialize openssl configuration, communicate with LDAP server, etc.
This is handled in https://bugzilla.redhat.com/show_bug.cgi?id=2096521 for RHEL 9.1 (C9S) and in https://bugzilla.redhat.com/show_bug.cgi?id=2096825 for RHEL 8.7 (C8S).
A workaround is to put SELinux into permissive mode until SELinux folks would produce a fix -- or apply a local policy extension described in the bugzillas.
Pretty much the same as what I showed below, is in that BZ - https://bugzilla.redhat.com/show_bug.cgi?id=2094975 I did not think it had to do with SELinux, which I put into permissive and still got a crash as below. Is not very critical as Samba from appstream repo (also 4.16) works, only no gluster's libgfapi.
many thanks,
-> $ systemctl restart smb.service
Starting Samba SMB Daemon... [2022/06/08 19:17:32.937351, 0, pid=49122] ../../source3/smbd/server.c:1741(main) smbd version 4.16.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2022/06/08 19:17:32.960756, 0, pid=49122] ../../lib/util/fault.c:172(smb_panic_log) ===============================================================
[2022/06/08 19:17:32.960925, 0, pid=49122] ../../lib/util/fault.c:176(smb_panic_log) INTERNAL ERROR: Signal 6: Aborted in pid 49122 (4.16.1) [2022/06/08 19:17:32.960981, 0, pid=49122] ../../lib/util/fault.c:181(smb_panic_log) If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting [2022/06/08 19:17:32.961022, 0, pid=49122] ../../lib/util/fault.c:182(smb_panic_log) ===============================================================
[2022/06/08 19:17:32.961056, 0, pid=49122] ../../lib/util/fault.c:184(smb_panic_log) PANIC (pid 49122): Signal 6: Aborted in 4.16.1 [2022/06/08 19:17:32.961647, 0, pid=49122] ../../lib/util/fault.c:288(log_stack_trace) BACKTRACE: 15 stack frames: #0 /lib64/libsamba-util.so.0(log_stack_trace+0x34) [0x7f41bbc0c7c4] #1 /lib64/libsamba-util.so.0(smb_panic+0xd) [0x7f41bbc0ca1d] #2 /lib64/libsamba-util.so.0(+0xeab9) [0x7f41bbc0cab9] #3 /lib64/libpthread.so.0(+0x12ce0) [0x7f41bb83bce0] #4 /lib64/libc.so.6(gsignal+0x10f) [0x7f41bb2a4a4f] #5 /lib64/libc.so.6(abort+0x127) [0x7f41bb277db5] #6 /lib64/libtalloc.so.2(+0x2f40) [0x7f41a34a7f40] #7 /lib64/libtalloc.so.2(+0x336c) [0x7f41a34a836c] #8 /usr/lib64/samba/pdb/ipasam.so(+0x11c2f) [0x7f41a38e7c2f] #9 /lib64/libsamba-passdb.so.0(make_pdb_method_name+0xb2) [0x7f41bbdae2f2] #10 /lib64/libsamba-passdb.so.0(+0x1d604) [0x7f41bbdae604] #11 /lib64/libsamba-passdb.so.0(initialize_password_db+0x1d) [0x7f41bbdb096d] #12 /usr/sbin/smbd(main+0x5d9) [0x55c945bbcf09] #13 /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f41bb290ca3] #14 /usr/sbin/smbd(_start+0x2e) [0x55c945bbe6de] [2022/06/08 19:17:32.962008, 0, pid=49122] ../../source3/lib/dumpcore.c:318(dump_core) coredump is handled by helper binary specified at /proc/sys/kernel/core_pattern
smb.service: Main process exited, code=dumped, status=6/ABRT smb.service: Failed with result 'core-dump'. Failed to start Samba SMB Daemon.
many thanks, L. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, 2022-06-15 at 10:25 +0100, lejeczek via CentOS-devel wrote:
On 15/06/2022 08:58, Alexander Bokovoy wrote:
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
What bug report? Can you point to it?
The only problem I know about is a missing SELinux policy extension for samba-dcerpcd daemon which prevent ipasam module from loading. samba-dcerpcd got a new SELinux context which is not allowed to do anything that ipasam is supposed to do: read /etc/krb5.conf, initialize openssl configuration, communicate with LDAP server, etc.
This is handled in https://bugzilla.redhat.com/show_bug.cgi?id=2096521 for RHEL 9.1 (C9S) and in https://bugzilla.redhat.com/show_bug.cgi?id=2096825%C2%A0for RHEL 8.7 (C8S).
A workaround is to put SELinux into permissive mode until SELinux folks would produce a fix -- or apply a local policy extension described in the bugzillas.
Pretty much the same as what I showed below, is in that BZ - https://bugzilla.redhat.com/show_bug.cgi?id=2094975 I did not think it had to do with SELinux, which I put into permissive and still got a crash as below. Is not very critical as Samba from appstream repo (also 4.16) works, only no gluster's libgfapi.
That's interesting..can you please get debug level 10 logs while starting smbd with Samba(v4.16) packages from centos-release-samba416 repository?
Anoop C S.
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
On 15/06/2022 08:58, Alexander Bokovoy wrote:
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
What bug report? Can you point to it?
The only problem I know about is a missing SELinux policy extension for samba-dcerpcd daemon which prevent ipasam module from loading. samba-dcerpcd got a new SELinux context which is not allowed to do anything that ipasam is supposed to do: read /etc/krb5.conf, initialize openssl configuration, communicate with LDAP server, etc.
This is handled in https://bugzilla.redhat.com/show_bug.cgi?id=2096521 for RHEL 9.1 (C9S) and in https://bugzilla.redhat.com/show_bug.cgi?id=2096825 for RHEL 8.7 (C8S).
A workaround is to put SELinux into permissive mode until SELinux folks would produce a fix -- or apply a local policy extension described in the bugzillas.
Pretty much the same as what I showed below, is in that BZ - https://bugzilla.redhat.com/show_bug.cgi?id=2094975 I did not think it had to do with SELinux, which I put into permissive and still got a crash as below. Is not very critical as Samba from appstream repo (also 4.16) works, only no gluster's libgfapi.
This one (from SIG) is built with embedded Samba libraries. It is unsupported to mix system-provided and embedded libraries, so crash is not surprising. Anoop and I talked and he is going to rethink CentOS Stream repo design because the current one was done for pre-Stream state of affairs when new Samba version was not available in CentOS before RHEL GA.
Mixing this repo and IPA builds in CentOS Stream is not supported, to make it clear. ;)
On 15/06/2022 13:25, Alexander Bokovoy wrote:
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
On 15/06/2022 08:58, Alexander Bokovoy wrote:
On ke, 15 kesä 2022, lejeczek via CentOS-devel wrote:
Hi guys.
I filed a bug report with RH's Bugzilla but nothing happened there thus thought I'd let - if SIGs read this list - you guys know that Samba 4.16 is broken, hard-crashes. For better picture - Samba is managed by IPA
What bug report? Can you point to it?
The only problem I know about is a missing SELinux policy extension for samba-dcerpcd daemon which prevent ipasam module from loading. samba-dcerpcd got a new SELinux context which is not allowed to do anything that ipasam is supposed to do: read /etc/krb5.conf, initialize openssl configuration, communicate with LDAP server, etc.
This is handled in https://bugzilla.redhat.com/show_bug.cgi?id=2096521 for RHEL 9.1 (C9S) and in https://bugzilla.redhat.com/show_bug.cgi?id=2096825 for RHEL 8.7 (C8S).
A workaround is to put SELinux into permissive mode until SELinux folks would produce a fix -- or apply a local policy extension described in the bugzillas.
Pretty much the same as what I showed below, is in that BZ - https://bugzilla.redhat.com/show_bug.cgi?id=2094975 I did not think it had to do with SELinux, which I put into permissive and still got a crash as below. Is not very critical as Samba from appstream repo (also 4.16) works, only no gluster's libgfapi.
This one (from SIG) is built with embedded Samba libraries. It is unsupported to mix system-provided and embedded libraries, so crash is not surprising. Anoop and I talked and he is going to rethink CentOS Stream repo design because the current one was done for pre-Stream state of affairs when new Samba version was not available in CentOS before RHEL GA.
Mixing this repo and IPA builds in CentOS Stream is not supported, to make it clear. ;)
Well, it worked well and yes with IPA, all the time I can remember with c8 and recently with c8s as well, well. Issues I have plus others I know, is that Gluster libgfapi is absent in baseos/default repo Samba.
thanks, L