I have an ES 3.0 kernel 2.4.21-4.ELsmp with samba version 3.0.2-6.3E that
has been running flawlessly for past 6 months, but has recently started
crashing smbd processes when a Windows 98 user tries to print to a shared
printer on the server. /var/log/messages reports the crash something like
this example:

Dec 16 07:16:43 sch smbd[3593]: [2004/12/16 07:16:43, 0]
lib/fault.c:fault_report(36)
Dec 16 07:16:43 sch smbd[3593]:   ==================================
Dec 16 07:16:43 sch smbd[3593]: [2004/12/16 07:16:43, 0]
lib/fault.c:fault_report(37)
Dec 16 07:16:43 sch smbd[3593]:   INTERNAL ERROR: Signal 11 in pid 3593
(3.0.2-6.3E)
Dec 16 07:16:43 sch smbd[3593]:   Please read the appendix Bugs of the S
amba
HOWTO collection
Dec 16 07:16:43 sch smbd[3593]: [2004/12/16 07:16:43, 0]
lib/fault.c:fault_report(39)
Dec 16 07:16:43 sch smbd[3593]:   ==================================
Dec 16 07:16:43 sch smbd[3593]: [2004/12/16 07:16:43, 0]
lib/util.c:smb_panic(1422)
Dec 16 07:16:43 sch smbd[3593]:   PANIC: internal error
Dec 16 07:16:43 sch smbd[3593]: [2004/12/16 07:16:43, 0]
lib/util.c:smb_panic(1430)
Dec 16 07:16:43 sch smbd[3593]:   BACKTRACE: 15 stack frames:
Dec 16 07:16:43 sch smbd[3593]:    #0 smbd(smb_panic+0x13f) [0x801a6
08f]
Dec 16 07:16:43 sch smbd[3593]:    #1 smbd [0x80191b48]
Dec 16 07:16:43 sch smbd[3593]:    #2 /lib/tls/libc.so.6 [0xb725fc08
]
Dec 16 07:16:43 sch smbd[3593]:    #3 smbd(print_queue_status+0x186)
[0x801c7246]
Dec 16 07:16:43 sch smbd[3593]:    #4 smbd [0x8004eca3]
Dec 16 07:16:43 sch smbd[3593]:    #5 smbd(api_reply+0x1cf) [0x80055
d4f]
Dec 16 07:16:43 sch smbd[3593]:    #6 smbd [0x8004bdae]
Dec 16 07:16:43 sch smbd[3593]:    #7 smbd(reply_trans+0x5ab) [0x800
4c53b]
Dec 16 07:16:43 sch smbd[3593]:    #8 smbd [0x800901f0]
Dec 16 07:16:43 sch smbd[3593]:    #9 smbd [0x80090403]
Dec 16 07:16:43 sch smbd[3593]:    #10 smbd(process_smb+0xa6) [0x800
90656]
Dec 16 07:16:43 sch smbd[3593]:    #11 smbd(smbd_process+0x192) [0x8
00913d2]
Dec 16 07:16:43 sch smbd[3593]:    #12 smbd(main+0x505) [0x8021d345]
Dec 16 07:16:43 sch smbd[3593]:    #13
/lib/tls/libc.so.6(__libc_start_main+0xf8) [0xb724d748]
Dec 16 07:16:43 sch smbd[3593]:    #14 smbd [0x80035a32]

The Windows 98 user only sees a printer-not-available error message. There
are a few Windows XP's that still print to the printer without crash or
error.

I have not run up2date on this server in past 5 months, so I'm sure there
are many updates. I am resorting to see if updating the OS will resolve
issue. Is it a slam-dunk to run up2date when it hasn't been run in a while?
I've done a lot of elimination test/trials, add/remove printer,
virus-checks, etc.
Any ideas appreciated.

[ Post a follow-up to this message ]