Re: [AOLSERVER] unclean shutdown
On 2007.03.16, John Buckman [EMAIL PROTECTED] wrote: package require Tclx Good, that confirms my guess. From your previous stacktrace: (gdb) where #0 0x0a00c254 in Tcl_AsyncDelete () #1 0x00649500 in SignalCmdCleanUp () #2 0x0a00f35e in DeleteInterpProc () ... That crash is happening in Tclx's thread cleanup code: http://tclx.cvs.sourceforge.net/tclx/tclx/generic/tclXsignal.c I'm surprised this doesn't cause instability at runtime, but I'm guessing you don't routinely send the nsd signals. When you shut down, are you doing it by issuing a ns_shutdown via the control port (nscp), or by sending it a signal? -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] unclean shutdown
On Mar 17, 2007, at 5:24 AM, Dossy Shiobara wrote: On 2007.03.16, John Buckman [EMAIL PROTECTED] wrote: package require Tclx Good, that confirms my guess. From your previous stacktrace: (gdb) where #0 0x0a00c254 in Tcl_AsyncDelete () #1 0x00649500 in SignalCmdCleanUp () #2 0x0a00f35e in DeleteInterpProc () ... That crash is happening in Tclx's thread cleanup code: http://tclx.cvs.sourceforge.net/tclx/tclx/generic/tclXsignal.c I'm surprised this doesn't cause instability at runtime, but I'm guessing you don't routinely send the nsd signals. Right, I don't use the nsd signals. Is there a patch for that TclX problem? There hasn't been a TclX update in 16 months (http:// sourceforge.net/project/showfiles.php?group_id=13247) but I haven't checked their CVS tree. When you shut down, are you doing it by issuing a ns_shutdown via the control port (nscp), or by sending it a signal? ns_shutdown -john -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] unclean shutdown
On 2007.03.15, John Buckman [EMAIL PROTECTED] wrote: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x0004 [Switching to process 4464 thread 0x4613] 0x0a00c254 in Tcl_AsyncDelete () (gdb) where #0 0x0a00c254 in Tcl_AsyncDelete () #1 0x00649500 in SignalCmdCleanUp () #2 0x0a00f35e in DeleteInterpProc () #3 0x0a00cad5 in Tcl_DeleteInterp () ... What patchlevel of Tcl? -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] unclean shutdown
On Mar 16, 2007, at 6:13 AM, Dossy Shiobara wrote: On 2007.03.15, John Buckman [EMAIL PROTECTED] wrote: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x0004 [Switching to process 4464 thread 0x4613] 0x0a00c254 in Tcl_AsyncDelete () (gdb) where #0 0x0a00c254 in Tcl_AsyncDelete () #1 0x00649500 in SignalCmdCleanUp () #2 0x0a00f35e in DeleteInterpProc () #3 0x0a00cad5 in Tcl_DeleteInterp () ... What patchlevel of Tcl? 8.4.14 - current release. -john -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] unclean shutdown
On 2007.03.16, John Buckman [EMAIL PROTECTED] wrote: What patchlevel of Tcl? 8.4.14 - current release. What modules are you loading? Are you using any of the Tcl async. stuff (introduced in 4.5) in your application code? -- Dossy -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] unclean shutdown
On Mar 16, 2007, at 2:50 PM, Dossy Shiobara wrote: On 2007.03.16, John Buckman [EMAIL PROTECTED] wrote: What patchlevel of Tcl? 8.4.14 - current release. What modules are you loading? Are you using any of the Tcl async. stuff (introduced in 4.5) in your application code? I don't think I'm using any async stuff, at least not in any code I've written, hopefully no library uses it automatically. Here's a list of modules I'm using. nsd is totally stable, running for weeks w/o a reboot, it's just at shutdown that I have a problem, and I should mention that it's not every time. About 75% of the time I do get a clean shutdown. package require ncgi package require struct::list package require tdom package require csv package require crc32 1.3 package require http package require html 1.3 package require Tclx -john -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
[AOLSERVER] unclean shutdown
My shutdowns of aolserver are rarely clean, nsd usually crashes on shutdown. I've started running nsd inside gdb, so I can see where the crash is. Here is a stack trace on a ctrl-c, using the latest cvs source. If there's anything else I can do to help track down these unclean shutdowns, let me know. Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x0004 [Switching to process 4464 thread 0x4613] 0x0a00c254 in Tcl_AsyncDelete () (gdb) where #0 0x0a00c254 in Tcl_AsyncDelete () #1 0x00649500 in SignalCmdCleanUp () #2 0x0a00f35e in DeleteInterpProc () #3 0x0a00cad5 in Tcl_DeleteInterp () #4 0x0007da11 in DeleteData () #5 0x793a in NsCleanupTls () #6 0x891f in FreeThread () #7 0x90024f60 in _pthread_tsd_cleanup () #8 0x90024ae8 in pthread_exit () #9 0x8203 in Ns_ThreadExit () #10 0x0006f6b6 in NsConnThread () #11 0x88ee in ThreadMain () #12 0x90023d87 in _pthread_body () -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to [EMAIL PROTECTED] with the body of SIGNOFF AOLSERVER in the email message. You can leave the Subject: field of your email blank.
