[08:50:40] Добрый день. У нас сайт на вашем движке. Последние 3 недели проблемы с поиском (поиск по сайту не работает). Можете подсказать в какой стороне искать ошибку? [10:18:15] ekaterina: Hi. What does "does not work" mean? Is there an error message? Which MediaWiki version are you using? [10:32:37] версия 1.30.0 [10:33:06] при поиске ошибка "Произошла ошибка при поиске: Нам не удалось завершить поиск из-за временной проблемы. Пожалуйста, повторите попытку позже." [11:11:12] Hmm, that is "We could not complete your search due to a temporary problem. Please try again later." which is vague, indeed [11:11:56] and https://www.mediawiki.org/wiki/Extension:CirrusSearch does not have any information for troubleshooting [11:12:04] maybe #wikimedia-discovery has ideas [11:13:12] ekaterina: have you installed elasticsearch? [11:13:58] да [11:14:57] ekaterina: if you have a shell access to this machine can you paste the output of : curl localhost:9200 [11:17:54] можно подробнее пожалуйста? [11:19:38] ekaterina: can run the command curl localhost:9200 on the machine running your MediaWiki installation? [11:20:12] it'll tell us if elasticsearch is running and if yes it'll tell the version you are running [11:23:43] 404 Not Found

404 Not Found

