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
Nir Soffer wrote:> > Hi! > > Samba 2.2.4, Linux. > > smbd loses connection to the PDC - although rest of organization feels > fine...Can you set a 'panic action', (panic action = /bin/sleep 9000 works well) and attach a debugger? We need a 'bt full' to see what's going on. Even better if you can compile with -g (--enable-debug configure switch for that).> 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?Interesting theory. That certainly is the SMB signiture (0ff SMB). See what you can get out of the debugger - and the last statements from a high level debug could help. Andrew Bartlett -- Andrew Bartlett abartlet@pcug.org.au Manager, Authentication Subsystems, Samba Team abartlet@samba.org Student Network Administrator, Hawker College abartlet@hawkerc.net http://samba.org http://build.samba.org http://hawkerc.net
> Can you set a 'panic action', (panic action = /bin/sleep 9000 works > well) and attach a debugger? > > We need a 'bt full' to see what's going on. Even better if you can > compile with -g (--enable-debug configure switch for that). > > >> 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 inthe>> 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?> Interesting theory. That certainly is the SMB signiture (0ff SMB).> See what you can get out of the debugger - and the last statementsfrom> a high level debug could help.Grumble grumble. Getting Outlook quoting to work like pine/elm won't be easy. Oh well - to the task at hand... I'm afraid that this has happened only once - and I have no idea what triggered it, so I can't really try to bt it. If I could, I would. :). Am I right in what I thought? The SMB signature should be around offset zero, and not the middle of the packet? If you have any idea what could trigger such a behaviour, I'll be glad to attempt to reproduce this... Otherwise, I'm afraid I'm at a dead end. To elaborate a bit more on the configuration - this is a cluster environment, where two nodes (the ones running smbd) experienced the same symptoms simultenously. This happened on another cluster, and IIRC on both nodes too, albeit two hours later. This has me confused. The PDC could've have been spewing some garbage or something, but that would've crashed several other servers. Yet it didn't. The fact that it happened in two nodes of the same cluster suggests it was some sort of a PDC screw up wrt to the specific NetBIOS name of that cluster... We've been getting several log entries before this crash that had something to do with the fact that it lost the credentials on the PDC. Being of the Windows world, the error code was naturally 0, so all I can tell you that the operation failed because of SUCCESS... :) To make a long and rambling post short - Happened only once, don't know how to reproduce it, will surely do so if/when it happens. Will be glad for some clues as to how to reproduce it. 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
> > Indeed - assuming that NT correctly captured the request. Could it be > the whole IP packet? With the IP header etc?I'll try to decode that a bit an see what I come up with...
Javid Abdul-AJAVID1
2002-Jul-29 10:32 UTC
[Samba] Strange crashes and disconnection from PDC?
I am just curious, how did u fix it, did u just stopped and restarted smbd thanks -----Original Message----- From: Nir Soffer [mailto:nirs@exanet.com] Sent: Sunday, July 28, 2002 6:39 AM To: Andrew Bartlett Cc: samba@samba.org Subject: RE: [Samba] Strange crashes and disconnection from PDC?> Can you set a 'panic action', (panic action = /bin/sleep 9000 works > well) and attach a debugger? > > We need a 'bt full' to see what's going on. Even better if you can > compile with -g (--enable-debug configure switch for that). > > >> 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 inthe>> 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?> Interesting theory. That certainly is the SMB signiture (0ff SMB).> See what you can get out of the debugger - and the last statementsfrom> a high level debug could help.Grumble grumble. Getting Outlook quoting to work like pine/elm won't be easy. Oh well - to the task at hand... I'm afraid that this has happened only once - and I have no idea what triggered it, so I can't really try to bt it. If I could, I would. :). Am I right in what I thought? The SMB signature should be around offset zero, and not the middle of the packet? If you have any idea what could trigger such a behaviour, I'll be glad to attempt to reproduce this... Otherwise, I'm afraid I'm at a dead end. To elaborate a bit more on the configuration - this is a cluster environment, where two nodes (the ones running smbd) experienced the same symptoms simultenously. This happened on another cluster, and IIRC on both nodes too, albeit two hours later. This has me confused. The PDC could've have been spewing some garbage or something, but that would've crashed several other servers. Yet it didn't. The fact that it happened in two nodes of the same cluster suggests it was some sort of a PDC screw up wrt to the specific NetBIOS name of that cluster... We've been getting several log entries before this crash that had something to do with the fact that it lost the credentials on the PDC. Being of the Windows world, the error code was naturally 0, so all I can tell you that the operation failed because of SUCCESS... :) To make a long and rambling post short - Happened only once, don't know how to reproduce it, will surely do so if/when it happens. Will be glad for some clues as to how to reproduce it. 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 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba