[AOLSERVER] nsd crash
I'm managing to get AOLserver 4.5 on FreeBSD 7.0 amd64 to crash every few days. I've upgraded from 4.0.10 on i386 which ran great for years. GDB gives #0 0x000800df3fec in thr_kill () from /lib/libc.so.7 [New Thread 0x80380c290 (LWP 100737)] [New Thread 0x804560120 (LWP 100728)] [New Thread 0x80380c850 (LWP 100725)] [New Thread 0x80380c570 (LWP 100423)] [New Thread 0x8016150f0 (LWP 100789)] [New Thread 0x801614f80 (LWP 100788)] [New Thread 0x801614e10 (LWP 100787)] [New Thread 0x801614ca0 (LWP 100735)] [New Thread 0x801614b30 (LWP 100734)] [New Thread 0x8016149c0 (LWP 100733)] [New Thread 0x801614850 (LWP 100732)] [New Thread 0x8016146e0 (LWP 100731)] [New Thread 0x801614570 (LWP 100730)] [New Thread 0x801614400 (LWP 100322)] [New Thread 0x801614290 (LWP 100471)] [New Thread 0x801614120 (LWP 100341)] [New Thread 0x8010016e0 (LWP 100211)] [New Thread 0x801001570 (LWP 100210)] [New Thread 0x801001400 (LWP 100209)] [New Thread 0x801001290 (LWP 100206)] [New Thread 0x801001120 (LWP 100311)] I've not bulit nsd with debugging symbols which I guess is the next thing I should do. To folk more knowledgeable than me does this give any hints as to whether its a FreeBSD threading thing or a problem with AOLserver ? What should I do next to track down the problem ? Many thanks Bernhard -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd crash
Hello Bernhard, I recommend you doing two things: 1) get the latest CVS version of AOLServer, do not use the one in ports, since it uses to be very outdated. 2) Compile AOLServer with debugging, since it indeed would help a lot. 3) If have some time, upgrade to FreeBSD 7.1, since I am sure that many bugs have been corrected. Anyways, I am not happy about AOLServer running in 64 bits. I have found many problems like memory leaks (process size grows and grows as time passes), which made me restart it each 2-3 days. My final solution was to set up "monit" to control it, and restart when needed. Please, do anything from the ones above, and let us know. Kind Regards, Juan José - Juan José del Río| (+34) 616 512 340|juanj...@simpleoption.com Simple Option S.L. Tel: (+34) 951 930 122 Fax: (+34) 951 930 122 http://www.simpleoption.es http://www.simpleoption.com On Mon, 2009-01-26 at 12:28 +, Bernhard van Woerden wrote: > I'm managing to get AOLserver 4.5 on FreeBSD 7.0 amd64 to crash every > few days. > I've upgraded from 4.0.10 on i386 which ran great for years. > > GDB gives > > #0 0x000800df3fec in thr_kill () from /lib/libc.so.7 > [New Thread 0x80380c290 (LWP 100737)] > [New Thread 0x804560120 (LWP 100728)] > [New Thread 0x80380c850 (LWP 100725)] > [New Thread 0x80380c570 (LWP 100423)] > [New Thread 0x8016150f0 (LWP 100789)] > [New Thread 0x801614f80 (LWP 100788)] > [New Thread 0x801614e10 (LWP 100787)] > [New Thread 0x801614ca0 (LWP 100735)] > [New Thread 0x801614b30 (LWP 100734)] > [New Thread 0x8016149c0 (LWP 100733)] > [New Thread 0x801614850 (LWP 100732)] > [New Thread 0x8016146e0 (LWP 100731)] > [New Thread 0x801614570 (LWP 100730)] > [New Thread 0x801614400 (LWP 100322)] > [New Thread 0x801614290 (LWP 100471)] > [New Thread 0x801614120 (LWP 100341)] > [New Thread 0x8010016e0 (LWP 100211)] > [New Thread 0x801001570 (LWP 100210)] > [New Thread 0x801001400 (LWP 100209)] > [New Thread 0x801001290 (LWP 100206)] > [New Thread 0x801001120 (LWP 100311)] > > > I've not bulit nsd with debugging symbols which I guess is the next > thing I should do. > > To folk more knowledgeable than me does this give any hints as to > whether its a FreeBSD threading thing or a problem with AOLserver ? > What should I do next to track down the problem ? > > Many thanks > Bernhard > > -- > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: > field of your email blank. > > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd crash
Thanks Juan, It was indeed built from the port. I'll try what you suggest and see if I can track down something repeatable. I'll also try monit or deamon tools to supervise meantime. Kind regards Bernhard 2009/1/26 Juan José del Río - Simple Option > Hello Bernhard, > > I recommend you doing two things: > > 1) get the latest CVS version of AOLServer, do not use the one in ports, > since it uses to be very outdated. > > 2) Compile AOLServer with debugging, since it indeed would help a lot. > > 3) If have some time, upgrade to FreeBSD 7.1, since I am sure that many > bugs have been corrected. > > > Anyways, I am not happy about AOLServer running in 64 bits. I have found > many problems like memory leaks (process size grows and grows as time > passes), which made me restart it each 2-3 days. > > My final solution was to set up "monit" to control it, and restart when > needed. > > Please, do anything from the ones above, and let us know. > > Kind Regards, > > Juan José > > - > Juan José del Río| > (+34) 616 512 340|juanj...@simpleoption.com > > > Simple Option S.L. > Tel: (+34) 951 930 122 > Fax: (+34) 951 930 122 > http://www.simpleoption.es > http://www.simpleoption.com > > > On Mon, 2009-01-26 at 12:28 +, Bernhard van Woerden wrote: > > I'm managing to get AOLserver 4.5 on FreeBSD 7.0 amd64 to crash every > > few days. > > I've upgraded from 4.0.10 on i386 which ran great for years. > > > > GDB gives > > > > #0 0x000800df3fec in thr_kill () from /lib/libc.so.7 > > [New Thread 0x80380c290 (LWP 100737)] > > [New Thread 0x804560120 (LWP 100728)] > > [New Thread 0x80380c850 (LWP 100725)] > > [New Thread 0x80380c570 (LWP 100423)] > > [New Thread 0x8016150f0 (LWP 100789)] > > [New Thread 0x801614f80 (LWP 100788)] > > [New Thread 0x801614e10 (LWP 100787)] > > [New Thread 0x801614ca0 (LWP 100735)] > > [New Thread 0x801614b30 (LWP 100734)] > > [New Thread 0x8016149c0 (LWP 100733)] > > [New Thread 0x801614850 (LWP 100732)] > > [New Thread 0x8016146e0 (LWP 100731)] > > [New Thread 0x801614570 (LWP 100730)] > > [New Thread 0x801614400 (LWP 100322)] > > [New Thread 0x801614290 (LWP 100471)] > > [New Thread 0x801614120 (LWP 100341)] > > [New Thread 0x8010016e0 (LWP 100211)] > > [New Thread 0x801001570 (LWP 100210)] > > [New Thread 0x801001400 (LWP 100209)] > > [New Thread 0x801001290 (LWP 100206)] > > [New Thread 0x801001120 (LWP 100311)] > > > > > > I've not bulit nsd with debugging symbols which I guess is the next > > thing I should do. > > > > To folk more knowledgeable than me does this give any hints as to > > whether its a FreeBSD threading thing or a problem with AOLserver ? > > What should I do next to track down the problem ? > > > > Many thanks > > Bernhard > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > > > > > To Remove yourself from this list, simply send an email to < > lists...@listserv.aol.com> with the > > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > > > > > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to < > lists...@listserv.aol.com> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Re: [AOLSERVER] nsd crash
You might try adding -nostartfiles to the makefile. Specifically, after doing a correct configure, edit your include/ns.mak file: CFLAGS_EXTRA= -fPIC -pipe -nostartfiles It might work, or not. I keep needing to add this on newer linux kernels. You also need to build tcl so that threads are enabled (in tcl/unix): #!/bin/bash ./configure --prefix=/web/tnt \ --enable-threads \ --enable-shared \ --enable-debug (maybe add --enable-symbols) Note that tcl building has changed recently, the configure script used to be up one level (main tcl source directory). If you use an older tcl, you would have to use ../configure instead of ./configure. Example script for building AOLserver: #!/bin/bash export TCLSH=/web/tnt/bin/tclsh8.4 ./configure --prefix=/web/tnt \ --with-tcl=/web/tnt/lib \ --enable-threads \ --enable-shared \ --enable-debug Reference the tclsh built above. tom jackson On Mon, 2009-01-26 at 14:16 +, Bernhard van Woerden wrote: > Thanks Juan, > It was indeed built from the port. I'll try what you suggest and see > if I can track down something repeatable. > I'll also try monit or deamon tools to supervise meantime. > > Kind regards > Bernhard > 2009/1/26 Juan José del Río - Simple Option > > Hello Bernhard, > > I recommend you doing two things: > > 1) get the latest CVS version of AOLServer, do not use the one > in ports, > since it uses to be very outdated. > > 2) Compile AOLServer with debugging, since it indeed would > help a lot. > > 3) If have some time, upgrade to FreeBSD 7.1, since I am sure > that many > bugs have been corrected. > > > Anyways, I am not happy about AOLServer running in 64 bits. I > have found > many problems like memory leaks (process size grows and grows > as time > passes), which made me restart it each 2-3 days. > > My final solution was to set up "monit" to control it, and > restart when > needed. > > Please, do anything from the ones above, and let us know. > > Kind Regards, > > Juan José > > - > Juan José del Río| > (+34) 616 512 340|juanj...@simpleoption.com > > > Simple Option S.L. > Tel: (+34) 951 930 122 > Fax: (+34) 951 930 122 > http://www.simpleoption.es > http://www.simpleoption.com > > > > On Mon, 2009-01-26 at 12:28 +, Bernhard van Woerden wrote: > > I'm managing to get AOLserver 4.5 on FreeBSD 7.0 amd64 to > crash every > > few days. > > I've upgraded from 4.0.10 on i386 which ran great for years. > > > > GDB gives > > > > #0 0x000800df3fec in thr_kill () from /lib/libc.so.7 > > [New Thread 0x80380c290 (LWP 100737)] > > [New Thread 0x804560120 (LWP 100728)] > > [New Thread 0x80380c850 (LWP 100725)] > > [New Thread 0x80380c570 (LWP 100423)] > > [New Thread 0x8016150f0 (LWP 100789)] > > [New Thread 0x801614f80 (LWP 100788)] > > [New Thread 0x801614e10 (LWP 100787)] > > [New Thread 0x801614ca0 (LWP 100735)] > > [New Thread 0x801614b30 (LWP 100734)] > > [New Thread 0x8016149c0 (LWP 100733)] > > [New Thread 0x801614850 (LWP 100732)] > > [New Thread 0x8016146e0 (LWP 100731)] > > [New Thread 0x801614570 (LWP 100730)] > > [New Thread 0x801614400 (LWP 100322)] > > [New Thread 0x801614290 (LWP 100471)] > > [New Thread 0x801614120 (LWP 100341)] > > [New Thread 0x8010016e0 (LWP 100211)] > > [New Thread 0x801001570 (LWP 100210)] > > [New Thread 0x801001400 (LWP 100209)] > > [New Thread 0x801001290 (LWP 100206)] > > [New Thread 0x801001120 (LWP 100311)] > > > > > > I've not bulit nsd with debugging symbols which I guess is > the next > > thing I should do. > > > > To folk more knowledgeable than me does this give any hints > as to > > whether its a FreeBSD threading thing or a problem with > AOLserver ? > > What should I do next to track down the problem ? > > > > Many thanks > > Bernhard > > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > > > > > To Remove yourself from this list, simply send an email to > with the > > body of "SIGNOFF AOLSERVER" in the email message. You can > leave the Subject: field of your email blank. > > > > > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an emai
