2009/09/22 10:50 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 11:03  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.904 second response time
2009/09/22 15:43 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
web2 features page is is not loading and is taking too long to respond
hi Amette
dev.tw.o page is not loading
2009/09/22 17:36  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.370 second response time
amette: : ping
2009/09/22 18:02 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 18:20  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.979 second response time
2009/09/22 18:30 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 19:08  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.834 second response time
2009/09/22 19:13 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 19:26  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.401 second response time
2009/09/22 19:57 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 20:30  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.050 second response time
2009/09/22 20:46 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 20:54  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.503 second response time
amette
http critical on dev.tikiwiki.org. the site does not load
2009/09/22 21:30 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/22 22:03  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.307 second response time
jasprit: pong
what did you do alreadyto fix it?
restarted the apache
and then?
checked the database?
it cleared and its been up and down
sounds like database to me
ooh ok]
you know how to handle it?
is it to kill the process ID that appeared on top??
\ mysqladmin processlist
ok
2009/09/22 22:50 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
are you on it?
have done it
but i dont know why its not clearing
there's still a query hanging since 28484 seconds
thats the one that i worked on
kill it again
ok
I killed it - died nicely - even closing tables first
which command did you use for killing?
and please shut down the apache on web1 - otherwise it will immediately die under the load
 mysql -e
mysql -e "kill 2846594;"
yes
maybe it was two different processes
oh ok
and dev died already under the load, hm?
yes
I still have a session open - shutting down apache
load 82
you need to be more aware of the hanging mysql processes - that's our biggest enemy
2846594 is a long time...
ok
err, bullshit - that was the process id :P
;)
2009/09/22 23:13  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.865 second response time
I started writing a nagios check for the hanging query today - that will help identify the problem
that'll be good
:)
I wonder why nagios doesn't go green...
it is green from our side
ya still some criticals on web1
n Disk warning on web2
2009/09/22 23:39 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/23 00:26  OK  web1 HTTP HTTP OK - HTTP/1.1 302 Found - 0.133 second response time
2009/09/23 00:26  OK  web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.778 second response time
me idiot - yesterday I tried to fix apache by making it bind to the external IP only and didn't roll back the change
the check goes to the internal ip
room for improvement... ;)
:L
:)
2009/09/23 00:43  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.881 second response time
2009/09/23 01:07 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
2009/09/23 01:20  OK  web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.292 second response time