[04:35:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeO51 [04:35:12] [02miraheze/services] 07MirahezeSSLBot 03787886b - BOT: Updating services config for wikis [06:25:33] RECOVERY - cp3 Disk Space on cp3 is OK: DISK OK - free space: / 2927 MB (12% inode=94%); [08:49:23] PROBLEM - test1 Current Load on test1 is WARNING: WARNING - load average: 1.89, 1.63, 1.45 [08:51:23] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.48, 1.59, 1.45 [08:57:21] PROBLEM - test1 Current Load on test1 is CRITICAL: CRITICAL - load average: 2.10, 1.77, 1.54 [08:59:21] PROBLEM - test1 Current Load on test1 is WARNING: WARNING - load average: 1.92, 1.85, 1.60 [09:03:20] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.46, 1.67, 1.58 [09:13:17] PROBLEM - test1 Current Load on test1 is WARNING: WARNING - load average: 1.75, 1.83, 1.67 [09:15:16] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.42, 1.68, 1.64 [10:24:59] PROBLEM - test1 Current Load on test1 is CRITICAL: CRITICAL - load average: 2.13, 1.83, 1.53 [10:26:59] PROBLEM - test1 Current Load on test1 is WARNING: WARNING - load average: 1.87, 1.86, 1.57 [10:28:58] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.40, 1.70, 1.54 [10:56:51] PROBLEM - test1 Current Load on test1 is CRITICAL: CRITICAL - load average: 2.27, 1.76, 1.52 [10:58:50] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.62, 1.66, 1.51 [11:29:41] PROBLEM - test1 Current Load on test1 is CRITICAL: CRITICAL - load average: 2.57, 2.09, 1.68 [11:33:39] PROBLEM - test1 Current Load on test1 is WARNING: WARNING - load average: 1.27, 1.85, 1.69 [11:37:38] RECOVERY - test1 Current Load on test1 is OK: OK - load average: 1.10, 1.53, 1.60 [11:39:09] Hello lukash98! If you have any questions, feel free to ask and someone should answer soon. [11:55:41] Hi there, is Rhinos around? [11:58:13] Hello, there. I am from piano.miraheze.org. Trying to understand why all the pictures (files) gone. [11:58:37] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 4 datacenters are down: 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:59:11] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw1 mw2 [11:59:37] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [11:59:43] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 2 backends are down. mw2 mw3 [12:01:37] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [12:01:43] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [12:02:36] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [12:03:11] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [12:18:40] lukash98: I'm sorry i just seen your message let me get someone from operations to help you! [12:18:44] paladox: RhinosF1 ^ [12:19:00] @Raidencrystal I dont know if he is around how can i help? [12:21:00] Nah just wanted to explain about something on User:RhinosF1/Anderlaxe [12:21:42] @Raidencrystal feel free to explain it here and im sure he'll see it [12:51:03] PROBLEM - cp3 Disk Space on cp3 is WARNING: DISK WARNING - free space: / 2649 MB (10% inode=94%); [12:51:35] Oof paladox ^ [13:15:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JeOxd [13:15:10] [02miraheze/services] 07MirahezeSSLBot 0385402a5 - BOT: Updating services config for wikis [13:30:16] hmm [13:30:48] I see images on https://piano.miraheze.org/wiki/Служебная:Список_файлов [13:30:49] [ Список файлов — Обслуживание и ремонт фортепиано ] - piano.miraheze.org [13:36:30] Right! Files are there now. Might it was a momentary lapse of reason.. Thankyou [13:57:51] !log gluster volume set mvolume network.ping-timeout "10" on gluster [13:58:01] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:10:24] !log gluster volume set mvolume client.event-threads "6" - on gluster [14:10:30] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:15:16] !log gluster volume set mvolume server.event-threads "2" - on gluster [14:15:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [14:48:38] !log gluster volume set mvolume performance.parallel-readdir on - on gluster [14:48:42] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:30:34] !log gluster volume set mvolume client.event-threads "2" [15:30:39] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:31:21] !log gluster volume set mvolume performance.parallel-readdir off - on gluster [15:31:26] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:38:33] !log gluster volume set mvolume network.ping-timeout "15" [15:38:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [15:53:29] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [15:55:30] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [16:27:31] [02landing] 07cuprevenge opened pull request 03#13: korean translation - 13https://git.io/Je3vG [16:41:38] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 1 backends are down. mw3 [16:41:43] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw3 [16:43:37] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [16:43:43] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [16:48:37] Anyone mind reviewing https://github.com/miraheze/landing/pull/13? To double check what travis said as I'm not seeing why it's not parsed right [16:48:37] [ korean translation by cuprevenge · Pull Request #13 · miraheze/landing · GitHub ] - github.com [16:49:25] Never mind spotted it [16:50:44] [02landing] 07RhinosF1 synchronize pull request 03#13: korean translation - 13https://git.io/Je3vG [16:51:07] paladox: I'll wait for Travis but any issues ^ [16:51:38] Ok, i doin't see any issues with adding more translations. I doin't speak the language so cannot comment on that aspect. [16:52:12] paladox: plugged a few into Google translate and seems fine [16:52:18] ok [16:53:27] your free to merge it! [16:53:53] [02landing] 07RhinosF1 closed pull request 03#13: korean translation - 13https://git.io/Je3vG [16:53:54] [02miraheze/landing] 07RhinosF1 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3f8 [16:53:56] [02miraheze/landing] 07cuprevenge 030102410 - korean translation (#13) * korean translation [16:54:09] paladox: ^ done [16:54:16] ok [16:59:22] [02landing] 07paladox commented on pull request 03#13: korean translation - 13https://git.io/Je3fz [17:22:32] [02landing] 07RhinosF1 created branch 03RhinosF1-patch-1 - 13https://git.io/fxEQA [17:22:34] [02miraheze/landing] 07RhinosF1 pushed 031 commit to 03RhinosF1-patch-1 [+0/-0/±1] 13https://git.io/Je3fd [17:22:35] [02miraheze/landing] 07RhinosF1 039503afc - Activate Korean Translations Please double check Google translate [17:22:37] [02landing] 07RhinosF1 opened pull request 03#14: Activate Korean Translations - 13https://git.io/Je3fF [17:22:50] paladox: ^ [17:23:49] miraheze/landing/RhinosF1-patch-1/9503afc - RhinosF1 The build passed. https://travis-ci.org/miraheze/landing/builds/586643157 [17:36:01] JohnLewis: https://meta.miraheze.org/wiki/User_talk:RhinosF1 [17:36:06] [ User talk:RhinosF1 - Miraheze Meta ] - meta.miraheze.org [17:36:38] RhinosF1: if you're deleting to permanently delete immediately to then recreate, that's a sysadmin job [17:36:49] as a sysadmin needs to permanently delete it [17:37:17] JohnLewis: I'm mobile but I can do the On-Wiki part of the deletion [17:37:29] paladox [17:37:44] if you're not doing the sysadmin side, don't delete on wiki :) [17:37:56] JohnLewis: k [17:37:59] paladox: ^ [17:39:57] well anyway the "sysadmin" part should be ops since they need to drop after [17:40:18] Reception123: see my post seconds ago in -staff [17:40:33] see my answer in staff :) [17:40:46] Seen [17:43:45] PROBLEM - lizardfs5 Puppet on lizardfs5 is CRITICAL: CRITICAL: Puppet has 4 failures. Last run 2 minutes ago with 4 failures. Failed resources (up to 3 shown) [17:43:47] PROBLEM - puppet1 Puppet on puppet1 is CRITICAL: CRITICAL: Puppet has 9 failures. Last run 2 minutes ago with 9 failures. Failed resources (up to 3 shown) [17:43:53] PROBLEM - bacula1 Puppet on bacula1 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 2 minutes ago with 2 failures. Failed resources (up to 3 shown) [17:44:04] PROBLEM - misc2 Puppet on misc2 is CRITICAL: CRITICAL: Puppet has 13 failures. Last run 2 minutes ago with 13 failures. Failed resources (up to 3 shown) [17:44:05] PROBLEM - glusterfs2 Puppet on glusterfs2 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 2 minutes ago with 6 failures. Failed resources (up to 3 shown) [17:44:26] PROBLEM - db4 Puppet on db4 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 2 minutes ago with 6 failures. Failed resources (up to 3 shown) [17:44:40] PROBLEM - glusterfs1 Puppet on glusterfs1 is CRITICAL: CRITICAL: Puppet has 6 failures. Last run 2 minutes ago with 6 failures. Failed resources (up to 3 shown) [17:44:46] PROBLEM - cp4 Puppet on cp4 is CRITICAL: CRITICAL: Puppet has 360 failures. Last run 2 minutes ago with 360 failures. Failed resources (up to 3 shown) [17:44:48] PROBLEM - db5 Puppet on db5 is CRITICAL: CRITICAL: Puppet has 3 failures. Last run 3 minutes ago with 3 failures. Failed resources (up to 3 shown) [17:45:01] PROBLEM - mw3 Puppet on mw3 is CRITICAL: CRITICAL: Puppet has 364 failures. Last run 2 minutes ago with 364 failures. Failed resources (up to 3 shown) [17:45:17] PROBLEM - misc4 Puppet on misc4 is CRITICAL: CRITICAL: Puppet has 14 failures. Last run 3 minutes ago with 14 failures. Failed resources (up to 3 shown) [17:45:21] PROBLEM - lizardfs4 Puppet on lizardfs4 is CRITICAL: CRITICAL: Puppet has 2 failures. Last run 3 minutes ago with 2 failures. Failed resources (up to 3 shown) [17:45:33] PROBLEM - misc1 Puppet on misc1 is CRITICAL: CRITICAL: Puppet has 39 failures. Last run 3 minutes ago with 39 failures. Failed resources (up to 3 shown) [17:45:34] PROBLEM - misc3 Puppet on misc3 is CRITICAL: CRITICAL: Puppet has 11 failures. Last run 3 minutes ago with 11 failures. Failed resources (up to 3 shown) [17:45:35] PROBLEM - cp2 Puppet on cp2 is CRITICAL: CRITICAL: Puppet has 246 failures. Last run 2 minutes ago with 246 failures. Failed resources (up to 3 shown): File[/usr/local/bin/nginx-prometheus-exporter],File[antiguabarbudacalypso.com],File[antiguabarbudacalypso.com_private],File[spiral.wiki] [17:45:40] PROBLEM - ns1 Puppet on ns1 is CRITICAL: CRITICAL: Puppet has 5 failures. Last run 3 minutes ago with 5 failures. Failed resources (up to 3 shown) [17:45:45] PROBLEM - cp3 Puppet on cp3 is CRITICAL: CRITICAL: Puppet has 169 failures. Last run 2 minutes ago with 169 failures. Failed resources (up to 3 shown): File[/etc/nginx/mime.types],File[/etc/nginx/fastcgi_params],File[/usr/local/bin/nginx-prometheus-exporter],File[antiguabarbudacalypso.com] [17:45:50] PROBLEM - mw2 Puppet on mw2 is CRITICAL: CRITICAL: Puppet has 362 failures. Last run 3 minutes ago with 362 failures. Failed resources (up to 3 shown) [17:46:12] PROBLEM - mw1 Puppet on mw1 is CRITICAL: CRITICAL: Puppet has 372 failures. Last run 3 minutes ago with 372 failures. Failed resources (up to 3 shown): File[/usr/local/bin/fileLockScript.sh],File[/usr/local/bin/foreachwikiindblist],File[/usr/local/bin/pushServices.sh],File[/etc/logrotate.d/salt-common] [17:52:48] RECOVERY - db5 Puppet on db5 is OK: OK: Puppet is currently enabled, last run 6 seconds ago with 0 failures [17:53:17] RECOVERY - misc4 Puppet on misc4 is OK: OK: Puppet is currently enabled, last run 19 seconds ago with 0 failures [17:53:21] RECOVERY - lizardfs4 Puppet on lizardfs4 is OK: OK: Puppet is currently enabled, last run 40 seconds ago with 0 failures [17:53:32] RECOVERY - misc1 Puppet on misc1 is OK: OK: Puppet is currently enabled, last run 27 seconds ago with 0 failures [17:53:33] RECOVERY - misc3 Puppet on misc3 is OK: OK: Puppet is currently enabled, last run 33 seconds ago with 0 failures [17:53:40] RECOVERY - ns1 Puppet on ns1 is OK: OK: Puppet is currently enabled, last run 55 seconds ago with 0 failures [17:53:45] RECOVERY - lizardfs5 Puppet on lizardfs5 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:53:47] RECOVERY - puppet1 Puppet on puppet1 is OK: OK: Puppet is currently enabled, last run 58 seconds ago with 0 failures [17:53:52] RECOVERY - bacula1 Puppet on bacula1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:54:01] RECOVERY - mw2 Puppet on mw2 is OK: OK: Puppet is currently enabled, last run 30 seconds ago with 0 failures [17:54:04] RECOVERY - misc2 Puppet on misc2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:54:05] RECOVERY - glusterfs2 Puppet on glusterfs2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:54:14] RECOVERY - mw1 Puppet on mw1 is OK: OK: Puppet is currently enabled, last run 32 seconds ago with 0 failures [17:54:26] RECOVERY - db4 Puppet on db4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:54:39] RECOVERY - glusterfs1 Puppet on glusterfs1 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:54:46] RECOVERY - cp4 Puppet on cp4 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:55:09] RECOVERY - mw3 Puppet on mw3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:55:33] RECOVERY - cp2 Puppet on cp2 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [17:55:50] RECOVERY - cp3 Puppet on cp3 is OK: OK: Puppet is currently enabled, last run 1 minute ago with 0 failures [18:04:34] RhinosF1 you doin't need me to review that because i doin't speak the language. So if you think it lgty merge. :) [18:05:00] paladox: will merge [18:05:08] RhinosF1 also ok to the thing JohnLewis said [18:05:30] paladox: you going to do it? [18:05:47] [02landing] 07RhinosF1 closed pull request 03#14: Activate Korean Translations - 13https://git.io/Je3fF [18:05:48] [02miraheze/landing] 07RhinosF1 pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3J9 [18:05:50] [02miraheze/landing] 07RhinosF1 037c84e6e - Activate Korean Translations (#14) Please double check Google translate [18:05:53] I guess so [18:06:15] Thx [18:06:40] RhinosF1 i'm not sure if they want it to be recreated (the same wiki) or if they want a different named wiki. [18:07:43] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 3 backends are down. mw1 mw2 mw3 [18:07:53] Known [18:07:53] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [18:08:13] known? [18:08:14] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [18:08:24] JohnLewis see -staff [18:08:28] JohnLewis: the issue [18:08:31] PROBLEM - cp3 Stunnel Http for mw3 on cp3 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [18:09:07] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw3 [18:09:43] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [18:09:53] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [18:10:14] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [18:10:24] paladox: I believe same name [18:10:26] RECOVERY - cp3 Stunnel Http for mw3 on cp3 is OK: HTTP OK: HTTP/1.1 200 OK - 24516 bytes in 0.659 second response time [18:11:05] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [18:12:16] ok [18:12:29] !log delete philosiversewiki per request https://meta.miraheze.org/wiki/User_talk:RhinosF1 [18:12:30] [ User talk:RhinosF1 - Miraheze Meta ] - meta.miraheze.org [18:12:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [18:14:53] RhinosF1 done [18:15:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3Uv [18:15:11] [02miraheze/services] 07MirahezeSSLBot 03507aa82 - BOT: Updating services config for wikis [18:15:21] paladox: thx [18:15:39] [02landing] 07paladox deleted branch 03RhinosF1-patch-1 - 13https://git.io/fxEQA [18:15:40] [02miraheze/landing] 07paladox deleted branch 03RhinosF1-patch-1 [19:19:51] Hello lukash18! If you have any questions, feel free to ask and someone should answer soon. [20:35:11] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3k0 [20:35:12] [02miraheze/services] 07MirahezeSSLBot 03a9f72ab - BOT: Updating services config for wikis [20:48:16] [02miraheze/CreateWiki] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3kS [20:48:17] [02miraheze/CreateWiki] 07paladox 0330899ed - Add new line to output of drop database syntax [20:50:34] [02miraheze/mediawiki] 07paladox pushed 031 commit to 03REL1_33 [+0/-0/±1] 13https://git.io/Je3k5 [20:50:35] [02miraheze/mediawiki] 07paladox 030b0ed03 - Update CW [20:56:55] paladox: with special:EmailUser does the email from say the wiki name it came from or just Miraheze/ [20:56:57] ?* [20:58:57] Zppix i'm not really sure :( [20:59:01] oh ok [21:01:30] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:03:29] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [21:04:29] ZppixBot: Depends on the subject I think, shall we try it - it might show in the footer [21:04:33] Zppix: ^ [21:05:23] ok [21:05:41] RhinosF1: but i dont mean the subject i mean like the FROM: [21:06:16] Zppix: see what your email shows [21:06:40] RhinosF1: that shows meta can you try one from testwiki? [21:06:49] Zppix: ye [21:08:29] Zppix: done [21:09:14] It does use wiki name cool [21:09:15] !log drop all wikis from https://phabricator.miraheze.org/P227 [21:09:16] [ ✎ P227 (An Untitled Masterwork) ] - phabricator.miraheze.org [21:09:20] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:11:30] Zppix: nice [21:13:51] PROBLEM - cp2 Stunnel Http for mw3 on cp2 is CRITICAL: CHECK_NRPE STATE CRITICAL: Socket timeout after 10 seconds. [21:14:02] PROBLEM - cp2 Varnish Backends on cp2 is CRITICAL: 2 backends are down. mw2 mw3 [21:14:09] PROBLEM - ns1 GDNSD Datacenters on ns1 is CRITICAL: CRITICAL - 6 datacenters are down: 107.191.126.23/cpweb, 2604:180:0:33b::2/cpweb, 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:15:24] PROBLEM - cp3 Varnish Backends on cp3 is CRITICAL: 1 backends are down. mw1 [21:15:29] PROBLEM - misc1 GDNSD Datacenters on misc1 is CRITICAL: CRITICAL - 4 datacenters are down: 128.199.139.216/cpweb, 2400:6180:0:d0::403:f001/cpweb, 81.4.109.133/cpweb, 2a00:d880:5:8ea::ebc7/cpweb [21:15:31] * RhinosF1 looks [21:15:43] PROBLEM - cp4 Varnish Backends on cp4 is CRITICAL: 1 backends are down. mw1 [21:15:50] RECOVERY - cp2 Stunnel Http for mw3 on cp2 is OK: HTTP OK: HTTP/1.1 200 OK - 24570 bytes in 3.235 second response time [21:16:01] RECOVERY - cp2 Varnish Backends on cp2 is OK: All 5 backends are healthy [21:16:09] RECOVERY - ns1 GDNSD Datacenters on ns1 is OK: OK - all datacenters are online [21:16:13] looks fine [21:21:18] RECOVERY - cp3 Varnish Backends on cp3 is OK: All 5 backends are healthy [21:21:30] RECOVERY - misc1 GDNSD Datacenters on misc1 is OK: OK - all datacenters are online [21:21:43] RECOVERY - cp4 Varnish Backends on cp4 is OK: All 5 backends are healthy [21:42:44] paladox: are cp1 and cp2 the same CP? [21:42:56] Nope [21:43:02] oh [21:43:10] i wasen't here for cp1 i think [21:43:26] .ip cp1.miraheze.org [21:44:06] cp1.miraheze.org is not a thing anymore [21:44:11] [IP/Host Lookup] Hostname: cp2.miraheze.org | Location: United States | Region: Georgia | City: Atlanta | ISP: AS3842 RamNode LLC [21:44:33] if it isnt then why still have cp1 in dns? [21:44:52] it's not [21:45:15] oh i see [21:45:23] (forgets that it would still resolve to cp2) [21:45:55] paladox: my brain has been a little slow for some reason :P [21:46:00] heh [21:47:11] paladox: do you know if i were to register a domain could i have it resolve to a website on tools.wmflabs.org? [21:47:36] You could i guess by adding the ip. [21:47:41] But i'm no expert [21:48:02] paladox: i just know you like touching wmf's configs so i didnt know if you knew of any anti-redirect thingy [21:48:26] the only wmf configs i've really touched are phabricator or gerrit :P [21:48:26] I'll ask -cloud [21:48:28] and some of ci [21:53:49] !log MariaDB [philosiversewiki]> update content_models set model_id = 1 where model_id = 4; [21:53:54] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:54:11] !log MariaDB [philosiversewiki]> update content_models set model_id = 4 where model_id = 3; [21:54:16] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:55:08] !log update content_models set model_id = 3 where model_id = 4; [21:55:13] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [21:55:22] paladox: back [21:55:31] RhinosF1: someone left a msg on your talk page [21:55:46] Zppix: that's what paladox is fixing [21:56:43] Fixed [22:00:35] paladox: fyi *.miraheze.org expires in 35 days [22:00:40] from globalsign [22:00:43] Zppix: known [22:00:47] There's a ticket in phab [22:00:52] SPF|Cloud is handling that :) [22:00:59] Damnit let me find something new :( [22:01:26] Zppix: SN - that could be a CVT action potentially [22:01:32] looking [22:01:53] RhinosF1: handling it now [22:02:53] Damnit Void-bot [22:02:57] Voidwalker: [22:03:51] * Zppix rolls my eyes at Voidwalker xD [22:04:48] Voidwalker: I need to report an unauthorized bot account, its at User:Void [22:04:55] xD [22:05:23] whoops :P [22:05:40] smh [22:06:05] I'm stalking their RC for a bit Voidwalker [22:06:53] yeah, they don't really have a local admin [22:07:13] Who needs that... pssh im not good enough? Voidwalker xD [22:07:47] lol [22:07:58] Zppix: why don't you take the wiki requests before I beat you to it? [22:08:24] RhinosF1: you can have all the non english ones [22:08:51] Zppix: I only speak poor french and native english so i'll leave them for now [22:09:50] RhinosF1: i speak poor english and no french :P [22:09:57] and im a american [22:10:00] Zppix: heh [22:13:40] [02puppet] 07paladox created branch 03paladox-patch-4 - 13https://git.io/vbiAS [22:13:41] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/Je3Ix [22:13:43] [02miraheze/puppet] 07paladox 038b6df00 - gluster: Add monotoring for port 24007 and 49152 [22:13:44] [02puppet] 07paladox opened pull request 03#1087: gluster: Add monotoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:14:33] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+1/-0/±0] 13https://git.io/Je3Ih [22:14:35] [02miraheze/puppet] 07paladox 031d31b3f - Create monotoring.yaml [22:14:36] [02puppet] 07paladox synchronize pull request 03#1087: gluster: Add monotoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:14:53] [02puppet] 07paladox edited pull request 03#1087: gluster: Add basic monitoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:15:09] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3Ij [22:15:11] [02miraheze/services] 07MirahezeSSLBot 039125084 - BOT: Updating services config for wikis [22:15:20] [02puppet] 07paladox synchronize pull request 03#1087: gluster: Add basic monitoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:15:21] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/Je3Lf [22:15:23] [02miraheze/puppet] 07paladox 0352a61a3 - Update init.pp [22:15:31] [02puppet] 07paladox synchronize pull request 03#1087: gluster: Add basic monitoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:15:32] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+1/-1/±0] 13https://git.io/Je3LJ [22:15:34] [02miraheze/puppet] 07paladox 03b8b8c35 - Rename monotoring.yaml to monitoring.yaml [22:15:37] [02puppet] 07paladox closed pull request 03#1087: gluster: Add basic monitoring for port 24007 and 49152 - 13https://git.io/Je3Ip [22:15:39] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+1/-0/±1] 13https://git.io/Je3LU [22:15:40] [02miraheze/puppet] 07paladox 037d981c7 - gluster: Add basic monitoring for port 24007 and 49152 (#1087) * gluster: Add monotoring for port 24007 and 49152 * Create monotoring.yaml * Update init.pp * Rename monotoring.yaml to monitoring.yaml [22:15:50] do some changes there paladox ? [22:16:13] Zppix hmm? [22:16:22] paladox: the notifico spam [22:16:39] oh, yes. [22:16:44] I've done some changes :) [22:21:23] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-4 [22:21:24] [02puppet] 07paladox deleted branch 03paladox-patch-4 - 13https://git.io/vbiAS [22:21:51] i've just realised... i've duplicated that whole thing [22:23:31] [02puppet] 07paladox created branch 03paladox-patch-4 - 13https://git.io/vbiAS [22:23:33] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-0/±1] 13https://git.io/Je3LY [22:23:34] [02miraheze/puppet] 07paladox 0389c565f - gluster: Fix monitoring [22:23:36] [02puppet] 07paladox opened pull request 03#1088: gluster: Fix monitoring - 13https://git.io/Je3L3 [22:23:54] [02miraheze/puppet] 07paladox pushed 031 commit to 03paladox-patch-4 [+0/-1/±0] 13https://git.io/Je3LG [22:23:55] [02miraheze/puppet] 07paladox 0319b7597 - Delete monitoring.yaml [22:23:57] [02puppet] 07paladox synchronize pull request 03#1088: gluster: Fix monitoring - 13https://git.io/Je3L3 [22:24:21] [02puppet] 07paladox closed pull request 03#1088: gluster: Fix monitoring - 13https://git.io/Je3L3 [22:24:22] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-1/±1] 13https://git.io/Je3Ln [22:24:24] hahaha [22:24:24] [02miraheze/puppet] 07paladox 03b1b0945 - gluster: Fix monitoring (#1088) * gluster: Fix monitoring * Delete monitoring.yaml [22:25:33] [02puppet] 07paladox deleted branch 03paladox-patch-4 - 13https://git.io/vbiAS [22:25:35] [02miraheze/puppet] 07paladox deleted branch 03paladox-patch-4 [22:50:11] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 7.43, 6.41, 5.47 [22:52:07] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 4.96, 5.81, 5.36 [22:57:07] !log rhinos@mw1:/srv/mediawiki/w/maintenance$ sudo -u www-data php deleteBatch.php -r [[mh:meta:User_talk:RhinosF1]] /home/rhinos/pagedel.txt --wiki philosiversewik [22:57:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [22:58:19] RhinosF1: why? [22:58:34] Zppix: requested [22:58:39] oh [22:58:49] on [[mh:meta:User talk:RhinosF1]] [22:59:34] ok [23:00:05] RhinosF1: you probably should of made it bot [23:00:09] RhinosF1: i think --bot [23:00:43] Zppix: maybe [23:00:52] it's nearly done now anyway [23:10:12] [02miraheze/services] 07MirahezeSSLBot pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3LA [23:10:13] [02miraheze/services] 07MirahezeSSLBot 0335c9a80 - BOT: Updating services config for wikis [23:20:08] PROBLEM - mw3 Current Load on mw3 is CRITICAL: CRITICAL - load average: 8.00, 8.83, 7.04 [23:22:03] PROBLEM - mw3 Current Load on mw3 is WARNING: WARNING - load average: 4.95, 7.64, 6.83 [23:27:50] RECOVERY - mw3 Current Load on mw3 is OK: OK - load average: 5.91, 6.59, 6.59 [23:42:03] !log gluster volume set mvolume server.event-threads "1" - on gluster [23:42:08] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log, Master [23:55:14] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3tz [23:55:16] [02miraheze/puppet] 07paladox 038791b24 - gluster::mount Add new options owner and group [23:58:45] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3tg [23:58:46] [02miraheze/puppet] 07paladox 034792be6 - Revert "gluster::mount Add new options owner and group" This reverts commit 8791b245eee7de65ad974725cdef45315a96d85a. [23:59:25] [02miraheze/puppet] 07paladox pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/Je3t2 [23:59:27] [02miraheze/puppet] 07paladox 0332178c9 - mediawiki: Add new mount /mnt/mediawiki-static-new using gluster