[08:26:49] is there some way to debug processes running on the toolforge grid? [13:57:39] does somebody know if there was a problem with memcached or similar? We had a problem in dewiki with an abusefilter that should have matched, but didn't [13:58:00] and it's kind of annoying, because the purpose is to enforce arbcom actions [13:59:43] Sagan: Nothing obvious comes to mind; could you file a Phabricator task? [14:01:24] ok, will do then [14:06:40] Seems like an old account of mine didn't get merged properly when we moved to global accounts. Anyone still doing cleanup of such problems? [14:09:55] jeblad, maybe the stewards can help you with that? [14:12:09] Perhaps I should just link them to the same account. No email, so I can't reset the password. [14:12:45] Perhaps that is why the merge failed. [14:32:52] Hello, could someone with shell access help me analyze some cache keys, please? (Or redirect me to the right place to ask) [14:36:45] If nobody responds, you could try #wikimedia-operations [14:36:54] I'd offer to help but i don't have shell access anymore [14:37:13] Daimona: How many are we talking about? [14:37:15] Sure, thanks. I wanted to try here because it's not serious [14:37:21] Reedy: In theory, one [14:37:31] But maybe we don't even need to check the key [14:37:38] Debug logs could be sufficient [14:39:46] To certain extent though, memcache keys are best effort, maybe the throttling key referenced in that bug just happened to be evicted from cache [14:40:54] That's what I was thinking [14:41:34] That said, I think I've rebuilt what the key should look like [14:41:41] But maybe it's better if we move to PM [14:42:14] Its not like this channel is so busy that you're interferring with other conversations ;) [14:42:36] It was just a precaution in case this is considered somewhat private :) [14:42:50] But well, it should already be pretty obvious from the task [14:43:24] They key wouldn't have an IP address in it, and the abusefilter that uses it is public, so I don't think it could be considred private data [14:43:41] I mean, it's easy enough to sanity check it before re-posting it [14:43:48] Sure [14:43:49] Unless it's many lines lon [14:43:51] g [14:44:03] So, in theory, it should be enough to grep debug logs for: dewiki:abusefilter:throttle:290:page:Wikipedia Diskussion:Schiedsgericht/Anfragen/Diskussionskomplex im Umfeld "Anetta Kahane":user:Brainswiffer [14:44:10] I'm uncertain about the quotes etc. [14:44:39] See https://phabricator.wikimedia.org/T210709#4811680 for sample messages [14:45:22] Are spaces even allowed in memcached keys? [14:45:56] That's another good question [14:46:18] I'd also presume not [14:46:39] Passing the components to wfMemcKey() might be a saner way to find out [14:46:41] Actually, I think we should call Title::getDBKey() instead of getPrefixedTitle [14:46:41] Most of the rest of MW hashes page titles before putting them in memcached keys [14:46:56] Or hashing, yes [14:47:51] Apparently, spaces are automatically replaced with underscores [14:48:00] Quotes seem to be allowed [14:48:36] I think it does hash things [14:48:49] line 842 of AbuseFilterRunner.php [14:49:02] $identifier = sha1( implode( ':', $identifiers ) ); [14:49:47] Eurgh [14:50:28] Indeed... [14:50:32] So that would make it be like dewiki:abusefilter:throttle:290:page,user: [14:50:58] Exactly [14:51:08] But well, maybe we don't even need the sha1 [14:51:52] Grepping until "user:" may be enough [14:52:34] Although, actually, that would be "user,page" [14:53:44] right [14:54:44] Now that I think about it, what could've happened is: [14:55:10] -The key got created yesterday, and it reached 2 by the end of the day [14:55:30] - Then it got to, say, 4 today [14:55:44] - Then it expired, and the new key started off from 0 [14:57:29] Or maybe not, today at 06:58 the filter disallowed an edit, so by that time the key was at 5 [14:57:57] But there've been 7 edits since then, in less than 24 hours [14:59:57] So the hash would be sha1( "404212:Wikipedia Diskussion:Schiedsgericht/Anfragen/Diskussionskomplexim Umfeld \"Anetta Kahane\"" ) [15:00:38] which is ce12284db0992734fd982f4a3ddd1f5f2b5c5408 [15:00:58] so dewiki:abusefilter:throttle:290:user,page:ce12284db0992734fd982f4a3ddd1f5f2b5c5408 [15:01:08] I think [15:01:42] seems correct [15:03:06] Rn my main guess is that the key was evicted for whatever reason [15:05:49] So Abusefilter has debug level logging at mwlog1001. I don't have access to that anymore (only logstash which only does "info" level logging), but that debug logging should be enough to verify what happened with this key [15:07:26] Reedy: Any chance you could paste on to the bug, what the results of grep ce12284db0992734fd982f4a3ddd1f5f2b5c5408 AbuseFilter.log is (on mwlog) [15:07:38] I can have a look, yeah [15:07:44] Agreed - and I also don't have access to mwlog. Poking the key should be unnecessary unless something ill is happening [15:08:00] Obviously, stating the obvious... Something isn't guaranteed to be in MW before its expiry time [15:08:12] That kind of assumes I managed to reconstruct that hash right, not sure how confident I feel about that [15:09:53] Maybe this is a sign i should try and get my shell access back :) [15:11:34] 0 results... But like you say, dunno if that means the hash is right ;p [15:12:33] This means we're doing it right [15:12:56] It would've been too easy otherwise [15:13:11] What happens if you grep "dewiki:abusefilter:throttle:290:user,page" instead? [15:30:19] reedy@mwlog1001:/srv/mw-log$ grep "dewiki:abusefilter:throttle:290" memcached.log [15:30:19] reedy@mwlog1001:/srv/mw-log$ [15:57:17] Uhm something's missing? [16:16:29] reedy@mwlog1001:/srv/mw-log$ zgrep "dewiki:abusefilter:throttle:290" archive/memcached-keys.log-201912* [16:16:29] reedy@mwlog1001:/srv/mw-log$ [16:23:49] I think it should be in mwlog (?) [16:56:32] Daimona: ? [16:56:36] The files are there on disk [16:57:03] reedy@mwlog1001:/srv/mw-log$ ls -al memcached.log [16:57:03] -rw-r--r-- 1 udp2log udp2log 6179236 Dec 17 16:56 memcached.log [17:26:45] Reedy: And is there any line like https://phabricator.wikimedia.org/T210709#4811680 ? [17:28:16] Not that specific one, but yes [17:28:52] reedy@mwlog1001:/srv/mw-log$ grep -c ":abusefilter:" memcached.log [17:28:52] 529 [17:29:17] lots of "ITEM TOO BIG" [17:35:53] Erm... [17:36:16] Could you please paste them somewhere? [17:40:41] they're mostly check-stash from what i can see [17:40:56] that's almost all that's in memcached.log for AF [19:33:25] I keep getting error 503s... [21:42:10] Huh, login.wikimedia.org hangs? [21:44:00] Got a timeout on the auth key but was still logged in? [21:54:08] A few people complaining about some potential EU issues [21:54:25] It is BREXIT!! [21:54:34] indeed, was just looking at that. looks like ATS on cp3050 was freaking out, not sure why yet. [21:54:37] * jeblad off to get his coffee [21:54:38] I've depooled the host. [21:56:08] Note that I got logged in even if the auth key had timed out. That could be an idication of a defunc 2fa system.