On Wed, 2016-02-10 at 14:32 -0500, Diego Remolina wrote: > I actually had this problem with CentOS 7 and glusterfs 3.7.x > > I downgraded to 3.6.x and the crashes stopped. > > See https://bugzilla.redhat.com/show_bug.cgi?id=1234877 > > It may be the same issue. > Probably not. This issue was root caused to an upstream Samba bug[1]. Following that new packages containing the fix were built sometime before (see comments #22 through #25 from the BZ mentioned above) and BZ was closed on receiving confirmation from reporter of the bug saying that crashes/coredumps were no longer seen. > I am still in the old samba-vfs-glusterfs-4.1.12-23.el7_1.x86_64 and > glusterfs-3.6.6-1.el7.x86_64 on that machine and see no crashes. > > Diego > > On Wed, Feb 10, 2016 at 2:19 PM, Glomski, Patrick > <patrick.glomski@xxxxxxxxxxxxx> wrote: > > I am running an SL7.2 machine with the samba version 4.2.4 hosted > > at > > download.gluster.org. I use the samba glusterfs virtual filesystem > > to > > connect to a 3.6.6 gluster array. Periodically (every hour or so > > when in > > use) smbd will panic, crash, and restart. Users don't seem to be > > complaining > > about it, but the fact that it keeps crashing is worrisome. Does > > anyone know > > if this issue has a bug or is fixed in a newer version of the > > glusterfs vfs > > plugin? I've attached an excerpt from /var/log/messages and a core > > dump. > > > > # cat /etc/redhat-release; echo "samba: $(smbd --version)"; echo > > "vfs: $(rpm > > -qa | grep vfs-glusterfs)" > > > > Scientific Linux release 7.2 (Nitrogen) > > samba: Version 4.2.4 > > vfs: samba-vfs-glusterfs-4.2.4-6.el7.centos.x86_64 > > Samba 4.2.4 includes the upstream bug fix [1]. So we suspect another problem to be debugged. > > /var/log/messages panic > > ####################### > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.329296, 0] > > ../lib/util/fault.c:78(fault_report) > > Feb 10 12:38:11 sb1 smbd[4880]: > > =============================================================== > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.329342, 0] > > ../lib/util/fault.c:79(fault_report) > > Feb 10 12:38:11 sb1 smbd[4880]: INTERNAL ERROR: Signal 6 in pid > > 4880 > > (4.2.4) > > Feb 10 12:38:11 sb1 smbd[4880]: Please read the Trouble-Shooting > > section of > > the Samba HOWTO > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.329365, 0] > > ../lib/util/fault.c:81(fault_report) > > Feb 10 12:38:11 sb1 smbd[4880]: > > =============================================================== > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.329390, 0] > > ../source3/lib/util.c:788(smb_panic_s3) > > Feb 10 12:38:11 sb1 smbd[4880]: PANIC (pid 4880): internal error > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.329633, 0] > > ../source3/lib/util.c:899(log_stack_trace) > > Feb 10 12:38:11 sb1 smbd[4880]: BACKTRACE: 12 stack frames: > > Feb 10 12:38:11 sb1 smbd[4880]: #0 > > /lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x7f24d03ced5a] > > Feb 10 12:38:11 sb1 smbd[4880]: #1 > > /lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f24d03cee30] > > Feb 10 12:38:11 sb1 smbd[4880]: #2 > > /lib64/libsamba-util.so.0(smb_panic+0x2f) [0x7f24d221e87f] > > Feb 10 12:38:11 sb1 smbd[4880]: #3 /lib64/libsamba- > > util.so.0(+0x1aa96) > > [0x7f24d221ea96] > > Feb 10 12:38:11 sb1 smbd[4880]: #4 > > /lib64/libpthread.so.0(+0xf100) > > [0x7f24d2447100] > > Feb 10 12:38:11 sb1 smbd[4880]: #5 /lib64/libc.so.6(gsignal+0x37) > > [0x7f24cea7d5f7] > > Feb 10 12:38:11 sb1 smbd[4880]: #6 /lib64/libc.so.6(abort+0x148) > > [0x7f24cea7ece8] > > Feb 10 12:38:11 sb1 smbd[4880]: #7 /lib64/libc.so.6(+0x75317) > > [0x7f24ceabd317] > > Feb 10 12:38:11 sb1 smbd[4880]: #8 /lib64/libc.so.6(+0x7cfe1) > > [0x7f24ceac4fe1] > > Feb 10 12:38:11 sb1 smbd[4880]: #9 > > /lib64/libglusterfs.so.0(gf_timer_proc+0x251) [0x7f24b75cc961] > > Feb 10 12:38:11 sb1 smbd[4880]: #10 > > /lib64/libpthread.so.0(+0x7dc5) > > [0x7f24d243fdc5] > > Feb 10 12:38:11 sb1 smbd[4880]: #11 /lib64/libc.so.6(clone+0x6d) > > [0x7f24ceb3e21d] > > Feb 10 12:38:11 sb1 smbd[4880]: [2016/02/10 12:38:11.330887, 0] > > ../source3/lib/dumpcore.c:318(dump_core) > > Feb 10 12:38:11 sb1 smbd[4880]: dumping core in > > /var/log/samba/cores/smbd > > Feb 10 12:38:11 sb1 smbd[4880]: > > Feb 10 12:38:11 sb1 abrt-server: Package 'samba' isn't signed with > > proper > > key > > Feb 10 12:38:11 sb1 abrt-server: 'post-create' on > > '/var/spool/abrt/ccpp-2016-02-10-12:38:11-4880' exited with 1 > > Feb 10 12:38:11 sb1 abrt-server: Deleting problem directory > > '/var/spool/abrt/ccpp-2016-02-10-12:38:11-4880' > > This back trace is different from what we have in the BZ #1234877. So this need to be root caused. And I remember some other community user reporting a similar issue with samba 4.2.4 and glusterfs 3.7.x on irc. Can you please file a bug attaching the core dump and explaining the issue in detail? [1] https://bugzilla.samba.org/show_bug.cgi?id=11115 --Anoop C S. > > Thanks, > > Patrick > > > > _______________________________________________ > > Gluster-users mailing list > > Gluster-users@xxxxxxxxxxx > > http://www.gluster.org/mailman/listinfo/gluster-users > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
