I think that file does not do good validation on the config settings before it uses them. I'll fix that. In the mean time, set the timeout param in the config to a number or remove it all together.

M

On Mar 4, 2008, at 2:08 PM, Xavier Bourguignon wrote:

allright,

I have followed the directions on how to install aolserver from there:
http://alex-andr.org/notes/tiki-index.php?page=nsd+setup+script

I have run the script, and it seems that everything is ok now in terms
of make and make install.

Now I have another problem.

I start aolserver with this command:
./bin/nsd -ft base.tcl

I get the following output:
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nsmain:
AOLserver/4.5.0 starting
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nsmain:
security info: uid=1000, euid=1000, gid=1000, egid=1000
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nsmain: max
files: FD_SETSIZE = 1024, rl_cur = 1024, rl_max = 1024
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: encoding: loaded: utf-8
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice:
fastpath[server1]: mapped GET /
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice:
fastpath[server1]: mapped HEAD /
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice:
fastpath[server1]: mapped POST /
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: adp[server1]:
mapped GET /*.adp
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: adp[server1]:
mapped HEAD /*.adp
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: adp[server1]:
mapped POST /*.adp
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: modload:
loading '/home/xbourgui/aolserver/aolserver4.5/bin/nssock.so'
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: modload:
loading '/home/xbourgui/aolserver/aolserver4.5/bin/nslog.so'
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nslog: opened
'/home/xbourgui/aolserver/aolserver4.5/servers/server1/modules/nslog/ access.log'
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: modload:
loading '/home/xbourgui/aolserver/aolserver4.5/bin/nscp.so'
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nscp:
listening on 127.0.0.1:8001
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nscp: added user:
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: conf:
[ns/server/server1]enabletclpages = 0
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Error: tcl: source
/home/xbourgui/aolserver/aolserver4.5/modules/tcl/pools.tcl failed:
timeout cannot be less than 1
NONE
timeout cannot be less than 1
  while executing
"ns_pools set default -minthreads $minthreads -maxthreads $maxthreads
-maxconns $maxconns -timeout $timeout"
(file "/home/xbourgui/aolserver/aolserver4.5/modules/tcl/ pools.tcl" line 39)
  invoked from within
"source $file"
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nsmain:
AOLserver/4.5.0 running
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: nsmain:
security info: uid=1000, euid=1000, gid=1000, egid=1000
[04/Mar/2008:18:26:09][25063.3083937456][-main-] Notice: driver:
starting: nssock
[04/Mar/2008:18:26:09][25063.3075005328][-socks-] Notice: socks: starting [04/Mar/2008:18:26:09][25063.3075169168][-sched-] Notice: sched: starting [04/Mar/2008:18:26:09][25063.3074169744][-nssock:driver-] Notice: starting
[04/Mar/2008:18:26:09][25063.3074169744][-nssock:driver-] Notice:
nssock: listening on 127.0.1.1:8000

It seems that there is a problem with one of the tcl files. Anyway, I
go to http://localhost:8001, but nothing happens at all. As soon as I
Ctrl-C the aolserver I get this in my browser:
login: Password:
Just those words, no entry field of any kind.
I also get this in the shell when I ctrl-C the aolserv:

[04/Mar/2008:18:31:41][25063.3083937456][-main-] Notice: nsmain:
AOLserver/4.5.0 stopping
[04/Mar/2008:18:31:41][25063.3083937456][-main-] Notice: driver:
stopping: nssock
[04/Mar/2008:18:31:41][25063.3083937456][-main-] Notice: sched: shutdown pending
[04/Mar/2008:18:31:41][25063.3074866064][-default:0-] Notice: exiting:
shutdown pending
[04/Mar/2008:18:31:41][25063.3074726800][-default:1-] Notice: exiting:
shutdown pending
[04/Mar/2008:18:31:41][25063.3074169744][-nssock:driver-] Notice: exiting
[04/Mar/2008:18:31:41][25063.3075169168][-sched-] Notice: sched:
shutdown started
[04/Mar/2008:18:31:41][25063.3075169168][-sched-] Notice: sched:
shutdown complete
[04/Mar/2008:18:31:41][25063.3074587536][-default:2-] Notice: exiting:
shutdown pending
[04/Mar/2008:18:31:41][25063.3075005328][-socks-] Notice: socks:
shutdown pending
[04/Mar/2008:18:31:41][25063.3075005328][-socks-] Notice: nscp: shutdown
[04/Mar/2008:18:31:41][25063.3075005328][-socks-] Notice: socks:
shutdown complete
[04/Mar/2008:18:31:41][25063.3074448272][-default:3-] Notice: exiting:
shutdown pending
[04/Mar/2008:18:31:41][25063.3074309008][-default:4-] Notice: exiting:
shutdown pending
[04/Mar/2008:18:31:41][25063.3083937456][-main-] Notice: driver: stopped: nssock
[04/Mar/2008:18:31:41][25063.3074169744][-shutdown-] Notice: nslog:
closing '/home/xbourgui/aolserver/aolserver4.5/servers/server1/ modules/nslog/access.log'
[04/Mar/2008:18:31:41][25063.3083937456][-main-] Notice: nsmain:
AOLserver/4.5.0 exiting

So I have no idea what to do next, why is my browserś request not
processed by the server?
Also, why do I see the login: and Password: words on the browser only
once I killed the server?

Thank you

On 04/03/2008, Gustaf Neumann <[EMAIL PROTECTED]> wrote:
Xavier Bourguignon schrieb:

Hello Gustaf,

yes I compiled tcl8.4.18 myself with --enable-threads.

I will redo everything and see what happens, will keep you guys posted on this.



what do you get when doing a

nm /home/xbourgui/programs/tcl8.4//lib/libtcl8.4.so | fgrep Tcl_GetMemory

?
You should see something like
0a064e91 T Tcl_GetMemoryInfo

The problem occurs in your listing with nstrheadtest, which is just
a testing routine, not needed for using aolserver. If only this
linkage fails, it would be no problem. But, if Tcl_GetMemoryInfo()
is not defined in libtcl8.4, you will have as well problems with linking
nsd, which would be serious.


-gustaf neumann

Thank you

On 04/03/2008, Gustaf Neumann <[EMAIL PROTECTED]> wrote:

Dear Xavier,

There is a known problem with Tcl_GetMemoryInfo()  in
Tcl 8.5 (see e.g.
http://aspn.activestate.com/ASPN/Mail/Message/tcl-core/3610677
or
http://sourceforge.net/tracker/index.php?func=detail&aid=1868171&group_id=10894&atid=110894) .

however, since you are using tcl 8.5, this seems wierd. Did you
compile Tcl yourself? Did you compile with --enable-threads?

best regards
-gustaf neumann

Xavier Bourguignon schrieb:


I ran make clean, then make all and I got this on make all:



gcc -O2 -Wall -Wno-implicit-int -fno-strict-aliasing -fPIC -O2
-fno-strict-aliasing -pipe -nostartfiles
-I/home/xbourgui/Desktop/aolserver-4.5.0/include
-I/home/xbourgui/programs/tcl8.4//include  -DNO_CONST
-DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1
-DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1
-DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1
-DTCL_THREADS=1 -DPEEK_XCLOSEIM=1 -D_LARGEFILE64_SOURCE=1
-DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 - DHAVE_OPEN64=1
-DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DHAVE_GETCWD=1
-DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1
-DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1
-DHAVE_GETPWUID_R_5=1 -DHAVE_GETPWUID_R=1 -DHAVE_GETPWNAM_R_5=1
-DHAVE_GETPWNAM_R=1 -DHAVE_GETGRGID_R_5=1 -DHAVE_GETGRGID_R=1
-DHAVE_GETGRNAM_R_5=1 -DHAVE_GETGRNAM_R=1 - DHAVE_GETHOSTBYNAME_R_6=1
-DHAVE_GETHOSTBYNAME_R=1 -DHAVE_GETHOSTBYADDR_R_8=1
-DHAVE_GETHOSTBYADDR_R=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1
-DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1
-DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1
-DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DHAVE_SIGNED_CHAR=1
-DHAVE_LANGINFO=1 -DHAVE_SYS_IOCTL_H=1  -DPACKAGE_NAME=\"\"
-DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING= \"\"
-DPACKAGE_BUGREPORT=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_INTTYPES_H=1
-DHAVE_TIMEGM=1 -DHAVE_DRAND48=1 -DHAVE_RANDOM=1 -DHAVE_POLL=1
-DHAVE_GETADDRINFO=1 -DHAVE_GETNAMEINFO=1    -c -o nsthreadtest.o
nsthreadtest.c
nsthreadtest.c: In function 'DumperThread':
nsthreadtest.c:336: warning: implicit declaration of function
'Tcl_GetMemoryInfo'
nsthreadtest.c: At top level:
nsthreadtest.c:51: warning: 'RCSID' defined but not used
/home/xbourgui/programs/tcl8.4/bin/tclsh8.4
/home/xbourgui/Desktop/aolserver-4.5.0/util/nsremove.tcl nsthreadtest
gcc  -o nsthreadtest nsthreadtest.o \
-L. -lnsthread -L/home/xbourgui/programs/tcl8.4// lib -ltcl8.4 -ldl -lpthread -lieee -lm -lgcc_s -Wl,--export- dynamic
-Wl,-rpath,/home/xbourgui/programs/tcl8.4/lib -Wl,-rpath,/lib
nsthreadtest.o: In function `DumperThread':
nsthreadtest.c:(.text+0x2a8): undefined reference to `Tcl_GetMemoryInfo'
collect2: ld returned 1 exit status
make[1]: *** [nsthreadtest] Error 1
make[1]: Leaving directory `/home/xbourgui/Desktop/ aolserver-4.5.0/nsthread'
make: *** [build] Error 1


So I don't know what is going on, but it seems that something is wrong
with one of the files.





--
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 - 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.



--
Xavier Bourguignon


--
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 - 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.

Reply via email to