two OSX bugs
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > AOL Webserver > two OSX bugs




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    two OSX bugs  
John Buckman


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
08-07-07 12:11 AM

I've had these two bugs for a while on OSX, thought I'd report them.
I'm running today's current CVS.

------------------
Bug #1: nszlib causes "abort trap" on OSX.

007:23:52:46][16387.2684407808][-main-] Notice: modload: loading '/
usr/local/aolserver/bin/nszlib.so'
[06/Aug/2007:23:52:48][16387.2684407808][-main-] Notice: conf: &
#91;ns/
server/BookMooch]enabletclpages = 0
[06/Aug/2007:23:52:48][16387.2684407808][-main-] Notice: default
thread pool: minthreads 0 maxthreads 10 idle 0 current 0 maxconns 0
queued 0 timeout 0
alloc: invalid block: 0x27e000: ef ef 80
./aol: line 4: 16387 Abort trap              sudo bin/nsd -ft
config.tcl -u john -b 127.0.0.1:81

if I don't use nszlib, I have no such problems. Also, nszlib works
fine for me on Linux. I haven't reported the problem before, because
I develop on OSX, but my servers are Linux, so not having zlib during
debugging isn't a big deal.

Program received signal SIGABRT, Aborted.
0x9003d66c in kill ()
(gdb) where
#0  0x9003d66c in kill ()
#1  0x9010e8cf in raise ()
#2  0x9010d422 in abort ()
#3  0x0a05788e in Tcl_PanicVA ()
#4  0x0a0578a9 in Tcl_Panic ()
#5  0x0a064fdb in TclpFree ()
#6  0x0a00e9c2 in Tcl_DeleteCommandFromToken ()
#7  0x0a0526fc in TclTeardownNamespace ()
#8  0x0a00f172 in DeleteInterpProc ()
#9  0x0a00c9b1 in Tcl_DeleteInterp ()
#10 0x0007d60c in PushInterp ()
#11 0x0007467b in NsInitServer ()
#12 0x0006d85e in Ns_Main ()
#13 0x00002a7e in main ()
------------------

Bug #2: occasional crash on OSX, when threads give notice of timeout
waiting for connection

The gdb stack trace is a bit more useful in this case:

[07/Aug/2007:00:05:15][16497.25228800][-nssock:driver-] Notice:
nssock: listening on 127.0.0.1:81
[07/Aug/2007:00:05:24][16497.25229824][-conn:0-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:24][16497.25203712][-conn:5-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:24][16497.25230848][-conn:2-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:24][16497.25229824][-conn:1-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:24][16497.25202688][-conn:4-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:24][16497.25201664][-conn:3-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25203712][-conn:6-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25229824][-conn:7-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25202688][-conn:9-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25204736][-conn:8-] Notice: exiting
:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25201664][-conn:10-] Notice: exitin
g:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25203712][-conn:11-] Notice: exitin
g:
timeout waiting for connection
[07/Aug/2007:00:05:25][16497.25202688][-conn:12-] Notice: exitin
g:
timeout waiting for connection

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
[Switching to process 16497 thread 0x3a0b]
0x0a00c130 in Tcl_AsyncDelete ()
(gdb) where
#0  0x0a00c130 in Tcl_AsyncDelete ()
#1  0x00655500 in SignalCmdCleanUp ()
#2  0x0a00f23a in DeleteInterpProc ()
#3  0x0a00c9b1 in Tcl_DeleteInterp ()
#4  0x0007da21 in DeleteData ()
#5  0x0000793a in NsCleanupTls ()
#6  0x0000891f in FreeThread ()
#7  0x90025400 in _pthread_tsd_cleanup ()
#8  0x90024f88 in pthread_exit ()
#9  0x00008203 in Ns_ThreadExit ()
#10 0x0006f756 in NsConnThread ()
#11 0x000088ee in ThreadMain ()
#12 0x90024227 in _pthread_body ()
(gdb)

This doesn't consistently occur, but it's often enough that I run nsd
in a re-starting shell script while running on OSX.

------

I wish I could be more helpful and actually give a C code patch for
these, but they're not aggravating enough for me to spend the ramp-up
time figuring how to fix this sort of thing, but I thought at least I
should report them so they could be logged.

-john







[ Post a follow-up to this message ]



    Re: two OSX bugs  
John Buckman


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
08-07-07 12:11 AM

I banged on this thread-time-crash-on-OSX bug a bit, and found that
setting
ns_param   threadtimeout   10000       ;# Idle threads die at this rate

gets rid of this problem. While setting
ns_param   threadtimeout   0       ;# Idle threads die at this rate

or
ns_param   threadtimeout  1       ;# Idle threads die at this rate

causes the problem to come back. So, it seems the problem is
generally with idle threads being shut down.

-john


> Bug #2: occasional crash on OSX, when threads give notice of
> timeout waiting for connection
>
> The gdb stack trace is a bit more useful in this case:
>
> [07/Aug/2007:00:05:15][16497.25228800][-nssock:driver-] Notice
:
> nssock: listening on 127.0.0.1:81
> [07/Aug/2007:00:05:24][16497.25229824][-conn:0-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:24][16497.25203712][-conn:5-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:24][16497.25230848][-conn:2-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:24][16497.25229824][-conn:1-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:24][16497.25202688][-conn:4-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:24][16497.25201664][-conn:3-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25203712][-conn:6-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25229824][-conn:7-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25202688][-conn:9-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25204736][-conn:8-] Notice: exiti
ng:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25201664][-conn:10-] Notice: exit
ing:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25203712][-conn:11-] Notice: exit
ing:
> timeout waiting for connection
> [07/Aug/2007:00:05:25][16497.25202688][-conn:12-] Notice: exit
ing:
> timeout waiting for connection
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
> [Switching to process 16497 thread 0x3a0b]
> 0x0a00c130 in Tcl_AsyncDelete ()
> (gdb) where
> #0  0x0a00c130 in Tcl_AsyncDelete ()
> #1  0x00655500 in SignalCmdCleanUp ()
> #2  0x0a00f23a in DeleteInterpProc ()
> #3  0x0a00c9b1 in Tcl_DeleteInterp ()
> #4  0x0007da21 in DeleteData ()
> #5  0x0000793a in NsCleanupTls ()
> #6  0x0000891f in FreeThread ()
> #7  0x90025400 in _pthread_tsd_cleanup ()
> #8  0x90024f88 in pthread_exit ()
> #9  0x00008203 in Ns_ThreadExit ()
> #10 0x0006f756 in NsConnThread ()
> #11 0x000088ee in ThreadMain ()
> #12 0x90024227 in _pthread_body ()
> (gdb)
>
> This doesn't consistently occur, but it's often enough that I run
> nsd in a re-starting shell script while running on OSX.
>
> ------
>
> I wish I could be more helpful and actually give a C code patch for
> these, but they're not aggravating enough for me to spend the ramp-
> up time figuring how to fix this sort of thing, but I thought at
> least I should report them so they could be logged.
>
> -john
>
>







[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 05:22 AM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register