Environment
Open Enterprise Server 2015 (OES 2015) Linux Support Pack 1
Situation
- rcnovell-cifs status or /etc/init.d/novell-cifs status report dead
- cifs/cifds stops for no apparent reason
- cifsd core dumps
- /var/log/cifs/cifs.log (in debug level) reports messages such as
MMM DD HH:MM:SS <Servername> CIFS[<PID>]: WARNING: NBNS: nbns process exiting as cifs process ceased to existMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: ENTRY: Shutdown, process going downMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: SIGTERM handler is waiting for NBNSUDPReceiveRoutine to exitMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: Shutdown, NBNS main thread is waiting for SIGTERM handler thread to exitMMM DD HH:MM:SS <Servername> CIFS[<PID>]: DEBUG: NBNS: NBNSReleaseNames: Releasing name: <Servername>MMM DD HH:MM:SS <Servername> CIFS[<PID>]: DEBUG: NBNS: NBNSUdpSendNAmePacket:port =<Port> IP= 255.255.255.255MMM DD HH:MM:SS <Servername> CIFS[<PID>]: DEBUG: NBNS: NBNSUdpSendNAmePacket:port =<Port> IP= 255.255.255.255MMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: NBNSReleaseNames: Cleared NetBIOS name "<Servername> " from NBNS listMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: NBNSReleaseNames: Cleared NetBIOS name "<Servername> " from NBNS listMMM DD HH:MM:SS <Servername> CIFS[<PID>]: DEBUG: NBNS: NBNSUdpSendNAmePacket:port =<Port> IP= 255.255.255.255MMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: NBNSReleaseNames: Cleared NetBIOS name "<Workgroup> " from NBNS listMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: NBNS: Shutdown, NBNS process is exiting from main threadMMM DD HH:MM:SS <Servername> CIFS[<PID>]: EVENT: ENTRY: SHUTDOWN: process is exiting from main thread
Resolution
This is fixed in version novell-cifs-1.8.0-0.289.18 available with the oes2015sp1-May-2017-Scheduled-Maintenance patch from the channel.
Cause
This could be caused by an incoming request from another server. More details cannot be given as this could be used as the basis for a DOS attack on unpatched servers.
Status
Reported to EngineeringAdditional Information
To find out more about the signature or fingerprint of this failure, use novell-getcore (see TID 7004526 Section 7) to package the core file, then extract the file /tmp/novell-getcore_gdb_command_output.<PID> from that package and examine it for the following:
# GDBCMDSTART bt#0 0x00007fbfa4140875 in raise () from /lib64/libc.so.6#1 0x00007fbfa4141e51 in abort () from /lib64/libc.so.6#2 0x00007fbfa4139740 in __assert_fail () from /lib64/libc.so.6#3 0x00007fbf9268441f in ?? () from /opt/novell/xad/lib64/gss/mech_cifs_ntlm.so#4 0x00007fbf9268331f in ?? () from /opt/novell/xad/lib64/gss/mech_cifs_ntlm.so#5 0x00007fbf9268381f in gss_accept_sec_context () from /opt/novell/xad/lib64/gss/mech_cifs_ntlm.so#6 0x00007fbfa538ec88 in gss_accept_sec_context () from /opt/novell/xad/lib64/libgssapi.so.1#7 0x00007fbf8ec14983 in ?? () from /opt/novell/xad/lib64/gss/mech_spnego.so#8 0x00007fbfa538ec88 in gss_accept_sec_context () from /opt/novell/xad/lib64/libgssapi.so.1#9 0x00000000004c3a29 in ?? ()#10 0x00000000004a267f in ?? ()#11 0x0000000000447a28 in ?? ()#12 0x000000000044716d in ?? ()#13 0x000000000046c504 in ?? ()#14 0x0000000000485618 in ?? ()#15 0x0000000000445d6a in ?? ()#16 0x000000000044614e in ?? ()#17 0x0000000000446a59 in ?? ()#18 0x0000000000444b3a in ?? ()#19 0x0000000000412e47 in ?? ()#20 0x00007fbfa6ea3806 in start_thread () from /lib64/libpthread.so.0#21 0x00007fbfa41ec67d in clone () from /lib64/libc.so.6#22 0x0000000000000000 in ?? ()# GDBCMDEND bt