why don't you guys go killing those hanging queries?
dev should be back soon
2009/11/12 03:09  OK  web1 HTTP HTTP OK - HTTP/1.1 302 Found - 0.047 second response time
2009/11/12 03:09  OK  web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.197 second response time
on wiki-translation.com?
@amette
on dev
it was now down for almost 3 hours since you noticed
.
http criticals  on wiki-translations, security.tikiwiki.org, info.tikwiki.org
info.tikiwiki.org is on critical
marclaporte: wiki-translation.com is on critical
security.tikiwiki.org is on critical
tks
2009/11/12 23:54 CRIT web1 TikiWiki CRITICAL - Socket timeout after 10 seconds
dev.tikiwiki.org is critical
then kill the process
2009/11/13 00:04 CRIT web1 HTTP CRITICAL - Socket timeout after 10 seconds
ok
process still there
deepak1: do you know, what you should do?
sorry, my fault - it's a new one
you see it?
ya tried the procedure given to use
it dosent work
sure it dos
thot i did sumthing wrong
does
look at the process table before and after killing - the procss will be gone
ok
check the process id - that's the relevant thing
do you see?
ya i killed the process and its not there
and its cleared
2009/11/13 00:32  OK  web1 HTTP HTTP OK - HTTP/1.1 302 Found - 0.030 second response time
2009/11/13 00:32  OK  web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.485 second response time
did you notice that the second time you killed - it was a different process
ya
good
thanks