[11:24:41] в админке есть информация об установленной версии Elasticsearch 6.4.1 [11:25:53] ekaterina: MediaWiki 1.30 requires elasticsearch 5.3.x or 5.4.x, 6.4.1 is not supported [11:27:13] есть возможность откатить версию? [11:29:11] ekaterina: if this elasticsearch cluster you are currently using is used for something else (have some data installed) then I suggest keep you 6.4.1 version and install elastic 5.4.x somewhere else [11:29:36] if your elasticsearch server is empty (without any data) you can remove it and install 5.4.x [11:30:05] but this operation really depends on the operating system you are using [15:01:11] Technical Advice IRC meeting starting in 60 minutes in channel #wikimedia-tech, hosts: @Thiemo_WMDE & @chiborg - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [15:03:39] nice [15:29:05] Hello [15:29:42] I am hoping someone might be able to steer me in the right direction for the TreeAndMenu extension. [15:30:56] Is there anyone there? [15:34:14] Hello? [15:36:28] hi :( [15:38:16] Just like any video conference, except for "Hello" being replaced by "Can you hear me?"... [15:51:08] Technical Advice IRC meeting starting in 10 minutes in channel #wikimedia-tech, hosts: @Thiemo_WMDE & @chiborg - all questions welcome, more infos: https://www.mediawiki.org/wiki/Technical_Advice_IRC_Meeting [16:25:21] Hello! I would like to migrate a 1.24.1 install to a new machine. My intention is to follow the plan at https://www.mediawiki.org/wiki/Manual:Upgrading but it doesn't feel respectful to the old version I am using. Does anyone have any best practices or recommends for older versions? [16:26:39] Why do you think it's not "respectful" to the version you are using? [16:27:25] The general advice is back up your database, back up the files on disk, back up the whole vm/machine if it's feasible... [16:27:33] Depends what versions of PHP you're upgrading from too [16:27:44] Probably lack of overall knowledge, and a slight recollection of compatability issues on another site [16:28:11] PHP version is 5.4.15 [16:28:21] mysql is 5.6.11 [16:28:46] mysql version is fine. PHP version won't be [16:28:51] Are you upgrading the whole machine at the same time? [16:29:14] I'm migrating to a new instance. [16:29:41] I'm not trying to upgrade the machine. There are 5 instances of mediawiki running on one machine [16:29:50] Fair [16:30:00] I'm most likely going to run an RDS of MySQL for the individual databases [16:30:11] and then an EC2 instance for each of the sites [16:30:49] I see now that the upgrading page may be off for 'migration' [16:31:05] Should I try to just move under current versions and then upgrade? [16:31:33] You might have some issues running PHP7 (or newer) on MW that old, but it should mostly work [16:31:47] Doing two different upgrades in one go is definitely more complex, but shouldn't be too bad to sort [16:32:15] The good news is that I have 5 attempts to try (in that there are 5 instances) and the first attempt is with a wiki where only the main page ever changed [16:32:32] It's the least scary result set and will be done first [16:32:52] Just remember you ideally need to update skins/extensions too when you update MediaWiki [16:32:56] Thanks so much for chatting with me, first of all [16:33:09] I grabbed that information off the version page. [16:33:24] Composer is much more majorly used in MW 1.25 and above [16:33:33] Is it possible to do a new MediaWiki installation with latest versions and then import 1.24 data? [16:33:39] So you'll need to use/run composer to install some libraries and depndancies [16:33:50] I probably wouldn't suggest doing that [16:33:56] At least, not as far as actually running the MW installer [16:34:19] You can put the older database into place, then run the updater from newer MW and that should be fine [16:34:26] I see [16:34:40] Because there will be DB changes [16:34:47] does the older version of mediawiki have to be installed? would that be the correct order? [16:34:50] Nope [16:35:00] You can if you wanted, but shouldn't be necessary [16:35:04] 1. install php [16:35:10] 2. install mediawiki [16:35:20] or does mysql have to get in there first? [16:35:25] make sure you install the relevant php libraries too [16:35:26] and then switch to the old database [16:35:34] Depends what you mean by "install" mediawiki [16:35:40] can't install mediawiki without mysql to use [16:35:46] but you can stage the source code etc [16:36:09] I guess I'm not familiar with how to incorporate mediawiki [16:36:46] the good news is I can fail and start over pretty easily [16:36:52] with the EC2 instances [16:37:38] noob here, but probably is better to make a "clean" install and import your articles/images with main/import*.php [16:38:21] I'm not sure I'd agree [16:38:31] Especially if you've got access to the database [16:38:56] oh yeah, I forgot about those [16:39:04] *that [16:41:35] so, PHP latest with libraries on an EC2 instance, MySQL latest on RDS, MediaWiki install - File transfer? [16:42:14] if by mediawiki install you mean extracting a tarball, or cloning from git [16:42:51] I guess I do. This is my first foray into mw installs [16:42:56] good page for that? [16:43:25] https://www.mediawiki.org/wiki/Manual:Installing_MediaWiki#Download_MediaWiki_software [16:44:03] +1's all aroudn [16:44:26] Bare in mind if you're changing your mysql host (from localhost) [16:44:50] You'll want to update $wgDBserver to the new host/ip [16:45:05] okay [16:45:09] And potentially $wgDBuser, $wgDBpassword and $wgDBname in LocalSettings.php for each wiki [16:45:14] right on [16:45:20] especially with multiple instances [16:45:29] we have a shared config file [16:45:36] coming off the old machine [17:01:43] Should I consider XAMPP for installation if this is coming off of IIS 6? [17:02:56] or just separate installation of php against win2016 iis... [17:03:28] ooh, you're installing on windows? :) [17:04:04] I think it mostly depends what you're more comfortable supporting [17:04:06] Well, [17:04:17] I can't comment whether XAMPP is suitable for production [17:04:24] Yeah... [17:04:53] I don't have to use windows, but it felt like since it was coming there the propensity for file name differences (case sensitivity) existed [17:05:02] I'm perfectly fine installing on a linux box [17:05:49] Maybe my best bet is to just fire up the instance with linux and see how far I get. I feel bad asking "What Should I Do?" questions when I could be saying "Okay, this is what I did." [17:06:17] If you're foraying into the unknown, it's not a bad thing to ask some questions first [17:06:20] I guess the last question is whether it's smart to do a new mediawiki install on a linux box and try to get 1.24. data working [17:06:42] I don't think that's particularly necessary [17:06:53] If you were using a much older version of MW, it might be sensible (also doing some step upgrades) [17:07:03] okay, so it's not too archaic [17:07:13] Nope, it's old, but not old enough I'd be majorly busy [17:07:43] But the backup advice obviously if you were upgrading the machine makes a lot of sense [17:08:07] I've gotta pack up and leave to get to my parents for my little sisters birthday. Back around later tonight [17:08:20] so, my first attempt will be php 7 and libraries, mysql, mysqldump -> create database from 1.24 data, mwinstall [17:08:26] fantastic. No rush, and fun! [17:08:31] I appreciate your responses! [17:49:18] Hi all, my wiki is down… I think I should erase the DB and reinstall… Is there a way to get a backup, knowing that my wiki is crashed? [17:54:21] what do you mean by crashed? [17:56:20] giby: have you checked your server log what the problem is? [17:56:27] https://www.mediawiki.org/wiki/Manual:How_to_debug [17:58:22] andre__, As I told you, it is actually trying a code from this page that initiated the crash. I cannot get access to the log, nor can restart it. [18:01:30] giby: why can you not access the web server? [18:02:35] giby: Or in other words: How can you be an admin of a server if you cannot access the server? [18:02:36] It is a service hosted by a company, I can hardly get answer from them… [18:03:02] But how did you set up the wiki software on a server without having access to the server? [18:04:15] https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki#Database [18:05:07] I do not have a physical access, I get a FTP access [18:05:39] Do you have ssh access? [18:06:17] giby: If you have FTP access, update LocalSettings.php as per https://www.mediawiki.org/wiki/Manual:How_to_debug to see in the web browser what the problem is [18:06:30] I should, but… it does not work [18:07:21] ask OVH for support [18:07:24] giby: If FTP access still works, see the two links I provided for instructions how to either get a database backup or how to debug the problem. [18:07:32] you should have shell access [18:07:37] https://www.mediawiki.org/wiki/Manual:How_to_debug and https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki#Database [18:08:06] I asked them about it few days ago… [18:09:09] your ssh conn gets closed [18:10:00] do you have console access (not ssh)? [18:10:29] I have never seen it [18:10:53] what is your dashboard like? [18:11:13] are we talking about a VPS, right? [18:12:32] I gonna have a screenshot [18:13:41] psiconauta, https://www.dropbox.com/s/uvj3dx6rpdgkns9/Capture%20d%27%C3%A9cran%202018-12-12%2020.13.27.png?dl=0 [18:15:16] !shell [18:15:16] Shell access (that is, SSH access, see http://en.wikipedia.org/wiki/SSH) is highly recommended if you want to run MediaWiki. You can install without it, and basic operation will work, but even creating backups or upgrading will be painful without it. Some more involved maintenance tasks may even be impossible. MediaWiki is not designed for minimal environments. [18:15:23] giby: --^ [18:22:55] giby: If you have FTP access, is there a reason why you don't update LocalSettings.php as per https://www.mediawiki.org/wiki/Manual:How_to_debug to see in the web browser what the problem is? [18:23:46] andre__, I explained you that point many time! [18:24:13] giby: you did not. [18:24:30] you said you have ftp access. [18:24:50] you also said that ssh does not work. [18:24:51] I did it, it lead to a crash, I erased the given line, it did not do anything! [18:25:04] what is "it"? [18:25:33] which exact line? [18:26:07] I did add error_reporting( -1 ); and ini_set( 'display_errors', 1 ); it led to crash… I erased them, did not solve the crash [18:28:52] seems a webserver issue to me [18:29:07] apache, nginx whtv [18:30:13] if OVH support does not help, ask them for the webserver logs [18:30:56] or better... order a VPS (super cheap on OVH) [18:52:50] VPS? My friend google tells me it is a football club of Finland [18:55:11] giby: https://en.wikipedia.org/wiki/Virtual_private_server [18:55:29] Don't use Google, use Wikipedia... [18:59:09] andre__, well, I could: https://en.wikipedia.org/wiki/Vaasan_Palloseura [19:01:10] lol [19:01:29] dude, you are better of with a VPS [19:01:41] you have full access to it [20:20:17] I need help https://i.imgur.com/6ZkaTFM.png usin REL_32 [20:21:44] kreyren: the error message says "CREATE command denier to user …". looks like you are not allowed to create database tables [20:21:52] Permissions problem. [20:22:01] andre__: more info? [20:22:26] ah i see database is using user instead of admin. [20:22:31] thanks [20:22:31] you'll have to allow it in MySQL configuration (or ask whoever maintains your server to do it) [20:24:59] More issues: http://wiki.rixotstudio.cz/subdom/wiki/index.php [20:26:58] kreyren: it often looks like that when there is whitespace or other stuff before the re; "headers already sent" [20:27:15] checking [20:27:43] check the beginning of LocalSettings.php, first line [20:28:29] also it kind of sounded like your fix for the mysql permission issue was to use an admin user, dont :) [20:28:57] give the normal user the rights to do what it needs [20:29:05] noted will fix [20:29:33] There was warning above cool [20:30:55] ^^ [20:31:40] now install Vector, heh [20:31:47] or change the skin setting [20:32:43] if you installed by git cloning, then go next to https://www.mediawiki.org/wiki/Download_from_Git#Using_Git_to_download_MediaWiki_skins [20:32:53] to get Vector in the ./skinds/ dir [20:33:01] ./skins/ [20:35:10] ok resolving permission on database now. btw. is LocalSettings.php required in root? Since it has password in plain text [20:35:21] yes [20:35:46] Seems as security vulnerability o.o [20:35:51] you can have it require_once a file outside of your webroot and put passwords there, or you can just ensure that your file permissions on LocalSettings.php are correct [20:36:12] as long as your webserver is configured to run php files as php instead of spitting them out, there are no issues with it living in the webroot [20:36:49] noted [20:41:37] this is also why you want to use a user with enough permissions it needs but not an admin user that can access all other databases as well, it minimzes damage if it leaks [20:42:40] Even if i have one database for one wiki? [20:43:29] Also is there any article on hardening the mediawiki? [20:44:28] also it seems that anyone who has `/mw-config/index.php?page=Complete` can download LocalSettings.php with password in plain text? [20:44:48] keep up with updates, don't install extensions with known vulnerabilities or that have their code on a wiki page, don't hand out enhanced privs to people you don't trust [20:45:00] database connections for the user should be limited to the webserver host. And the database server properly firewalled [20:45:04] kreyren: no, all of that stuff is stored on cookies in your browser. Try clearing your cookies and trying that again [20:46:14] Skizzerz: Blocked cookies and wiki won't let me reset nor download the localsettings.ini thanks [20:47:12] Using: http://wiki.rixotstudio.cz/subdom/wiki/mw-config/index.php?localsettings=1 Seems to bypass the cookies? [20:48:05] It's a normal installation process. Without database credentials you can do nothing [20:48:05] what I was saying is that the username/password, etc. are stored in session storage, so *only you* were able to download that original LocalSettings file [20:48:22] it's not something anyone on the internet can grab, because they don't have the cookies you have [20:48:31] But feel free to restrict access to that folder once you've finished installation [20:49:02] once you upload LocalSettings.php to your server, mw-config is used to perform upgrades and requires the randomly-generated upgrade key present in your LocalSettings.php before it does anything [20:49:29] also, take a look at that php warning [20:49:42] I'm not sure what your disable_functions line is, but it probably has way too many things on it [20:49:48] Skizzerz: i've blocked the cookies and it seems to be able to reset the configuration. Reproducable on anonymous mode. [20:50:04] did you hit continue? [20:50:26] if no, try that [20:50:35] `our session data was lost! Check your php.ini and make sure session.save_path is set to an appropriate directory.` ah i see sorry [20:50:55] not just that [20:51:01] I'm also seeing Warning: putenv() has been disabled for security reasons in /data/web/virtuals/161195/virtual/www/subdom/wiki/includes/Setup.php on line 132 [20:51:24] anyway you have your php.ini overly restricted [20:51:30] `putenv()` is disabled by hosting it seems i was told that it doesn't affect wikimedia [20:51:33] your wiki probably isn't going to work until you loosen that up a bit [20:52:14] ok i'm going to request that on hosting. [20:52:36] you don't have access to php.ini yourself? [20:53:51] the putenv thing is ignorable (although you should turn off error_reporting in that case because a PHP warning at the top of every page isn't good for visitors and will break most skins) [20:53:59] I don't by default. I can request access to it. [20:54:16] but if putenv is restricted I can pretty much guarantee that there's other things in there that *are* required for mediawiki to function which are also restricted [20:54:39] meaning? [20:54:57] were you planning on enabling uploads and embedding pictures into pages? [20:55:03] yes [20:55:17] generating thumbnail images typically requires shell_exec() [20:55:40] hosting told me that putenv is disabled for security reasons (i'm on chat with them atm) [20:55:43] (although there's ways around that) [20:55:59] there is no good security reason to disable that [20:56:26] more info? Needs reasoning and i'm not aware what putenv does. [20:56:31] get a better host [20:56:37] that's my only response at this point in time [20:56:39] This is the best hosting in CZ :D [20:56:43] I doubt that [20:56:50] get a VPS [20:57:24] if "the application requires that the function be enabled" isn't good enough for them, then your host is shit [20:57:31] uneffective for this usecase, their webhosting is on stronger VPS, but is limited by default. [20:58:48] kreyren: ask them what the current list of disabled functions is and I'll tell you which of them mediawiki needs [20:59:18] asking [20:59:37] thanks for help btw. [21:01:16] https://hosting.wedos.com/cs/webhosting/php.html https://hosting.wedos.com/cs/webhosting/apache.html ware provided [21:01:34] en translate is available [21:01:51] https://hosting.wedos.com/en/webhosting/php.html https://hosting.wedos.com/en/webhosting/apache.html [21:02:03] which php version are you using? [21:02:10] 7.1.5 i believe [21:02:18] checking [21:05:55] http://wiki.rixotstudio.cz/info.php [21:06:11] 7.1.5 confirmed [21:07:13] any extension from the library PECL, XCache shared memory, ffmpeg, mencoder. are disabled by hosting [21:10:02] the following functions need to be enabled to enable various mediawiki features: putenv() is sometimes needed for proper support of non-English languages (I cannot identify the cases where it is required offhand), passthru() is required for the cleanupSpam.php maintenance script, proc_open() and related proc_* commands are required for image thumbnailing, automatic edit conflict resolution, obtaining information on git versions if using [21:10:03] git, and running Scribunto modules [21:10:18] and probably a handful of other things too [21:10:28] proc_open is the major one that'll block you from using a lot of mw features if it's off [21:12:08] lack of set_time_limit() will prevent you from running some maintenance scripts depending on server configuration [21:13:09] Noted requesting required features. [21:15:57] set_time_limit() doesn't seem to be disabled by hosting? [21:16:46] it is, check your info.php page [21:17:27] I don't see it where? [21:18:42] i see sry i'm blind xD [21:20:40] They will enable those functions tommorow thanks for info. [21:38:18] Gamepedia will now be part of Wikia :( http://community.wikia.com/wiki/User_blog:Brandon_Rhea/Fandom_and_Curse_Media_are_joining_forces [21:38:30] eww [21:40:22] tbh i can't imagine anime, gaming topics on wikipedia-like website o.o [21:43:22] gamepedia is massively popular and widely used for a lot of games [21:45:53] is gamepedia on mediawiki base? [21:45:55] yes [21:46:13] moreso than wikia is, at any rate [21:46:24] Seems heavily modified [21:46:43] Vulpix: I'm also not excited about how Wikia will mis-manage and kill off the non-wiki properties run by Curse, some of which I use quite a bit [21:50:54] Seems that wikia is webapp with native support for iOS and Android + has easier GUI.. Seems to me as selling point for gamers o.o [21:51:20] like gamers usually don't like much features.. [22:42:44] hi, anyone know any good wikicode linter? or something else that will fix the code with proper spaces and so on?