[01:17:52] (03CR) 10Krinkle: Proof-of-concept to remove globals in ORES service (031 comment) [extensions/ORES] - 10https://gerrit.wikimedia.org/r/510166 (owner: 10Kosta Harlan) [01:20:15] (03CR) 10Krinkle: Proof-of-concept to remove globals in ORES service (031 comment) [extensions/ORES] - 10https://gerrit.wikimedia.org/r/510166 (owner: 10Kosta Harlan) [07:18:31] 10ORES, 10Scoring-platform-team, 10WMDE-Analytics-Engineering, 10Wikidata, 10User-GoranSMilovanovic: track quality of all/top 10000 Wikidata items over time - https://phabricator.wikimedia.org/T195702 (10GoranSMilovanovic) a:03GoranSMilovanovic [07:42:20] (03CR) 10jenkins-bot: Localisation updates from https://translatewiki.net. [extensions/ORES] - 10https://gerrit.wikimedia.org/r/510667 (owner: 10L10n-bot) [08:03:52] my update is that I ran into some drag building variables for the number of active editors on each wiki using spark today and didn't manage to finish building the variables [08:04:06] and I'm gonna take most of tomorrow off to prepare my ICA presentation. [08:04:26] I have a practice talk tomorrow [08:05:08] planning to make up for it on saturday probably [08:48:17] PROBLEM - puppet on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [08:48:30] PROBLEM - check users on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [08:48:48] PROBLEM - check disk on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234. Check system logs on 172.16.6.234 [08:49:44] PROBLEM - check load on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [08:55:21] PROBLEM - puppet on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [08:55:37] PROBLEM - check disk on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [08:55:49] PROBLEM - check load on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [08:56:03] PROBLEM - check users on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [08:57:52] PROBLEM - check users on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [08:58:23] PROBLEM - puppet on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [08:59:00] PROBLEM - check disk on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [08:59:26] PROBLEM - check load on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [09:15:19] PROBLEM - puppet on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [09:15:36] PROBLEM - check users on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [09:15:36] PROBLEM - check load on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123. Check system logs on 172.16.3.123 [09:15:49] PROBLEM - check disk on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [09:16:16] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [09:17:30] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [09:18:07] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [09:18:45] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [11:08:22] PROBLEM - puppet on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [11:08:32] PROBLEM - check users on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [11:08:52] PROBLEM - check disk on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [11:09:47] PROBLEM - check load on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer [11:15:22] PROBLEM - puppet on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [11:15:42] PROBLEM - check disk on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [11:15:52] PROBLEM - check load on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [11:16:07] PROBLEM - check users on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer [11:17:57] PROBLEM - check users on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [11:18:27] PROBLEM - puppet on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [11:19:02] PROBLEM - check disk on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [11:19:27] PROBLEM - check load on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer [11:35:21] PROBLEM - puppet on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [11:35:36] PROBLEM - check users on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [11:35:37] PROBLEM - check load on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [11:35:51] PROBLEM - check disk on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer [11:35:55] Looking into it from our side will let you know if we need you guys to do anything [11:35:58] Will ack for now [11:36:16] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [11:37:00] ACKNOWLEDGEMENT - check disk on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer zppix looking [11:37:12] ACKNOWLEDGEMENT - check load on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer zppix looking [11:37:21] ACKNOWLEDGEMENT - check users on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer zppix looking [11:37:29] ACKNOWLEDGEMENT - puppet on ORES-redis02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.123: Connection reset by peer zppix looking [11:37:31] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [11:37:59] ACKNOWLEDGEMENT - check disk on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer zppix looking [11:38:06] ACKNOWLEDGEMENT - check load on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer zppix looking [11:38:11] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125. Check system logs on 172.16.3.125 [11:38:14] ACKNOWLEDGEMENT - check users on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234: Connection reset by peer zppix looking [11:38:22] ACKNOWLEDGEMENT - puppet on ORES-web02.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.6.234. Check system logs on 172.16.6.234 zppix looking [11:38:46] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [11:40:23] ACKNOWLEDGEMENT - check disk on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer zppix looking [11:40:31] ACKNOWLEDGEMENT - check load on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer zppix looking [11:40:38] ACKNOWLEDGEMENT - check users on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer zppix looking [11:40:46] ACKNOWLEDGEMENT - puppet on ORES-web01.Experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.131: Connection reset by peer zppix looking [11:41:06] ACKNOWLEDGEMENT - check disk on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer zppix looking [11:41:13] ACKNOWLEDGEMENT - check load on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer zppix looking [11:41:20] ACKNOWLEDGEMENT - check users on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer zppix looking [11:41:27] ACKNOWLEDGEMENT - puppet on ORES-worker01.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.127: Connection reset by peer zppix looking [11:41:35] Sorry for spam [11:53:49] I will let you know when I see halfak around here [11:53:49] @notify halfak [11:53:49] 04Error: Command “notify” not recognized. Please review and correct what you’ve written. [12:08:38] Amir1: are you around and free for a min? [13:56:20] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [13:57:35] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [13:58:15] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [13:58:50] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [16:16:24] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [16:17:39] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [16:18:19] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [16:18:54] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [16:35:29] halfak: can you make sure in nrpe_local.cfg thats in /etc/nagios/ that it contains allowed_hosts=172.16.1.180 on the ores hostd [17:23:59] Zppix, I'll need to take a look at it tomorrow. I'm traveling today. Could you file a task? [18:36:28] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [18:37:43] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [18:38:23] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [18:38:58] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [20:56:31] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [20:57:47] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [20:58:26] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [20:59:01] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [23:16:35] PROBLEM - check load on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [23:17:50] PROBLEM - check users on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [23:18:30] PROBLEM - check disk on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer [23:19:05] PROBLEM - puppet on ORES-worker02.experimental is CRITICAL: CHECK_NRPE: Error - Could not connect to 172.16.3.125: Connection reset by peer