[00:06:48] RECOVERY - cp37 Disk Space on cp37 is OK: DISK OK - free space: / 57873MiB (12% inode=99%); [00:24:31] !log [void@puppet181] Upgraded packages on mattermost1: liblzma5 and xz-utils [00:24:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:24:44] !log [void@puppet181] Upgraded packages on cp36: liblzma5 and xz-utils [00:24:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:24:56] !log [void@puppet181] Upgraded packages on changeprop201: liblzma5 and xz-utils [00:24:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:08] !log [void@puppet181] Upgraded packages on cloud20: liblzma5 and xz-utils [00:25:10] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:21] !log [void@puppet181] Upgraded packages on cloud17: liblzma5 and xz-utils [00:25:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:29] RECOVERY - cp36 APT on cp36 is OK: APT OK: 34 packages available for upgrade (0 critical updates). [00:25:33] !log [void@puppet181] Upgraded packages on db151: liblzma5 and xz-utils [00:25:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:39] RECOVERY - mattermost1 APT on mattermost1 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:25:45] !log [void@puppet181] Upgraded packages on matomo151: liblzma5 and xz-utils [00:25:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:25:56] !log [void@puppet181] Upgraded packages on cp38: liblzma5 and xz-utils [00:25:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:26:09] !log [void@puppet181] Upgraded packages on cloud19: liblzma5 and xz-utils [00:26:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:26:21] !log [void@puppet181] Upgraded packages on db161: liblzma5 and xz-utils [00:26:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:26:30] RECOVERY - db151 APT on db151 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:26:33] !log [void@puppet181] Upgraded packages on bots171: liblzma5 and xz-utils [00:26:35] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:26:40] RECOVERY - cloud20 APT on cloud20 is OK: APT OK: 76 packages available for upgrade (0 critical updates). [00:26:46] !log [void@puppet181] Upgraded packages on cloud16: liblzma5 and xz-utils [00:26:46] RECOVERY - changeprop201 APT on changeprop201 is OK: APT OK: 33 packages available for upgrade (0 critical updates). [00:26:48] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:26:52] RECOVERY - cloud17 APT on cloud17 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [00:26:54] RECOVERY - db161 APT on db161 is OK: APT OK: 31 packages available for upgrade (0 critical updates). [00:26:58] !log [void@puppet181] Upgraded packages on graylog161: liblzma5 and xz-utils [00:27:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:27:03] RECOVERY - cloud16 APT on cloud16 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [00:27:05] RECOVERY - bots171 APT on bots171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:27:09] !log [void@puppet181] Upgraded packages on db172: liblzma5 and xz-utils [00:27:10] RECOVERY - db172 APT on db172 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:27:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:27:16] RECOVERY - matomo151 APT on matomo151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:27:24] !log [void@puppet181] Upgraded packages on cloud15: liblzma5 and xz-utils [00:27:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:27:32] RECOVERY - graylog161 APT on graylog161 is OK: APT OK: 3 packages available for upgrade (0 critical updates). [00:27:36] !log [void@puppet181] Upgraded packages on cp37: liblzma5 and xz-utils [00:27:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:27:46] RECOVERY - cloud15 APT on cloud15 is OK: APT OK: 75 packages available for upgrade (0 critical updates). [00:27:48] !log [void@puppet181] Upgraded packages on db171: liblzma5 and xz-utils [00:27:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:28:02] !log [void@puppet181] Upgraded packages on cloud18: liblzma5 and xz-utils [00:28:04] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:28:06] RECOVERY - cloud19 APT on cloud19 is OK: APT OK: 76 packages available for upgrade (0 critical updates). [00:28:15] RECOVERY - db171 APT on db171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:28:17] !log [void@puppet181] Upgraded packages on kafka181: liblzma5, xz-utils, libjetty9-java, and libjetty9-extra-java [00:28:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:28:30] !log [void@puppet181] Upgraded packages on db181: liblzma5 and xz-utils [00:28:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:28:44] !log [void@puppet181] Upgraded packages on eventgate181: liblzma5 and xz-utils [00:28:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:28:56] !log [void@puppet181] Upgraded packages on db182: liblzma5 and xz-utils [00:28:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:29:10] !log [void@puppet181] Upgraded packages on ldap171: liblzma5 and xz-utils [00:29:11] RECOVERY - cloud18 APT on cloud18 is OK: APT OK: 74 packages available for upgrade (0 critical updates). [00:29:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:29:15] RECOVERY - db182 APT on db182 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:29:16] RECOVERY - db181 APT on db181 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:29:23] !log [void@puppet181] Upgraded packages on bast161: liblzma5 and xz-utils [00:29:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:29:29] RECOVERY - cp37 APT on cp37 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:29:29] RECOVERY - eventgate181 APT on eventgate181 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:29:36] !log [void@puppet181] Upgraded packages on bast181: liblzma5 and xz-utils [00:29:38] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:29:51] !log [void@puppet181] Upgraded packages on mem151: liblzma5 and xz-utils [00:29:53] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:01] RECOVERY - kafka181 APT on kafka181 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:30:03] !log [void@puppet181] Upgraded packages on mem161: liblzma5 and xz-utils [00:30:05] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:05] RECOVERY - ldap171 APT on ldap171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:30:15] !log [void@puppet181] Upgraded packages on mem201: liblzma5 and xz-utils [00:30:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:29] !log [void@puppet181] Upgraded packages on mon181: liblzma5 and xz-utils [00:30:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:34] RECOVERY - bast161 APT on bast161 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:30:41] RECOVERY - bast181 APT on bast181 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:30:45] !log [void@puppet181] Upgraded packages on mw152: liblzma-dev, liblzma5, and xz-utils [00:30:47] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:30:57] RECOVERY - mem201 APT on mem201 is OK: APT OK: 33 packages available for upgrade (0 critical updates). [00:31:01] !log [void@puppet181] Upgraded packages on mw153: liblzma-dev, liblzma5, and xz-utils [00:31:03] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:31:05] RECOVERY - mem161 APT on mem161 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:31:15] !log [void@puppet181] Upgraded packages on mw161: liblzma-dev, liblzma5, and xz-utils [00:31:17] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:31:21] RECOVERY - mon181 APT on mon181 is OK: APT OK: 7 packages available for upgrade (0 critical updates). [00:31:30] !log [void@puppet181] Upgraded packages on mw162: liblzma-dev, liblzma5, and xz-utils [00:31:32] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:31:44] !log [void@puppet181] Upgraded packages on mw163: liblzma-dev, liblzma5, and xz-utils [00:31:46] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:31:47] RECOVERY - mem151 APT on mem151 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:31:50] RECOVERY - mw161 APT on mw161 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:31:50] RECOVERY - mw162 APT on mw162 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:32:00] !log [void@puppet181] Upgraded packages on mw151: liblzma-dev, liblzma5, and xz-utils [00:32:02] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:32:14] !log [void@puppet181] Upgraded packages on mw192: liblzma-dev, liblzma5, and xz-utils [00:32:15] RECOVERY - mw152 APT on mw152 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:32:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:32:29] !log [void@puppet181] Upgraded packages on mw173: liblzma-dev, liblzma5, and xz-utils [00:32:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:32:33] RECOVERY - mw153 APT on mw153 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:32:35] RECOVERY - mw192 APT on mw192 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:32:43] !log [void@puppet181] Upgraded packages on mw171: liblzma-dev, liblzma5, and xz-utils [00:32:45] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:32:57] !log [void@puppet181] Upgraded packages on mw191: liblzma-dev, liblzma5, and xz-utils [00:32:57] RECOVERY - mw171 APT on mw171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:32:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:33:01] RECOVERY - mw173 APT on mw173 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:33:12] !log [void@puppet181] Upgraded packages on mw172: liblzma-dev, liblzma5, and xz-utils [00:33:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:33:26] !log [void@puppet181] Upgraded packages on mw193: liblzma-dev, liblzma5, and xz-utils [00:33:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:33:29] RECOVERY - mw163 APT on mw163 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:33:31] RECOVERY - mw151 APT on mw151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:33:37] RECOVERY - mw191 APT on mw191 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:33:41] !log [void@puppet181] Upgraded packages on mw201: liblzma-dev, liblzma5, and xz-utils [00:33:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:33:54] RECOVERY - mw201 APT on mw201 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:33:56] !log [void@puppet181] Upgraded packages on mw181: liblzma-dev, liblzma5, and xz-utils [00:33:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:34:10] !log [void@puppet181] Upgraded packages on mwtask161: liblzma-dev, liblzma5, and xz-utils [00:34:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:34:26] !log [void@puppet181] Upgraded packages on mw183: liblzma-dev, liblzma5, and xz-utils [00:34:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:34:35] RECOVERY - mw183 APT on mw183 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:34:38] RECOVERY - mw172 APT on mw172 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:34:42] !log [void@puppet181] Upgraded packages on mwtask151: liblzma-dev, liblzma5, and xz-utils [00:34:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:34:57] !log [void@puppet181] Upgraded packages on mw182: liblzma-dev, liblzma5, and xz-utils [00:34:59] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:35:10] RECOVERY - mw181 APT on mw181 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:35:12] !log [void@puppet181] Upgraded packages on mw202: liblzma-dev, liblzma5, and xz-utils [00:35:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:35:22] RECOVERY - mw193 APT on mw193 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:35:27] !log [void@puppet181] Upgraded packages on mwtask171: liblzma-dev, liblzma5, and xz-utils [00:35:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:35:39] RECOVERY - mw182 APT on mw182 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:35:42] !log [void@puppet181] Upgraded packages on mw203: liblzma-dev, liblzma5, and xz-utils [00:35:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:35:51] RECOVERY - mwtask161 APT on mwtask161 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:35:54] !log [void@puppet181] Upgraded packages on os161: liblzma5 and xz-utils [00:35:56] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:36:07] !log [void@puppet181] Upgraded packages on prometheus151: liblzma5 and xz-utils [00:36:07] RECOVERY - mwtask171 APT on mwtask171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:36:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:36:23] !log [void@puppet181] Upgraded packages on mwtask181: liblzma-dev, liblzma5, and xz-utils [00:36:25] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:36:33] RECOVERY - mwtask151 APT on mwtask151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:36:37] !log [void@puppet181] Upgraded packages on ns1: liblzma5 and xz-utils [00:36:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:36:44] PROBLEM - cp38 health.wikitide.net HTTPS on cp38 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 56 - OpenSSL SSL_read: OpenSSL/3.0.15: error:0A00045C:SSL routines::tlsv13 alert certificate required, errno 0 [00:36:49] !log [void@puppet181] Upgraded packages on phorge171: liblzma5 and xz-utils [00:36:51] RECOVERY - phorge171 APT on phorge171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:36:51] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:36:53] RECOVERY - mw202 APT on mw202 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:37:04] !log [void@puppet181] Upgraded packages on rdb151: liblzma5 and xz-utils [00:37:05] RECOVERY - mwtask181 APT on mwtask181 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:37:06] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:37:09] RECOVERY - rdb151 APT on rdb151 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:37:17] !log [void@puppet181] Upgraded packages on os162: liblzma5 and xz-utils [00:37:19] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:37:20] RECOVERY - mw203 APT on mw203 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:37:29] !log [void@puppet181] Upgraded packages on puppet181: liblzma5 and xz-utils [00:37:31] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:37:38] RECOVERY - os161 APT on os161 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:37:41] RECOVERY - ns1 APT on ns1 is OK: APT OK: 31 packages available for upgrade (0 critical updates). [00:37:41] !log [void@puppet181] Upgraded packages on reports171: liblzma5 and xz-utils [00:37:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:37:55] !log [void@puppet181] Upgraded packages on os151: liblzma5 and xz-utils [00:37:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:38:06] RECOVERY - prometheus151 APT on prometheus151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:38:12] !log [void@puppet181] Upgraded packages on ns2: liblzma5 and xz-utils [00:38:14] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:38:14] RECOVERY - ns2 APT on ns2 is OK: APT OK: 31 packages available for upgrade (0 critical updates). [00:38:17] RECOVERY - reports171 APT on reports171 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:38:26] !log [void@puppet181] Upgraded packages on test151: liblzma-dev, liblzma5, and xz-utils [00:38:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:38:29] RECOVERY - puppet181 APT on puppet181 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:38:42] !log [void@puppet181] Upgraded packages on swiftproxy171: liblzma5 and xz-utils [00:38:44] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:38:44] RECOVERY - swiftproxy171 APT on swiftproxy171 is OK: APT OK: 35 packages available for upgrade (0 critical updates). [00:38:48] RECOVERY - os162 APT on os162 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:38:56] !log [void@puppet181] Upgraded packages on swiftobject151: liblzma5 and xz-utils [00:38:58] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:39:05] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [00:39:06] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 18:24:13) [00:39:07] mwtask161: not running [00:39:08] mwtask171: not running [00:39:08] RECOVERY - test151 APT on test151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:39:09] mwtask181: not running [00:39:11] !log [void@puppet181] Upgraded packages on swiftac171: liblzma5 and xz-utils [00:39:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:39:25] !log [void@puppet181] Upgraded packages on swiftproxy161: liblzma5 and xz-utils [00:39:27] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:39:28] RECOVERY - os151 APT on os151 is OK: APT OK: 1 packages available for upgrade (0 critical updates). [00:39:28] RECOVERY - swiftproxy161 APT on swiftproxy161 is OK: APT OK: 34 packages available for upgrade (0 critical updates). [00:39:40] !log [void@puppet181] Upgraded packages on swiftobject161: liblzma5 and xz-utils [00:39:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:39:44] RECOVERY - swiftobject151 APT on swiftobject151 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:39:55] !log [void@puppet181] Upgraded packages on swiftobject171: liblzma5 and xz-utils [00:39:57] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:40:09] !log [void@puppet181] Upgraded packages on swiftobject191: liblzma5 and xz-utils [00:40:11] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:40:17] RECOVERY - swiftobject161 APT on swiftobject161 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:40:26] !log [void@puppet181] Upgraded packages on swiftobject181: liblzma5 and xz-utils [00:40:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:40:32] RECOVERY - swiftobject181 APT on swiftobject181 is OK: APT OK: 33 packages available for upgrade (0 critical updates). [00:40:41] !log [void@puppet181] Upgraded packages on swiftobject201: liblzma5 and xz-utils [00:40:43] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [00:41:10] RECOVERY - swiftac171 APT on swiftac171 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:41:32] RECOVERY - swiftobject171 APT on swiftobject171 is OK: APT OK: 32 packages available for upgrade (0 critical updates). [00:41:52] RECOVERY - swiftobject191 APT on swiftobject191 is OK: APT OK: 33 packages available for upgrade (0 critical updates). [00:42:20] RECOVERY - swiftobject201 APT on swiftobject201 is OK: APT OK: 33 packages available for upgrade (0 critical updates). [00:44:12] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 7.34, 6.44, 5.59 [00:46:12] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 6.03, 6.20, 5.61 [01:25:14] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 23.81, 19.87, 13.53 [01:29:06] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 19.87, 20.27, 15.14 [01:34:56] PROBLEM - mwtask181 Current Load on mwtask181 is CRITICAL: LOAD CRITICAL - total load average: 25.01, 22.50, 17.61 [01:36:52] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 22.16, 22.53, 18.22 [01:38:48] PROBLEM - mwtask181 Current Load on mwtask181 is CRITICAL: LOAD CRITICAL - total load average: 24.19, 23.08, 18.94 [01:39:07] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [01:39:08] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 19:24:16) [01:39:09] mwtask161: not running [01:39:10] mwtask171: not running [01:39:11] mwtask181: not running [01:42:40] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 17.00, 22.34, 19.72 [01:44:36] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 11.25, 18.34, 18.56 [01:50:12] PROBLEM - matomo151 Current Load on matomo151 is WARNING: LOAD WARNING - total load average: 7.05, 6.36, 5.79 [01:52:12] RECOVERY - matomo151 Current Load on matomo151 is OK: LOAD OK - total load average: 5.82, 6.22, 5.81 [02:06:40] [02ssl] 07MacFan4000 pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/428adb94e2c50f2818e5bcc98de3ab1244dcdb54 [02:06:40] 02ssl/03master 07MacFan4000 03428adb9 add northgard.wiki [02:09:45] [02ssl] 07WikiTideSSLBot pushed 1 new commit to 03master 13https://github.com/miraheze/ssl/commit/7cef0c9a0717f343f8b4ee571522c84bb2a58376 [02:09:45] 02ssl/03master 07WikiTideSSLBot 037cef0c9 Bot: Update SSL cert for volunteerforukraine.com [02:10:20] PROBLEM - mwtask181 Current Load on mwtask181 is CRITICAL: LOAD CRITICAL - total load average: 25.75, 18.50, 14.24 [02:12:20] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 13.75, 16.66, 14.12 [02:17:50] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 20.79, 20.90, 16.75 [02:19:46] PROBLEM - mwtask181 Current Load on mwtask181 is CRITICAL: LOAD CRITICAL - total load average: 25.86, 22.78, 17.92 [02:23:37] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 20.42, 21.23, 18.42 [02:31:19] PROBLEM - mwtask181 Current Load on mwtask181 is CRITICAL: LOAD CRITICAL - total load average: 25.93, 23.04, 20.21 [02:37:05] PROBLEM - mwtask181 Current Load on mwtask181 is WARNING: LOAD WARNING - total load average: 18.65, 22.52, 21.09 [02:39:09] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [02:39:10] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 20:24:18) [02:39:11] mwtask161: not running [02:39:12] mwtask171: not running [02:39:13] mwtask181: not running [02:40:56] RECOVERY - mwtask181 Current Load on mwtask181 is OK: LOAD OK - total load average: 8.97, 16.62, 19.08 [03:01:14] RECOVERY - db172 Backups SQL on db172 is OK: FILE_AGE OK: /var/log/db-backups/db-backups/db-backups.log is 69 seconds old and 2131 bytes [03:39:12] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [03:39:13] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 21:24:20) [03:39:14] mwtask161: not running [03:39:15] mwtask171: not running [03:39:16] mwtask181: not running [04:39:14] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [04:39:15] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 22:24:23) [04:39:16] mwtask161: not running [04:39:17] mwtask171: not running [04:39:18] mwtask181: not running [05:20:19] RECOVERY - cp38 health.wikitide.net HTTPS on cp38 is OK: HTTP OK: HTTP/1.1 200 OK - 268 bytes in 0.010 second response time [05:39:17] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [05:39:18] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 23:24:25) [05:39:19] mwtask161: not running [05:39:20] mwtask171: not running [05:39:21] mwtask181: not running [05:46:35] [02mw-config] 07Universal-Omega requested changes on pull request #5890 13https://github.com/miraheze/mw-config/pull/5890#pullrequestreview-2745044284 [05:46:35] [02mw-config] 07Universal-Omega left a file comment in pull request #5890 0307b9a99: type hints (including return value of void) please 13https://github.com/miraheze/mw-config/pull/5890#discussion_r2030045394 [05:46:35] [02mw-config] 07Universal-Omega left a file comment in pull request #5890 0307b9a99: Comment can be removed if type hinting is done as mentioned above. 13https://github.com/miraheze/mw-config/pull/5890#discussion_r2030045579 [05:48:50] [02mw-config] 07Universal-Omega left a file comment in pull request #5890 0307b9a99: Also add $extraData param even if it's unused just to resemble the actual hook interface. 13https://github.com/miraheze/mw-config/pull/5890#discussion_r2030045956 [05:52:19] [02mw-config] 07Aeywoo opened pull request #5899: Configuration change per T13482 (07miraheze:03master...07Aeywoo:03patch-7) 13https://github.com/miraheze/mw-config/pull/5899 [05:53:06] miraheze/mw-config - Aeywoo the build passed. [05:54:18] [02mw-config] 07BlankEclair merged 07Aeywoo's pull request #5899: Configuration change per T13482 (07miraheze:03master...07Aeywoo:03patch-7) 13https://github.com/miraheze/mw-config/pull/5899 [05:54:18] [02mw-config] 07BlankEclair pushed 1 new commit to 03master 13https://github.com/miraheze/mw-config/commit/1c5ec0f2521c48b74054722f68fd7e7d48154f68 [05:54:18] 02mw-config/03master 07Aeywoo 031c5ec0f Configuration change per T13482 (#5899)… [05:55:10] miraheze/mw-config - BlankEclair the build passed. [06:11:06] !log [blankeclair@mwtask181] starting deploy of {'pull': 'config', 'config': True} to all [06:11:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [06:11:28] !log [blankeclair@mwtask181] finished deploy of {'pull': 'config', 'config': True} to all - SUCCESS in 22s [06:11:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [06:16:16] PROBLEM - cp38 Haproxy TLS backend for mw181 on cp38 is CRITICAL: connect to address localhost and port 8119: Connection refused [06:16:19] PROBLEM - cp38 health.wikitide.net HTTPS on cp38 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 7 - Failed to connect to health.wikitide.net port 443 after 0 ms: Couldn't connect to server [06:16:19] PROBLEM - cp38 Haproxy TLS backend for swiftproxy161 on cp38 is CRITICAL: connect to address localhost and port 8206: Connection refused [06:16:24] PROBLEM - cp38 Haproxy TLS backend for reports171 on cp38 is CRITICAL: connect to address localhost and port 8205: Connection refused [06:16:24] PROBLEM - cp38 Haproxy TLS backend for mw183 on cp38 is CRITICAL: connect to address localhost and port 8127: Connection refused [06:16:29] PROBLEM - cp38 Haproxy TLS backend for puppet181 on cp38 is CRITICAL: connect to address localhost and port 8204: Connection refused [06:16:36] PROBLEM - cp38 Haproxy TLS backend for mw172 on cp38 is CRITICAL: connect to address localhost and port 8118: Connection refused [06:16:50] PROBLEM - cp38 Haproxy TLS backend for mon181 on cp38 is CRITICAL: connect to address localhost and port 8201: Connection refused [06:16:50] PROBLEM - cp38 Haproxy TLS backend for mw171 on cp38 is CRITICAL: connect to address localhost and port 8117: Connection refused [06:16:50] PROBLEM - cp38 Haproxy TLS backend for mw192 on cp38 is CRITICAL: connect to address localhost and port 8130: Connection refused [06:16:52] PROBLEM - cp38 Haproxy TLS backend for mw203 on cp38 is CRITICAL: connect to address localhost and port 8134: Connection refused [06:16:53] PROBLEM - cp38 Haproxy TLS backend for mw201 on cp38 is CRITICAL: connect to address localhost and port 8132: Connection refused [06:16:54] PROBLEM - cp38 Haproxy TLS backend for test151 on cp38 is CRITICAL: connect to address localhost and port 8181: Connection refused [06:16:55] PROBLEM - cp38 Haproxy TLS backend for mwtask171 on cp38 is CRITICAL: connect to address localhost and port 8161: Connection refused [06:16:58] PROBLEM - cp38 Haproxy TLS backend for mwtask151 on cp38 is CRITICAL: connect to address localhost and port 8162: Connection refused [06:16:58] PROBLEM - cp38 Haproxy TLS backend for mwtask181 on cp38 is CRITICAL: connect to address localhost and port 8160: Connection refused [06:16:59] PROBLEM - cp38 Haproxy TLS backend for mw151 on cp38 is CRITICAL: connect to address localhost and port 8113: Connection refused [06:17:02] PROBLEM - cp38 Haproxy TLS backend for mw182 on cp38 is CRITICAL: connect to address localhost and port 8120: Connection refused [06:17:02] PROBLEM - cp38 Haproxy TLS backend for swiftproxy171 on cp38 is CRITICAL: connect to address localhost and port 8207: Connection refused [06:17:05] PROBLEM - cp38 Haproxy TLS backend for mw202 on cp38 is CRITICAL: connect to address localhost and port 8133: Connection refused [06:17:05] PROBLEM - cp38 Haproxy TLS backend for mw153 on cp38 is CRITICAL: connect to address localhost and port 8121: Connection refused [06:17:07] PROBLEM - cp38 Haproxy TLS backend for mw191 on cp38 is CRITICAL: connect to address localhost and port 8129: Connection refused [06:17:18] PROBLEM - cp38 Haproxy TLS backend for mw152 on cp38 is CRITICAL: connect to address localhost and port 8114: Connection refused [06:17:24] PROBLEM - cp38 Haproxy TLS backend for mw161 on cp38 is CRITICAL: connect to address localhost and port 8115: Connection refused [06:17:26] PROBLEM - cp38 Haproxy TLS backend for mw163 on cp38 is CRITICAL: connect to address localhost and port 8123: Connection refused [06:17:35] PROBLEM - cp38 Haproxy TLS backend for phorge171 on cp38 is CRITICAL: connect to address localhost and port 8202: Connection refused [06:17:42] PROBLEM - cp38 Haproxy TLS backend for mwtask161 on cp38 is CRITICAL: connect to address localhost and port 8163: Connection refused [06:17:42] PROBLEM - cp38 Haproxy TLS backend for mw162 on cp38 is CRITICAL: connect to address localhost and port 8116: Connection refused [06:17:43] PROBLEM - cp38 Haproxy TLS backend for matomo151 on cp38 is CRITICAL: connect to address localhost and port 8203: Connection refused [06:17:49] PROBLEM - cp38 Haproxy TLS backend for mw173 on cp38 is CRITICAL: connect to address localhost and port 8125: Connection refused [06:18:09] PROBLEM - cp38 Haproxy TLS backend for mw193 on cp38 is CRITICAL: connect to address localhost and port 8131: Connection refused [06:27:49] RECOVERY - cp38 Haproxy TLS backend for mw173 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8125 [06:28:09] RECOVERY - cp38 Haproxy TLS backend for mw193 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8131 [06:28:16] RECOVERY - cp38 Haproxy TLS backend for mw181 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8119 [06:28:19] RECOVERY - cp38 health.wikitide.net HTTPS on cp38 is OK: HTTP OK: HTTP/1.1 200 OK - 268 bytes in 0.012 second response time [06:28:19] RECOVERY - cp38 Haproxy TLS backend for swiftproxy161 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8206 [06:28:24] RECOVERY - cp38 Haproxy TLS backend for reports171 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8205 [06:28:24] RECOVERY - cp38 Haproxy TLS backend for mw183 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8127 [06:28:29] RECOVERY - cp38 Haproxy TLS backend for puppet181 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8204 [06:28:36] RECOVERY - cp38 Haproxy TLS backend for mw172 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8118 [06:28:50] RECOVERY - cp38 Haproxy TLS backend for mon181 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8201 [06:28:50] RECOVERY - cp38 Haproxy TLS backend for mw171 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8117 [06:28:50] RECOVERY - cp38 Haproxy TLS backend for mw192 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8130 [06:28:52] RECOVERY - cp38 Haproxy TLS backend for mw203 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8134 [06:28:53] RECOVERY - cp38 Haproxy TLS backend for mw201 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8132 [06:28:54] RECOVERY - cp38 Haproxy TLS backend for test151 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8181 [06:28:55] RECOVERY - cp38 Haproxy TLS backend for mwtask171 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8161 [06:28:58] RECOVERY - cp38 Haproxy TLS backend for mwtask151 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8162 [06:28:58] RECOVERY - cp38 Haproxy TLS backend for mwtask181 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8160 [06:28:59] RECOVERY - cp38 Haproxy TLS backend for mw151 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8113 [06:29:02] RECOVERY - cp38 Haproxy TLS backend for swiftproxy171 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8207 [06:29:02] RECOVERY - cp38 Haproxy TLS backend for mw182 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8120 [06:29:05] RECOVERY - cp38 Haproxy TLS backend for mw202 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8133 [06:29:05] RECOVERY - cp38 Haproxy TLS backend for mw153 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8121 [06:29:07] RECOVERY - cp38 Haproxy TLS backend for mw191 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8129 [06:29:18] RECOVERY - cp38 Haproxy TLS backend for mw152 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8114 [06:29:24] RECOVERY - cp38 Haproxy TLS backend for mw161 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8115 [06:29:26] RECOVERY - cp38 Haproxy TLS backend for mw163 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8123 [06:29:35] RECOVERY - cp38 Haproxy TLS backend for phorge171 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8202 [06:29:42] RECOVERY - cp38 Haproxy TLS backend for mw162 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8116 [06:29:42] RECOVERY - cp38 Haproxy TLS backend for mwtask161 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8163 [06:29:43] RECOVERY - cp38 Haproxy TLS backend for matomo151 on cp38 is OK: TCP OK - 0.000 second response time on localhost port 8203 [06:39:19] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [06:39:20] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 1-00:24:28) [06:39:21] mwtask161: not running [06:39:22] mwtask171: not running [06:39:23] mwtask181: not running [07:00:44] [02mw-config] 07Aeywoo commented on pull request #5887: Conflicts are resolved @RhinosF1. 13https://github.com/miraheze/mw-config/pull/5887#issuecomment-2781274109 [07:01:15] miraheze/mw-config - Aeywoo the build passed. [07:39:22] * MirahezeLSBot is checking the other mwtask* servers on refreshLinks [07:39:23] mwtask151: sudo -u www-data php /srv/mediawiki/1.43/maintenance/run.php refreshLinks --wiki=zhindividualballwiki 10001 (running for 1-01:24:30) [07:39:24] mwtask161: not running [07:39:25] mwtask171: not running [07:39:26] mwtask181: not running [07:50:49] PROBLEM - cp37 Disk Space on cp37 is WARNING: DISK WARNING - free space: / 49877MiB (10% inode=99%); [08:18:31] PROBLEM - mw203 HTTPS on mw203 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:18:32] PROBLEM - mw191 MediaWiki Rendering on mw191 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.010 second response time [08:18:34] PROBLEM - mw161 MediaWiki Rendering on mw161 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:34] PROBLEM - mw181 MediaWiki Rendering on mw181 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:36] PROBLEM - mw171 MediaWiki Rendering on mw171 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:36] PROBLEM - mw192 MediaWiki Rendering on mw192 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:37] PROBLEM - cp36 HTTPS on cp36 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [08:18:39] PROBLEM - mw161 HTTPS on mw161 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:18:40] PROBLEM - mw193 MediaWiki Rendering on mw193 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:41] PROBLEM - mw172 MediaWiki Rendering on mw172 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [08:18:48] PROBLEM - mw162 MediaWiki Rendering on mw162 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:50] PROBLEM - mw151 MediaWiki Rendering on mw151 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:53] PROBLEM - mw151 HTTPS on mw151 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:18:55] Huh [08:18:56] PROBLEM - mw203 MediaWiki Rendering on mw203 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:57] PROBLEM - mw191 HTTPS on mw191 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:18:57] PROBLEM - mw153 MediaWiki Rendering on mw153 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:18:59] PROBLEM - mw152 HTTPS on mw152 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:18:59] PROBLEM - mw201 MediaWiki Rendering on mw201 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.012 second response time [08:19:01] PROBLEM - mw183 MediaWiki Rendering on mw183 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:19:06] PROBLEM - mw163 MediaWiki Rendering on mw163 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:19:06] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is CRITICAL: CRITICAL - NGINX Error Rate is 79% [08:19:07] That's not supposed to be happening [08:19:10] PROBLEM - mw173 MediaWiki Rendering on mw173 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:19:10] PROBLEM - mw182 MediaWiki Rendering on mw182 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:19:13] PROBLEM - mw171 HTTPS on mw171 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:15] PROBLEM - cp37 HTTPS on cp37 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 503 [08:19:16] PROBLEM - mw183 HTTPS on mw183 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:17] PROBLEM - cp37 Varnish Backends on cp37 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [08:19:18] PROBLEM - mw192 HTTPS on mw192 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:18] PROBLEM - mw173 HTTPS on mw173 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:27] PROBLEM - mw202 HTTPS on mw202 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:28] PROBLEM - mw152 MediaWiki Rendering on mw152 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 8191 bytes in 0.011 second response time [08:19:34] PROBLEM - mw172 HTTPS on mw172 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:35] PROBLEM - mw193 HTTPS on mw193 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/2 502 [08:19:53] PROBLEM - mw162 HTTPS on mw162 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10001 milliseconds with 0 bytes received [08:20:00] PROBLEM - db181 Current Load on db181 is CRITICAL: LOAD CRITICAL - total load average: 248.23, 109.48, 43.33 [08:20:06] PROBLEM - mw202 MediaWiki Rendering on mw202 is CRITICAL: CRITICAL - Socket timeout after 10 seconds [08:20:06] PROBLEM - mw163 HTTPS on mw163 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10002 milliseconds with 0 bytes received [08:20:09] PROBLEM - mw153 HTTPS on mw153 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10000 milliseconds with 0 bytes received [08:20:10] PROBLEM - mw201 HTTPS on mw201 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [08:20:15] PROBLEM - mw181 HTTPS on mw181 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10003 milliseconds with 0 bytes received [08:20:21] PROBLEM - mw182 HTTPS on mw182 is CRITICAL: HTTP CRITICAL - Invalid HTTP response received from host on port 443: cURL returned 28 - Operation timed out after 10004 milliseconds with 0 bytes received [08:20:22] PROBLEM - cp36 Varnish Backends on cp36 is CRITICAL: 19 backends are down. mw151 mw152 mw161 mw162 mw171 mw172 mw181 mw182 mw153 mw163 mw173 mw183 mw191 mw192 mw193 mw201 mw202 mw203 mediawiki [08:22:09] !log [rhinos@mwtask181] starting deploy of {'config': True, 'force': True} to all [08:22:17] PROBLEM - db181 MariaDB on db181 is UNKNOWN: [08:22:43] PROBLEM - db181 APT on db181 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 60 seconds. [08:23:05]