***: franck has quit IRC ()
timothyv has joined #tikiwiki-monitor
timothyv has left
timothyv1 has joined #tikiwiki-monitor
jasprit has quit IRC ("Leaving.")
marclaporte has joined #tikiwiki-monitor
nagios: 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
***: franck_ has joined #tikiwiki-monitor
ChanServ sets mode: +o franck_
epeli_e has joined #tikiwiki-monitor
timothyv1 has quit IRC ("Leaving.")
franck_ has quit IRC (Read error: 113 (No route to host))
franck_ has joined #tikiwiki-monitor
ChanServ sets mode: +o franck_
franck_ has quit IRC (Read error: 113 (No route to host))
nagios: 2009/09/22 15:43 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
epeli_e: web2 features page is is not loading and is taking too long to respond
***: rupeni has left
epeli_e: hi Amette
dev.tw.o page is not loading
nagios: 2009/09/22 17:36 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.370 second response time
marclaporte: amette: : ping
nagios: 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
***: Epeli has joined #tikiwiki-monitor
Epeli has left
Epel1 has joined #tikiwiki-monitor
Epel1 has quit IRC (Remote closed the connection)
epeli_1 has joined #tikiwiki-monitor
nagios: 2009/09/22 20:30 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.050 second response time
***: jasprit has joined #tikiwiki-monitor
epeli_e has quit IRC (Read error: 113 (No route to host))
nagios: 2009/09/22 20:46 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
***: franck has joined #tikiwiki-monitor
ChanServ sets mode: +o franck
nagios: 2009/09/22 20:54 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.503 second response time
***: epeli_1 has quit IRC (Remote closed the connection)
epeli_e has joined #tikiwiki-monitor
epeli_1 has joined #tikiwiki-monitor
franck_ has joined #tikiwiki-monitor
ChanServ sets mode: +o franck_
jasprit: amette
http critical on dev.tikiwiki.org. the site does not load
nagios: 2009/09/22 21:30 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
***: epeli_e has quit IRC (Read error: 113 (No route to host))
franck has quit IRC (Read error: 113 (No route to host))
franck_ is now known as franck
nagios: 2009/09/22 22:03 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.307 second response time
amette: jasprit: pong
what did you do alreadyto fix it?
epeli_1: restarted the apache
amette: and then?
checked the database?
epeli_1: it cleared and its been up and down
amette: sounds like database to me
epeli_1: ooh ok]
amette: you know how to handle it?
epeli_1: is it to kill the process ID that appeared on top??
amette: mysqladmin processlist
epeli_1: ok
nagios: 2009/09/22 22:50 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
amette: are you on it?
epeli_1: have done it
but i dont know why its not clearing
amette: there's still a query hanging since 28484 seconds
***: marclaporte has quit IRC ("Miranda IM! Smaller, Faster, Easier. http://miranda-im.org")
epeli_1: thats the one that i worked on
amette: kill it again
epeli_1: ok
amette: 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
epeli_1: mysql -e
amette: mysql -e "kill 2846594;"
epeli_1: yes
amette: maybe it was two different processes
epeli_1: oh ok
amette: and dev died already under the load, hm?
epeli_1: yes
amette: 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...
***: franck has quit IRC ()
epeli_1: ok
amette: err, bullshit - that was the process id :P
epeli_1: ;)
nagios: 2009/09/22 23:13 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.865 second response time
amette: I started writing a nagios check for the hanging query today - that will help identify the problem
epeli_1: that'll be good
:)
***: franck has joined #tikiwiki-monitor
ChanServ sets mode: +o franck
franck has quit IRC (Read error: 54 (Connection reset by peer))
franck has joined #tikiwiki-monitor
ChanServ sets mode: +o franck
amette: I wonder why nagios doesn't go green...
epeli_1: it is green from our side
jasprit: ya still some criticals on web1
n Disk warning on web2
nagios: 2009/09/22 23:39 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
***: jasprit has left
jasprit has joined #tikiwiki-monitor
jasprit has quit IRC (Remote closed the connection)
jasprit has joined #tikiwiki-monitor
nagios: 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
amette: 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... ;)
epeli_1: :L
jasprit: :)
nagios: 2009/09/23 00:43 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.881 second response time
***: jasprit has left
nagios: 2009/09/23 01:07 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds
***: jasprit has joined #tikiwiki-monitor
epeli_1 has left
epeli_e has joined #tikiwiki-monitor
nagios: 2009/09/23 01:20 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.292 second response time