[02:35:22] <Esther>	 Hi!
[02:38:37] <d3r1ck>	 Esther: Hi
[09:32:23] <praisethemoon>	 Hello
[13:39:17] <lmat>	 I'm having trouble with my wikimedia installation. I got it installed, using mysql. When I click "edit" on the home page, I get
[13:39:22] <lmat>	 A database query error has occurred. This may indicate a bug in the software.[cef81f30b605b028026a471e] 2017-08-23 12:12:02: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"
[13:39:33] <lmat>	 Oh yeah, I'm serving with httpd. Nothing is logged about this in /var/log/httpd/error_log.
[13:39:48] <lmat>	 Other things work: for instance "protecting" that home page...
[13:39:59] <lmat>	 view history works on this page, and it shows that I protected it.
[13:43:06] <lmat>	 Oh yeah, I logged into mysql as the mediawiki user, and successfully selected from some tables there. I suppose this is a needless test because installation succeeded, and it's serving content.
[13:49:54] <Esther>	 !debug
[13:49:54] <goat-bot>	 For information on debugging (including viewing errors), see https://mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging Also see https://mediawiki.org/wiki/Manual:Errors_and_symptoms
[13:49:59] <Esther>	 lmat: ^
[13:55:14] <lmat>	 Great, thanks
[14:27:48] <MichaelSchoenitz>	 Technical Advice IRC meeting starting at 3 pm UTC/5 pm MEZ in channel #wikimedia-tech, hosts: @addshore & @CFisch_WMDE - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting
[14:47:04] <lmat>	 Esther: Thanks! I'm looking at "Creating custom error logs". Without doing that, where do debug logs go? Where is the default?
[14:47:47] <andre__>	 debug log for what exactly?
[14:48:11] <andre__>	 for example, if your web server does not like something, it depends on your web server's configuration.
[14:48:17] <andre__>	 not much to generalize...
[14:48:18] <lmat>	 andre__: DB.  $wgDBerrorLog = '/var/log/mediawiki/dberror.log';    If I don't set that, what is the default?
[14:48:45] <Reedy>	 /dev/null
[14:48:46] <bawolff>	 lmat: if you don't set a generic debug log, then they go nowhere (as in they aren't stored)
[14:48:46] <andre__>	 /dev/null ? :P no idea, sorry
[14:48:55] <lmat>	 :-o
[14:49:04] <lmat>	 Well then, I'll set up logging
[14:49:49] <bawolff>	 Debug logging really is for debugging. The logs aren't all that useful if you're not trying to fix something, and they will get very large if you just have them enabled on your wiki all the time
[14:50:12] <lmat>	 bawolff: I see. Yes, I have an error (see above)
[14:50:45] <bawolff>	 oh, you don't want debug logging for that
[14:50:49] <Reedy>	 Yeah
[14:50:56] <lmat>	 oh
[14:50:57] <Reedy>	 You just need to enable it to print more stuff out to the web
[14:51:03] <Reedy>	 So you get full errors
[14:51:18] <lmat>	 Reedy: I think I did that... I did   wgShowSQLErrors, wgDebugDumpSql and wgShowDBErrorBacktrace
[14:51:29] <Reedy>	 That... should be enough
[14:51:32] <bawolff>	 Just set: $wgShowSQLErrors = true; $wgShowDBErrorBacktrace = true; $wgShowExceptionDetails=true;
[14:51:35] <bawolff>	 jinx
[14:51:47] <lmat>	 doesn't say anything else:    A database query error has occurred. This may indicate a bug in the software.[bb04e6c7d3024118edb6b0dc] 2017-08-23 14:47:30: Fatal exception of type "Wikimedia\Rdbms\DBQueryError"
[14:52:06] <Reedy>	 $wgShowExceptionDetails = true;
[14:52:07] <Reedy>	 That one too
[14:52:23] <bawolff>	 We have a rediciulous number of variables controlling if sql errors are shown
[14:52:45] <lmat>	 Reedy: HEY! That one gave data...looking
[14:53:10] <lmat>	 table doesn't exist.   "A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?"
[14:53:17] <Reedy>	 well, did you?
[14:53:28] <lmat>	 I don't know how to "run" a "schema"...
[14:53:35] <Reedy>	 !update
[14:53:35] <goat-bot>	 update.php is a script that updates the database tables. You usually need to run it after upgrading MediaWiki or installing certain extensions. For details, see <http://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script>
[14:53:43] <lmat>	 By the way, the missing table is from an extension!
[14:53:55] <Reedy>	 answer should still be the same
[14:54:01] <lmat>	 aye.
[14:54:10] <lmat>	 does "run a schema" mean "run update.php"?
[14:54:22] <bawolff>	 Weird that the "did you forget..." isn't shown by default
[14:54:36] <bawolff>	 where do you see run a schema?
[14:54:57] <bawolff>	 "application's database schema updater" means update.php
[14:55:23] <bawolff>	 I don't know why we don't just say update.php in that message. Its kind of a silly wording
[14:55:39] <Reedy>	 !fixit
[14:55:39] <goat-bot>	 There is no such key, you probably want to try: !sofixit, 
[14:55:47] <lmat>	 bawolff: It's nonsensical actually.
[14:56:28] <bawolff>	 lmat: Not really, its grammatically correct and has all the right words
[14:56:46] <bawolff>	 Its just going to be confusing to the target audiance
[14:56:58] <lmat>	 bawolff: :-) Yes, grammatically, it's correct. If "run a schema" means anything, I think it would mean "make sure the database daemon is on", right?
[14:57:20] <Reedy>	 With sqlite... That doesn't make sense either :P
[14:57:25] <lmat>	 bawolff: That reminds me of my friend who was a non-programmer. He asked me how he could "hook up the API"...
[14:57:29] <lmat>	 Reedy: yeah ;-)
[14:58:04] <bawolff>	 Its saying run a schema updater, not run a schema
[14:59:03] <bawolff>	 I don't see why it doesn't make sense for sqlite - sqlite is less strict than traditional dbs when it comes to schemata, but it still has the same concept
[14:59:15] <Reedy>	 https://gerrit.wikimedia.org/r/373302
[14:59:17] <Reedy>	 bike shedding time
[14:59:29] <bawolff>	 lol
[15:00:30] <lmat>	 bawolff: Oh goodness. I misread it. Sorry!
[15:00:56] <lmat>	 bawolff: That makes much more sense. Then my question would be: "Where is the schema updater?" which is much more serviceable. oof
[15:01:10] <bawolff>	 I guess the only other question is whether to mention the web installer as an option, but maybe that's too much info in the error
[15:01:13] <bawolff>	 that sounds good
[15:01:48] <lmat>	 Reedy: Hey, that's pretty good!
[15:02:12] <Reedy>	 Or maybe we just add that bit in brackets or something
[15:02:32] <bawolff>	 Already +2'd. Its too late :P
[15:02:38] <Reedy>	 lol
[15:03:50] <lmat>	 Reedy: Perhaps a link to https://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script ?
[15:03:55] <lmat>	 oh, too late :-P
[15:04:03] <Reedy>	 Well, we can make more patches
[15:04:09] <Reedy>	 I think a plain text link might work...
[15:04:15] <Reedy>	 But we can't guarantee it's HTML
[15:04:21] <Reedy>	 As I think shell can barf with that too
[15:05:14] <lmat>	 nice. "abort with control-C" I aborted so I could read the message, then ran again.
[15:05:17] <lmat>	 Oh, Done in 6.6s
[15:06:03] <lmat>	 EDIT WORKS! \o/
[15:06:10] <lmat>	 This wiki is going to change the world...
[15:06:21] <Reedy>	 It's gonna be yuge
[15:06:26] <Reedy>	 You WILL love it.
[15:06:40] <lmat>	 ;-)
[15:08:03] <Reedy>	 bawolff: MatmaRex just said no
[15:08:47] <bawolff>	 MatmaRex raining on our parade ;)
[15:09:02] <MatmaRex>	 sorry D:
[15:09:22] <Reedy>	 It makes sense, to the extent it should have MW specific stuff
[15:09:31] <bawolff>	 I didn't even thing about the whole /libs thing
[15:09:31] <Reedy>	 But MW core needs a way to override that message... Or append to it
[15:09:37] <Reedy>	 Obviously we can't use MW hooks
[15:10:12] <MatmaRex>	 "Maybe we could have some special handling in MWExceptionRenderer to specifically mention update.php?"
[15:10:19] <Reedy>	 Mmm
[15:10:58] <Reedy>	 I guess a task never got filed for it
[15:11:25] <lmat>	 MatmaRex: Yeah, that
[15:13:44] <Reedy>	 https://phabricator.wikimedia.org/T173946
[15:13:48] <bawolff>	 oh, we are already doing this for DBConnectionError
[15:13:54] <bawolff>	 so it should be straight forward
[15:35:03] <bewbs>	 block and nuke shows hte same userlist every time even after i blocked and nuked them?
[15:35:20] <bewbs>	 that doesn't make sense
[15:46:21] <bewbs>	 if blockandnuke unintentionally blocks a user, how do i unblock them
[15:47:26] <bewbs>	 and blockandnuke didn't do anything...
[15:47:28] <bawolff>	 bewbs: Special:Unblock should work
[15:48:21] <bewbs>	 cna i see a list of blocked user/ip's
[15:49:17] <bewbs>	 i'm thinking lbockandnuke isn't working for me 
[15:50:02] <bewbs>	 when i click blockandnuke it has a list of users. i click the button athte bottom and it comes up with a list of pages and ip's. when i click block and nuke, it just spins
[15:53:22] <bawolff>	 Special:listblocks
[16:59:45] <lmat>	 How do I test e-mail capability on my server?
[17:00:06] <lmat>	 It never had me set up a SMTP host...does it have a good default?
[17:02:24] <andre__>	 errm, you create two users and try to send an email to yourself? :P
[17:02:32] <andre__>	 what do you mean?
[17:02:51] <lmat>	 andre__: Yeah, that.
[17:03:06] <lmat>	 andre__: How does one "send an email to yourself?"?
[17:03:47] <andre__>	 You register two users, at least one with a valid email address, and then log in as one user and use "Email the user" to the user that has registered a valid email address.
[17:03:50] <andre__>	 I think.
[17:04:49] <lmat>	 andre__: "Email the user" is that something one can do within mediawiki?
[17:04:55] <andre__>	 yeah
[17:05:02] <lmat>	 andre__: http://lmat.info.tm/LibrEd  
[17:05:04] <andre__>	 or what email functionality are you after actually?
[17:05:57] <lmat>	 andre__: Nothing in particular, I just want to make sure it's properly configured
[17:06:23] <lmat>	 So that if an e-mail comes, I'll get it :-)
[23:22:19] <Esther>	 lmat is discovering MediaWiki!