[Samba] Strange crashes and disconnection from PDC?

[Nir Soffer]

Hi!

Samba 2.2.4, Linux.

smbd loses connection to the PDC - although rest of organization feels
fine...

I've had the following cropping up:
Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0]
lib/fault.c:fault_report(38)  
Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0]
lib/fault.c:fault_report(39)  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:   Please read the file BUGS.txt in
the distribution  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:
===============================================================  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:   INTERNAL ERROR: Signal 11 in pid
6994 (2.2.4)  
Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0]
lib/fault.c:fault_report(41)  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:
===============================================================  
Jul 25 07:40:13 10.17.0.2 smbd[6994]: [2002/07/25 07:40:13, 0]
lib/util.c:smb_panic(1092)  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:   PANIC: internal error  
Jul 25 07:40:13 10.17.0.2 smbd[6994]:  



In some correlation - these messages popped up on the PDC....
Disregard the IPs. They are different interfaces.

Event Type:	Error
Event Source:	Srv
Event Category:	None
Event ID:	2006
Date:		7/28/2002
Time:		8:18:20 AM
User:		N/A
Computer:	HAWK
Description:
The server received an incorrectly formatted request from \\10.0.10.12. 
Data:
0000: 00 00 34 00 02 00 7c 00   ..4...|.
0008: 00 00 00 00 d6 07 00 c0   ....?..?
0010: 00 00 00 00 01 20 98 c0   ..... ??
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: b3 06 00 00 ff 53 4d 42   ³...?SMB
0030: 25 00 00 00 00 08 01 c0   %......?
0038: 00 00 00 00 00 00 00 00   ........
0040: 00 00 00 00 06 18 bb 68   ......»h
0048: 00 30 01 00 10 00 00 48   .0.....H
0050: 00 00 00 48 00 00 00 00   ...H....
0058: 00 00 00 00               ....    


I'll be glad if anyone has any ideas... Is this is a known issue in
2.2.4? Has it been resolved? Isn't the SMB Magic supposed to be in the
beggining of the packet and not in the middle? Could this be some 
buffer going ballistic and screwing up the alignment of the packet 
with something else, consequently causing a SIGSEGV?

Thanks,
Nir.

--
Nir Soffer -=- Software Engineer, Exanet Inc. -=-
"Father, why are all the children weeping? / They are merely crying son
 O, are they merely crying, father? / Yes, true weeping is yet to come"
        -- Nick Cave and the Bad Seeds, The Weeping Song