2009/10/12 07:27 OK web1 Disk OK : /: 80%used(5725MB/7158MB) : < 80 % 2009/10/12 08:02 WARN web1 Disk WARNING : /: 80%used(5728MB/7158MB) : > 80 % 2009/10/12 08:15 OK web1 Disk OK : /: 80%used(5721MB/7158MB) : < 80 % 2009/10/12 16:42 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds 2009/10/12 17:05 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.672 second response time 2009/10/12 17:23 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds 2009/10/12 17:41 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 8.922 second response time amette: are you working on that server ? 2009/10/12 17:46 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds changi|work: nope doc flaps often, especially features page, the trackers eat performance as hell ok 2009/10/12 18:09 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.302 second response time 2009/10/12 18:59 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds 2009/10/12 19:07 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 7.177 second response time 2009/10/12 19:17 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds 2009/10/12 19:25 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.165 second response time 2009/10/12 19:36 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds amette ? what are the proc cpu of then xen server ? have we access to this one too ? i think we do if you think, that's pretty cool :) i m not sure sorry :) Amette bist du da ? as someone admin right on sysadm.two ? s/as/has/ 2009/10/12 21:10 CRIT web1 TikiWiki CRITICAL - Socket timeout after 10 seconds 2009/10/12 21:13 CRIT web1 HTTP CRITICAL - Socket timeout after 10 seconds lot of segfault 2009/10/12 21:18 OK web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.474 second response time 2009/10/12 21:21 OK web1 HTTP HTTP OK - HTTP/1.1 302 Found - 0.092 second response time 2009/10/12 21:26 CRIT web1 HTTP CRITICAL - Socket timeout after 10 seconds 2009/10/12 21:28 CRIT web1 TikiWiki CRITICAL - Socket timeout after 10 seconds 2009/10/12 21:34 OK web1 HTTP HTTP OK - HTTP/1.1 302 Found - 0.113 second response time just restart apache on dev :) my first action :) changi|home: http://pastebin.com/m538bc710 and yeah, deepaks is right changi|home: yeah - thumbs up! :) buuut.... ... it's another problem... check here: http://sysadm.tikiwiki.org/tiki-index.php?page=Procedures&structure=InstallationHandbook 2009/10/12 21:36 OK web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.312 second response time amette: i just add a new page on sysadm.two with some question and proposition to discuss. 2009/10/12 21:41 CRIT web1 TikiWiki HTTP CRITICAL - No data received from host "Ceeeelebrate good times, come on!" - dubidubidu... :) should be good Finally the wiki becomes a collaborative space! :) cool, I'll read that later - thanks! :) just saw a very long mysql query yes, that's the one that's always hanging... check htop - one CPU is constantly under 100% - dev.tw.o will die in the next hour ah, nope, someone killed the query now what is the tiki version of dev ? 2009/10/12 21:49 OK web1 TikiWiki HTTP OK HTTP/1.1 200 OK - 0.269 second response time 2009/10/12 21:49 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 9.991 second response time it's proposed branch right after release changi|home: the MySQL backup fails since a couple of days with "Lost connection during"... you have an idea right from the top of your mind? are our tables getting too big? buffer-sizes or so? try /root/bin/MySQL-backup.sh nfs net is a bit slow i think maybe i put my own script that i use for backu maybe we can use it wait timeout is at 28800, that is a little bit short to make an alldatabase backup just have a look, i use this script with subversion to make a daily backup good night every one 2009/10/13 00:34 CRIT web2 Features Page CRITICAL - Socket timeout after 10 seconds 2009/10/13 01:02 OK web2 Features Page HTTP OK HTTP/1.1 200 OK - 6.776 second response time