[00:14:02] <firespeaker>	 FYI that link to the [[Manual:Configuration_settings]] references a section that apparently no longer exists (#Debug.2Flogging)
[00:43:39] <firespeaker>	 can't seem to get logging working...
[00:52:07] <firespeaker>	 ah, no, was just not putting anything into the logs
[00:53:21] <firespeaker>	 oh my now it's working
[00:53:29] <firespeaker>	 tons of select on that page.....
[01:02:43] <firespeaker>	 [rdbms] Wikimedia\Rdbms\LoadBalancer::reuseOrOpenConnectionForNewRef: reusing co
[01:02:44] <firespeaker>	 nnection for 0/wikidb
[01:02:44] <firespeaker>	 [rdbms] WikiPage::pageData [0.203ms] localhost: SELECT  page_id,page_namespace,p
[01:02:44] <firespeaker>	 age_title,page_is_redirect,page_is_new,page_random,page_touched,page_links_updat
[01:02:44] <firespeaker>	 ed,page_latest,page_len,page_content_model  FROM `page`    WHERE page_namespace 
[01:02:46] <firespeaker>	 = 10 AND page_title = 'PAGENAME'  LIMIT 1
[01:03:11] <firespeaker>	 ack, sorry, thought that would paste as one line :(
[01:03:47] <firespeaker>	 but I get thousands of those lines
[01:04:51] <firespeaker>	 for the page that's not loading
[16:18:43] <firespeaker>	 so this page that's breaking things, I'm not sure how the debugging output is helpful
[16:19:02] <firespeaker>	 I just get thousands of SELECT queries
[16:19:20] <firespeaker>	 and this statement between them: [rdbms] Wikimedia\Rdbms\LoadBalancer::reuseOrOpenConnectionForNewRef: reusing connection for 0/wikidb
[16:19:55] <firespeaker>	 I wonder if the upgrade scripts did something weird to my database :(
[16:21:31] <firespeaker>	 the time taken for each query has doubled in the last 15 hours though...
[16:21:42] <firespeaker>	 maybe because the log file's so long...?
[16:24:50] <firespeaker>	 ah, looking at the exceptions log, there's two pages that seem to be running into this problem, not just one
[16:30:59] <firespeaker>	 here's the full log for when it times out: https://dpaste.org/g3S9N
[16:33:22] <firespeaker>	 the thousands of repeated queries seem to begin right after the PHP Deprecated traceback
[16:33:58] <firespeaker>	 maybe 1.43.0 isn't as future-proof as the LTS label suggests
[16:34:30] <moonmoon>	 the AccessControl extension is raising a compat issue, try disabling it and see if the problem goes away
[16:34:52] <firespeaker>	 ah indeed it is that extension
[16:34:56] <firespeaker>	 okay, lemme try
[16:35:28] <firespeaker>	 yep, works just fine now
[16:35:44] <firespeaker>	 okay so I'll file a bug against that extension
[16:36:01] <firespeaker>	 funny, I didn't use that extension at all in relation to the pages that are crashing
[16:38:27] <moonmoon>	 an extension like that needs to run on every page just to check if it is relevant
[16:40:28] <firespeaker>	 yeah, but it shouldn't do much else if its control sequences aren't matched...
[16:40:57] <firespeaker>	 I use a lot of non-Latin unicode on my wiki.... I wonder if there's something there it doesn't like
[16:41:43] <firespeaker>	 the pages it's crashing on would be particularly offensive to something that doesn't like non-Latin unicode :-P
[16:42:24] <moonmoon>	 MW supports unicode just fine (there are Wikipedias in most languages, even if many are quite sparse)
[16:43:21] <moonmoon>	 ultimately the extension choose a questionable means of operation (embedding metadata into a page) and then was never maintained/updated as the underlying MediaWiki APIs changed, so it kept bitrotting until the point it broke
[16:44:03] <moonmoon>	 the underlying page model has changed significantly since the time the extension was first written and I see zero commits in its history of it adapting to that
[16:44:54] <moonmoon>	 tbh I'd consider the ext unmaintained and find a replacement; I don't think a bug report against it is going to get resolved anytime soon (if ever). Probably still worth opening one though just so it's a known issue, so to speak
[16:46:43] <firespeaker>	 hah okay
[16:53:57] <moonmoon>	 what were you using the ext for? were you trying to lock down read access to pages, or just edit access?
[16:54:04] <firespeaker>	 read access
[16:54:56] <firespeaker>	 I was organising a project over a decade ago using the wiki (a project that never happened) and had names of people to contact about it listed
[16:55:12] <firespeaker>	 and I didn't want anyone scooping the project or the people to see their names associated with it before I contact them
[16:55:29] <firespeaker>	 so I should still probably find a way to read-restrict those pages again
[16:56:03] <firespeaker>	 issue filed, btw: https://phabricator.wikimedia.org/T383913 .  I hope that's sufficient
[17:00:52] <moonmoon>	 might just want to delete those pages then, if they're historical and no longer relevant
[17:02:51] <moonmoon>	 you can always view the deleted content as an admin should you need, or restore the pages later on if the project gets revived, but that lets you "kick the can" of access control down the road to when there are hopefully better options
[17:03:13] <firespeaker>	 yeah, was hoping there was some other hack I could do in the meantime
[17:03:20] <firespeaker>	 the word "delete" makes my stomach churn
[17:03:53] <firespeaker>	 I guess I could comment out the contents of the page—a little obfuscation would probably be plenty in this context
[17:23:55] <moonmoon>	 that could potentially work, although automated scrapers would still see it and possibly send spam
[17:24:30] <moonmoon>	 there's no real "hard-delete" in MediaWiki. Deleted revisions stick around and can be easily restored later
[19:29:59] <firespeaker>	 yeah, but the word still gives me the heebie-jeebies
[19:54:21] <Vulpix>	 editing those pages now will make them appear in recent changes. If someone is watching recent changes, it may trigger their curiosity and find out what you were trying to hide
[22:56:03] <firespeaker>	 Vulpix, true, good point