[00:01:04] PROBLEM - Puppet freshness on ocg3 is CRITICAL: Puppet has not run in the last 10 hours [00:01:05] PROBLEM - Puppet freshness on virt1004 is CRITICAL: Puppet has not run in the last 10 hours [00:06:17] New review: Nemo bis; "Duplicate https://gerrit.wikimedia.org/r/39312" [operations/mediawiki-config] (master) C: -1; - https://gerrit.wikimedia.org/r/40074 [00:17:05] New patchset: Nemo bis; "(bug 43240) Add localised logos for Wiktionaries without one" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/39312 [00:22:22] PROBLEM - MySQL Slave Delay on db26 is CRITICAL: CRIT replication delay 199 seconds [00:22:58] PROBLEM - MySQL Replication Heartbeat on db1007 is CRITICAL: CRIT replication delay 203 seconds [00:23:25] PROBLEM - MySQL Replication Heartbeat on db26 is CRITICAL: CRIT replication delay 240 seconds [00:23:34] PROBLEM - MySQL Slave Delay on db1007 is CRITICAL: CRIT replication delay 222 seconds [00:24:28] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [00:25:31] RECOVERY - MySQL Slave Delay on db1007 is OK: OK replication delay 0 seconds [00:26:25] RECOVERY - MySQL Replication Heartbeat on db1007 is OK: OK replication delay 0 seconds [00:26:52] RECOVERY - MySQL Replication Heartbeat on db26 is OK: OK replication delay 0 seconds [00:27:28] RECOVERY - MySQL Slave Delay on db26 is OK: OK replication delay 0 seconds [00:35:25] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 3.688 seconds [00:57:10] PROBLEM - Puppet freshness on spence is CRITICAL: Puppet has not run in the last 10 hours [01:10:31] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [01:22:13] PROBLEM - Puppet freshness on db1047 is CRITICAL: Puppet has not run in the last 10 hours [01:22:14] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Puppet has not run in the last 10 hours [01:22:14] PROBLEM - Puppet freshness on ms-fe1004 is CRITICAL: Puppet has not run in the last 10 hours [01:22:14] PROBLEM - Puppet freshness on ms-fe1003 is CRITICAL: Puppet has not run in the last 10 hours [01:22:14] PROBLEM - Puppet freshness on sq48 is CRITICAL: Puppet has not run in the last 10 hours [01:22:14] PROBLEM - Puppet freshness on zinc is CRITICAL: Puppet has not run in the last 10 hours [01:23:16] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.045 seconds [01:50:16] RECOVERY - Puppet freshness on spence is OK: puppet ran at Sun Dec 23 01:49:54 UTC 2012 [01:56:35] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [02:10:58] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.039 seconds [02:28:46] Change abandoned: Dereckson; "Included in I41b50fb9" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/40074 [02:29:31] !log LocalisationUpdate completed (1.21wmf6) at Sun Dec 23 02:29:31 UTC 2012 [02:29:42] Logged the message, Master [04:24:29] PROBLEM - Puppet freshness on search1001 is CRITICAL: Puppet has not run in the last 10 hours [04:27:29] PROBLEM - Puppet freshness on analytics1001 is CRITICAL: Puppet has not run in the last 10 hours [04:35:26] PROBLEM - Puppet freshness on ssl3001 is CRITICAL: Puppet has not run in the last 10 hours [05:12:49] PROBLEM - Puppet freshness on ms1002 is CRITICAL: Puppet has not run in the last 10 hours [06:25:34] RECOVERY - Varnish HTCP daemon on cp1042 is OK: PROCS OK: 1 process with UID = 997 (varnishhtcpd), args varnishhtcpd worker [06:26:10] RECOVERY - Varnish HTTP mobile-backend on cp1042 is OK: HTTP OK HTTP/1.1 200 OK - 696 bytes in 0.053 seconds [06:26:46] RECOVERY - Varnish traffic logger on cp1042 is OK: PROCS OK: 3 processes with command name varnishncsa [06:31:07] PROBLEM - Varnish HTCP daemon on cp1042 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [06:31:34] PROBLEM - Varnish HTTP mobile-backend on cp1042 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [06:32:10] PROBLEM - Varnish traffic logger on cp1042 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [08:33:45] PROBLEM - Puppet freshness on ms1004 is CRITICAL: Puppet has not run in the last 10 hours [08:38:51] PROBLEM - Puppet freshness on db10 is CRITICAL: Puppet has not run in the last 10 hours [08:42:45] PROBLEM - Puppet freshness on ms-be1005 is CRITICAL: Puppet has not run in the last 10 hours [08:42:45] PROBLEM - Puppet freshness on analytics1007 is CRITICAL: Puppet has not run in the last 10 hours [08:42:46] PROBLEM - Puppet freshness on ms-be1007 is CRITICAL: Puppet has not run in the last 10 hours [08:42:46] PROBLEM - Puppet freshness on ms-be1006 is CRITICAL: Puppet has not run in the last 10 hours [10:02:45] PROBLEM - Puppet freshness on ocg3 is CRITICAL: Puppet has not run in the last 10 hours [10:02:45] PROBLEM - Puppet freshness on virt1004 is CRITICAL: Puppet has not run in the last 10 hours [10:41:36] PROBLEM - MySQL Replication Heartbeat on db1035 is CRITICAL: CRIT replication delay 191 seconds [10:42:12] PROBLEM - MySQL Slave Delay on db1035 is CRITICAL: CRIT replication delay 215 seconds [11:23:18] RECOVERY - MySQL Replication Heartbeat on db1035 is OK: OK replication delay 0 seconds [11:23:18] PROBLEM - Puppet freshness on db1047 is CRITICAL: Puppet has not run in the last 10 hours [11:23:19] PROBLEM - Puppet freshness on ms-fe1003 is CRITICAL: Puppet has not run in the last 10 hours [11:23:19] PROBLEM - Puppet freshness on ms-fe1004 is CRITICAL: Puppet has not run in the last 10 hours [11:23:19] PROBLEM - Puppet freshness on sq48 is CRITICAL: Puppet has not run in the last 10 hours [11:23:19] PROBLEM - Puppet freshness on zinc is CRITICAL: Puppet has not run in the last 10 hours [11:23:19] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Puppet has not run in the last 10 hours [11:23:46] RECOVERY - MySQL Slave Delay on db1035 is OK: OK replication delay 0 seconds [11:24:48] PROBLEM - MySQL Slave Delay on db1007 is CRITICAL: CRIT replication delay 191 seconds [11:25:24] PROBLEM - MySQL Replication Heartbeat on db26 is CRITICAL: CRIT replication delay 198 seconds [11:25:34] PROBLEM - MySQL Slave Delay on db26 is CRITICAL: CRIT replication delay 201 seconds [11:26:00] PROBLEM - MySQL Replication Heartbeat on db1007 is CRITICAL: CRIT replication delay 230 seconds [11:32:18] RECOVERY - MySQL Replication Heartbeat on db26 is OK: OK replication delay 0 seconds [11:32:27] RECOVERY - MySQL Slave Delay on db26 is OK: OK replication delay 0 seconds [11:34:42] RECOVERY - MySQL Replication Heartbeat on db1007 is OK: OK replication delay 0 seconds [11:35:09] RECOVERY - MySQL Slave Delay on db1007 is OK: OK replication delay 0 seconds [11:41:18] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [11:44:45] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.047 seconds [12:16:43] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [12:30:48] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 4.622 seconds [13:05:01] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [13:17:37] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.036 seconds [13:19:52] RECOVERY - Varnish traffic logger on cp1042 is OK: PROCS OK: 3 processes with command name varnishncsa [13:20:01] RECOVERY - Varnish HTTP mobile-backend on cp1042 is OK: HTTP OK HTTP/1.1 200 OK - 698 bytes in 0.054 seconds [13:20:10] RECOVERY - Varnish HTCP daemon on cp1042 is OK: PROCS OK: 1 process with UID = 997 (varnishhtcpd), args varnishhtcpd worker [13:49:51] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [14:00:30] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 9.492 seconds [14:03:03] PROBLEM - MySQL Slave Delay on db26 is CRITICAL: CRIT replication delay 192 seconds [14:03:12] PROBLEM - MySQL Replication Heartbeat on db26 is CRITICAL: CRIT replication delay 198 seconds [14:25:33] PROBLEM - Puppet freshness on search1001 is CRITICAL: Puppet has not run in the last 10 hours [14:28:33] PROBLEM - Puppet freshness on analytics1001 is CRITICAL: Puppet has not run in the last 10 hours [14:34:52] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [14:36:39] PROBLEM - Puppet freshness on ssl3001 is CRITICAL: Puppet has not run in the last 10 hours [14:39:12] PROBLEM - Varnish traffic logger on cp1042 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [14:39:57] PROBLEM - Varnish HTCP daemon on cp1042 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [14:39:57] PROBLEM - Varnish HTTP mobile-backend on cp1042 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [14:48:39] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 8.890 seconds [14:53:18] PROBLEM - Memcached on virt0 is CRITICAL: Connection refused [15:03:30] RECOVERY - MySQL Replication Heartbeat on db26 is OK: OK replication delay 0 seconds [15:03:39] RECOVERY - MySQL Slave Delay on db26 is OK: OK replication delay 0 seconds [15:08:47] New patchset: Dereckson; "(bug 43359) Enable WebFonts on Javanese projects" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/39578 [15:13:42] PROBLEM - Puppet freshness on ms1002 is CRITICAL: Puppet has not run in the last 10 hours [15:23:00] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [15:30:20] New review: Dereckson; "Please wait I0fbae921 is merged before submit this configuration change." [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/39578 [15:33:49] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 2.652 seconds [15:34:42] RECOVERY - Memcached on virt0 is OK: TCP OK - 0.002 second response time on port 11000 [15:59:36] PROBLEM - Puppet freshness on db48 is CRITICAL: Puppet has not run in the last 10 hours [15:59:36] PROBLEM - Puppet freshness on es3 is CRITICAL: Puppet has not run in the last 10 hours [15:59:37] PROBLEM - Puppet freshness on es9 is CRITICAL: Puppet has not run in the last 10 hours [15:59:37] PROBLEM - Puppet freshness on es8 is CRITICAL: Puppet has not run in the last 10 hours [15:59:37] PROBLEM - Puppet freshness on mw1115 is CRITICAL: Puppet has not run in the last 10 hours [15:59:37] PROBLEM - Puppet freshness on mw1149 is CRITICAL: Puppet has not run in the last 10 hours [15:59:37] PROBLEM - Puppet freshness on cp1001 is CRITICAL: Puppet has not run in the last 10 hours [15:59:38] PROBLEM - Puppet freshness on ms-be6 is CRITICAL: Puppet has not run in the last 10 hours [15:59:38] PROBLEM - Puppet freshness on mw1152 is CRITICAL: Puppet has not run in the last 10 hours [15:59:39] PROBLEM - Puppet freshness on srv222 is CRITICAL: Puppet has not run in the last 10 hours [15:59:39] PROBLEM - Puppet freshness on sq85 is CRITICAL: Puppet has not run in the last 10 hours [15:59:40] PROBLEM - Puppet freshness on srv228 is CRITICAL: Puppet has not run in the last 10 hours [16:00:39] PROBLEM - Puppet freshness on srv241 is CRITICAL: Puppet has not run in the last 10 hours [16:00:39] PROBLEM - Puppet freshness on mc2 is CRITICAL: Puppet has not run in the last 10 hours [16:00:39] PROBLEM - Puppet freshness on srv285 is CRITICAL: Puppet has not run in the last 10 hours [16:08:54] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [16:23:00] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 1.772 seconds [16:29:36] PROBLEM - Puppet freshness on celsus is CRITICAL: Puppet has not run in the last 10 hours [16:29:36] PROBLEM - Puppet freshness on cp1029 is CRITICAL: Puppet has not run in the last 10 hours [16:29:37] PROBLEM - Puppet freshness on snapshot1001 is CRITICAL: Puppet has not run in the last 10 hours [16:29:37] PROBLEM - Puppet freshness on mw1030 is CRITICAL: Puppet has not run in the last 10 hours [16:29:37] PROBLEM - Puppet freshness on tin is CRITICAL: Puppet has not run in the last 10 hours [16:29:37] PROBLEM - Puppet freshness on neon is CRITICAL: Puppet has not run in the last 10 hours [16:29:37] PROBLEM - Puppet freshness on srv210 is CRITICAL: Puppet has not run in the last 10 hours [16:30:39] PROBLEM - Puppet freshness on search1002 is CRITICAL: Puppet has not run in the last 10 hours [16:56:00] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [17:06:39] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 9.390 seconds [17:41:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [17:51:35] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 5.730 seconds [17:51:53] PROBLEM - MySQL Replication Heartbeat on db1035 is CRITICAL: CRIT replication delay 196 seconds [17:52:02] PROBLEM - MySQL Slave Delay on db1035 is CRITICAL: CRIT replication delay 202 seconds [18:05:41] RECOVERY - MySQL Replication Heartbeat on db1035 is OK: OK replication delay 0 seconds [18:05:50] RECOVERY - MySQL Slave Delay on db1035 is OK: OK replication delay 0 seconds [18:26:24] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [18:35:23] PROBLEM - Puppet freshness on ms1004 is CRITICAL: Puppet has not run in the last 10 hours [18:40:29] PROBLEM - Puppet freshness on db10 is CRITICAL: Puppet has not run in the last 10 hours [18:40:29] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.040 seconds [18:44:23] PROBLEM - Puppet freshness on analytics1007 is CRITICAL: Puppet has not run in the last 10 hours [18:44:23] PROBLEM - Puppet freshness on ms-be1005 is CRITICAL: Puppet has not run in the last 10 hours [18:44:24] PROBLEM - Puppet freshness on ms-be1007 is CRITICAL: Puppet has not run in the last 10 hours [18:44:24] PROBLEM - Puppet freshness on ms-be1006 is CRITICAL: Puppet has not run in the last 10 hours [18:47:14] RECOVERY - Varnish HTTP mobile-backend on cp1042 is OK: HTTP OK HTTP/1.1 200 OK - 698 bytes in 0.054 seconds [18:47:14] RECOVERY - Varnish HTCP daemon on cp1042 is OK: PROCS OK: 1 process with UID = 997 (varnishhtcpd), args varnishhtcpd worker [18:47:59] RECOVERY - Varnish traffic logger on cp1042 is OK: PROCS OK: 3 processes with command name varnishncsa [19:13:29] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:25:38] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 3.521 seconds [19:32:24] PROBLEM - Puppet freshness on ms-fe3001 is CRITICAL: Puppet has not run in the last 10 hours [19:46:20] PROBLEM - Varnish HTTP mobile-backend on cp1042 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [19:46:47] PROBLEM - Varnish HTCP daemon on cp1042 is CRITICAL: CHECK_NRPE: Socket timeout after 10 seconds. [19:49:47] RECOVERY - Varnish HTTP mobile-backend on cp1042 is OK: HTTP OK HTTP/1.1 200 OK - 698 bytes in 0.053 seconds [19:50:23] RECOVERY - Varnish HTCP daemon on cp1042 is OK: PROCS OK: 1 process with UID = 997 (varnishhtcpd), args varnishhtcpd worker [20:00:26] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [20:04:29] PROBLEM - Puppet freshness on ocg3 is CRITICAL: Puppet has not run in the last 10 hours [20:04:30] PROBLEM - Puppet freshness on virt1004 is CRITICAL: Puppet has not run in the last 10 hours [20:12:26] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 0.030 seconds [20:17:22] apergos, you about? [20:18:03] not really, food then sleep [20:18:27] ah this one's quick, please can you add Philippe to RT #4164? [20:20:37] ok he is a cc, is that what you wanted? [20:20:55] yes, if that will let him view it? [20:21:39] uh [20:21:53] no idea but he should get all futur messages [20:22:06] ok thanks [20:22:29] sure, good night [20:46:11] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [20:56:32] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 2.923 seconds [21:18:35] MaxSem: can you get the backtrace for https://bugzilla.wikimedia.org/show_bug.cgi?id=43374 fatal? [21:25:00] PROBLEM - Puppet freshness on db1047 is CRITICAL: Puppet has not run in the last 10 hours [21:25:00] PROBLEM - Puppet freshness on ms-be1010 is CRITICAL: Puppet has not run in the last 10 hours [21:25:00] PROBLEM - Puppet freshness on ms-fe1003 is CRITICAL: Puppet has not run in the last 10 hours [21:25:00] PROBLEM - Puppet freshness on sq48 is CRITICAL: Puppet has not run in the last 10 hours [21:25:00] PROBLEM - Puppet freshness on zinc is CRITICAL: Puppet has not run in the last 10 hours [21:25:00] PROBLEM - Puppet freshness on ms-fe1004 is CRITICAL: Puppet has not run in the last 10 hours [21:26:55] Nemo_bis, done [21:28:49] thanks [21:31:18] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [21:43:45] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 7.169 seconds [21:55:54] PROBLEM - Host srv278 is DOWN: PING CRITICAL - Packet loss = 100% [21:58:54] RECOVERY - Host srv278 is UP: PING OK - Packet loss = 0%, RTA = 0.39 ms [22:02:10] Change merged: Reedy; [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/39312 [22:02:58] PROBLEM - Apache HTTP on srv278 is CRITICAL: Connection refused [22:04:10] !log reedy synchronized wmf-config/InitialiseSettings.php [22:04:24] Logged the message, Master [22:06:33] whoops, URLs are wrong :o [22:17:39] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [22:17:46] New patchset: Nemo bis; "(bug 43240) Add localised logos for Wiktionaries without one" [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/40282 [22:18:01] Reedy: sorry, I broke the logos on those wiki, can you merge the fix above? [22:18:53] why does one always forget to check the obvious important things :/ [22:19:35] New review: Nemo bis; "Follow-up fix at https://gerrit.wikimedia.org/r/#/c/40282/ ..." [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/39312 [22:30:06] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 3.800 seconds [22:31:03] Change merged: Reedy; [operations/mediawiki-config] (master) - https://gerrit.wikimedia.org/r/40282 [22:31:28] !log reedy synchronized wmf-config/InitialiseSettings.php [22:31:37] Logged the message, Master [22:31:40] thanks and sorry again... [22:32:05] hah Nemo_bis ;) [22:32:33] * jeremyb goes to procure some provisions [22:32:45] ou [22:44:25] jeremyb: No need to bother [22:44:29] The world didn't end [22:44:54] 0) citation needed [22:45:00] 1) i still need to eat [23:02:28] RECOVERY - Apache HTTP on srv278 is OK: HTTP OK - HTTP/1.1 301 Moved Permanently - 1.784 second response time [23:05:10] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:15:31] RECOVERY - Puppetmaster HTTPS on stafford is OK: HTTP OK HTTP/1.1 400 Bad Request - 336 bytes in 3.536 seconds [23:24:38] !log reedy synchronized php-1.21wmf6/includes/filebackend/FSFileBackend.php [23:24:46] Logged the message, Master [23:50:46] PROBLEM - Puppetmaster HTTPS on stafford is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:56:28] PROBLEM - Apache HTTP on srv224 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [23:58:07] RECOVERY - Apache HTTP on srv224 is OK: HTTP OK - HTTP/1.1 301 Moved Permanently - 1.917 second response time