On Tue, 22 Jun 2010 21:39:33 +0200, Örjan Persson <ora...@fobie.net> wrote: > o2o bug reporter (bugrepor...@one-2-one.pl) wrote: >> The problem is that after quite random time of operation (at least 30 >> minutes, usually few hours)- while daemon is not under heavy load (I >> would even >> say while it is almost not used) - it crashes, leaving it's PID file. >> Without using 'gdb' it was impossible for me to get any clue why it >> bahaves so. >> Daemon process has just been dissappearing at a time. > > Hello,
Hi! > > That sounds indeed like a bug, but I'm unable to reproduce this problem. > > I started a server like this: > > $ ttserver -port 1999 -ext expire.lua -extpc expire 1.0 -ld > test.tct#idx=key:lex#idx=x:dec#idx=val:lex#dfunit=8 > > And then I inserted some keys: > > $ for i in `seq 1 60`; do tcrmgr put -port 1999 -sep '|' localhost "$i" > "x|$((`date +%s`+i))"; done > > And to verify the keys, I did this: > > $ tcrmgr list -pv -port 1999 -sep '|' localhost > > I also tried sending HUP to it: > > $ kill -HUP `pgrep -f 'ttserver -port 1999'` > > Can you always reproduce this when SIGHUP is sent to the process? Or is > it completely random? Seems that problem is appearing in client session and it is not connected to performing SIGHUP. In log I've previously send, the SIGHUP command was issued quite long before daemon crashed. In my log I can see: 2010-06-20T17:16:59+01:00 INFO connected: 10.0.3.101:46776 2010-06-20T17:16:59+01:00 DEBUG doing stat command 2010-06-20T17:16:59+01:00 DEBUG doing misc command 2010-06-20T17:16:59+01:00 DEBUG doing out command 2010-06-20T17:16:59+01:00 INFO connection finished 2010-06-20T17:17:10+01:00 INFO connected: 10.0.3.101:46871 2010-06-20T17:17:10+01:00 DEBUG doing stat command 2010-06-20T17:17:10+01:00 DEBUG doing misc command 2010-06-20T17:17:10+01:00 DEBUG doing out command 2010-06-20T17:17:10+01:00 DEBUG doing misc command Currently I also started session as you described and it is working fine for about 5 minutes now. Than I'll try to search application that normally runs there, what is exactly the 'misc' command performed. Seems that this 'misc' command is problem here. The application code has been previously used on another installation of TT - in some other server environment and it used to work fine there. Regards; AdamLis; > > Regards, > Örjan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
