[03:43:29] !rights [03:43:30] For information on customizing user access, see < http://www.mediawiki.org/wiki/Help:User_rights >. For common examples of restricting access using both rights and extensions, see < http://www.mediawiki.org/wiki/Manual:Preventing_access >. [05:10:59] Hi there. I'm looking for a little help getting my MediaWiki installed. I'm trying to install and run it off a Raspberry Pi 2 B+. [05:11:34] I'm being asked to enter a database host. What do I enter for what I'm trying to do? [05:17:42] localhost [05:18:11] and install mysql-server on the pi if you haven't already [05:18:58] Excellent. I think I already did install mysql-server but I'll double check after I finish installing Synaptic. [05:19:12] if entering localhost works, then you installed it [05:21:09] "DB connection error: Access denied for user 'root'@'localhost'(localhost) [05:21:22] you have to enter the correct password [05:21:33] For the pi? [05:21:39] for mysql [05:21:55] Fark. I'm not 100% sure I remember. [05:25:49] if worst comes to worst, you can wipe your data directory and start again [05:26:48] or disable authentication in my.cnf [05:26:49] Looks like it might come to that. Can I basically just uninstall and reinstall mysql? [05:27:14] you are using raspbian I assume? [05:27:22] Yeh. [05:28:53] here we go, https://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_skip-grant-tables [05:30:01] you can just put on its own line "skip_grant_tables" in /etc/mysql/my.cnf or whatever the file is called [05:30:09] Jaysus. Can I sudo apt-get purge and then reinstall as an alternative? [05:30:18] yes [05:30:18] Apologies, this is new ground for me. [05:30:24] make sure /var/lib/mysql is gone after you purge [05:30:25] Alright, I'll try that. [05:30:33] if not, just rm -rf [05:32:12] Hrm. In trying to remove it I accidentally opened it up with no password. Can I tell it to spit out or change the password? [05:33:19] It opened up to MariaDB [05:33:37] help password doesn't indicate a way to change or produce it. [05:34:31] passwords are hashed, but you can do "alter user root@localhost identified by '...';" [05:35:33] or possibly: set password for root@localhost = '...'; [05:35:36] depends on version [05:37:44] I'm just getting a text entry -> [05:37:51] Nothing I enter seems to do anything. [05:47:41] maybe you left out the semicolon or quote [05:52:45] Had the keyboard layout farked. It's asking for the password hash. [06:04:25] Alright. I have the password reset but now I'm getting "DB connection error: No such file or directory (localhost)" [06:05:50] maybe it is trying to connect with the unix socket (that's the default when you write the exact string "localhost"), but you broke it somehow [06:06:10] you could try 127.0.0.1 for the host instead [06:06:59] "Connection refuse" [06:07:02] *refused [06:07:33] the server is probably not running, that would explain both errors [06:08:28] msql isn't running? [06:09:16] try in a root shell: service mysql start [06:10:00] ps -C mysqld [06:10:54] PID 8674 TTY ? TIME 00:00:00 [06:12:17] so it is running now? can you install MW? [06:13:13] Arg wth, now it's rejecting the password again. I'm just going to flush mysql and reinstall [06:13:27] good idea [06:28:31] Ok, done, but it's still denying access. [14:52:12] Technical Advice IRC meeting in 10 minutes in channel #wikimedia-tech, hosts: @addshore & @Tobi_WMDE_SW - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [18:05:58] Does anybody know what "Has default::form" only works for pages and not for categories? [18:09:20] !hss [18:09:20] https://upload.wikimedia.org/wikipedia/mediawiki/6/69/Hesaidsemanticga2.jpg [18:11:17] for whom was that? [18:11:51] #semantic-mediawiki is just dead :/ [18:13:41] hmm [18:13:50] km@km-tp ~> curl -I "https://upload.wikimedia.org/wikipedia/mediawiki/6/69/Hesaidsemanticga2.jpg" | grep content-type [18:13:50] content-type: application/x-www-form-urlencoded [18:13:55] surely that's wrong [18:20:10] xD [18:20:20] what, swift is wrong? unpossible! [21:35:17] Question about maxlag. Why an higher maxlag is more aggressive? [21:45:43] it's not [21:46:54] amazing how we still keep that parameter at all [21:48:06] From Pywikibot, user-config.py: «Higher values are more aggressive in seeking access to the wiki.» [21:48:28] aha [21:48:41] From mw:Manual:Maxlag__parameter: «Higher values mean more aggressive behaviour, lower values are nicer.» [21:48:58] well, so aggressive is relative to who's being aggressive [21:48:59] :) [21:49:29] ? [21:50:03] so maxlag is maximum replication lag allowed [21:50:22] pywikibot aggressiveness against MediaWiki [21:50:58] depending on configuration, number of pending jobs can be used for lag purpose too [21:51:20] (converted to seconds using some magic hodgepodge) [21:51:46] if you set maxlag higher, that means the software will accept more edits when it's already under heavy replication load (vs rejecting them for the slaves lagging too much) [21:51:55] lag means database server is overloaded by writes [21:52:09] so your bot is more "aggressive" in the sense that it's contributing more to the load issue rather than backing off and being a "nice" citizen [21:52:34] so the higher maxlag you specify, the more you allow your bot to press on MediaWiki [21:52:41] that's what aggressive means [21:52:49] I don't understand. Replica slave can have a certain sync lag to the master. That is the lag. Right? [21:52:55] yes [21:52:58] So, [21:53:11] say, a master can write to a replica at rate X edits per second [21:53:11] and ideally, this lag should be under one second [21:53:29] So a slave with an high lag, means that is not much precious as slave, because it's not in sync. Right? [21:53:39] not so simple, there's no easy formula for that [21:53:41] if you make Y edits in a short amount of time (where "you" means "all editors combined"), where Y > X, then you're editing faster than it can sync to slaves, causing a backlog/lag [21:53:57] it's more nuanced than that [21:54:06] but it works as a general idea [21:54:25] So, working with machines with high lag, means that you will enlarge that lag, and it's not good. Right? [21:55:02] anomie, why do we still support maxlag, even? this feels like an implementation detail that doesn't make sense for us to expose these days [21:55:39] yes, so "aggressive" means bot being aggressive to the site [21:56:20] force good bots to throttle while bad bots take down the site! [21:56:54] however, if you look at things from MW's perspective, "aggressive" is what nice bots do to restrict themselves to low lag:) [21:57:25] Vulpix: yes! what could possibly go wrong? [21:57:39] Vulpix, good bots forcing the ops to ban the bad bots :P [22:08:15] ...:) I thought that slave with high lag were "less precious" than slaves with low lag, so I thought that setting an higher maxlag would meant that I would prefere working on less precious slaves that are out of sync. :P [22:08:44] (sorry for bad en) Now it's clear. [22:10:30] valerio-bozzolan: you don't write to slaves, you only read from slaves. [22:10:40] writes always go to the master [22:12:09] (That it's clear, but I thought that accessing through the API to a slave not in sync was good, because slaves in sync were more precious and so have to be preserved for human beings.) [22:12:32] (That was no much sense, now it's clear.) [22:12:35] I doubt the maxlag parameter even does anything for reads [22:16:57] Skizzerz, actually, it does: https://en.wikipedia.org/w/api.php?action=query&meta=siteinfo&maxlag=-1 [22:17:04] Yep [22:21:34] MaxSem: interesting; I wonder why [22:22:22] (probably "it's easier and more consistent that way") [22:22:25] because API module defaults are that it needs maxlag [22:22:35] which kinda doesn't make sense :P [22:55:04] Skizzerz, https://phabricator.wikimedia.org/T176373