Project:Support desk

Jump to navigation Jump to search

About this board

Welcome to's Support desk, where you can ask MediaWiki questions!

There are also other places where to ask :

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
    • MediaWiki
    • PHP
    • Database
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new topic".
Previous page history was archived for backup purposes at Project:Support_desk/old on 2015-07-30.
Other languages: English  العربية čeština Esperanto français 日本語 中文
Tofiq Kərimli (talkcontribs)

Commons files do not appear on my wiki . Previously displayed, but after upgrading the Server Commons Files are not displayed. What can i do? Thank you in advance.

Reply to "Image from commons not displaying"

"Error creating thumbnail: Error code: 2"

16 (talkcontribs)


I recently moved my MediaWiki from one server to another. Everything seems to work well except thumbnail generation: I receive "Error creating thumbnail: Error code: 2"

I have reviewed and tried the various documented online solutions without success. My LocalSettings.php is

$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";

I can confirm that ImageMagick is installed (version 6.7.7-10) and the convert command path works when I try it from the Mediawiki directory prompt. . MediaWiki is looking into the right place for images (full images upload and display fine). I temporarily changed permissions to 777 on /images and on /images/temp just to see if that solved a problem. It didn't. I tried specifying

$wgMaxShellMemory = 512 000; 
$wgMaxShellFileSize = unlimited;

But that didn't solve the problem. I tried specifying the /images/temp directory with $wgTmpDirectory = "$IP/images/temp"; but that didn't solve the problem either. For kicks I tried using /etc/alternatives/convert but that didn't work either. I logged out of the wiki after each change and 'hard' refreshed my browser just to make sure that I was looking at the new settings effects. My MediaWiki is in /var/www/html/wikiname. It is version 1.23.2.

Convinced that imagemagick isn't being called or exiting properly I followed the links and got:

me@star:/usr/bin$ ls -l /usr/bin/convert
lrwxrwxrwx 1 root root 25 Nov  3 17:39 /usr/bin/convert -> /etc/alternatives/convert
me@star:/usr/bin$ ls -l /etc/alternatives/convert
lrwxrwxrwx 1 root root 20 Nov  3 17:39 /etc/alternatives/convert -> /usr/bin/convert.im6
me@star:/usr/bin$ ls -l /usr/bin/convert.im6
-rwxr-xr-x 1 root root 6320 Mar  6  2014 /usr/bin/convert.im6
me@star:/usr/bin$ dpkg -S /usr/bin/convert.im6
imagemagick: /usr/bin/convert.im6

I tried changing the LocalSettings command path to /usr/bin/convert/im6 but it didn't help. I'm out of troubleshooting ideas. Any suggestions?

Ciencia Al Poder (talkcontribs)

You say you have this:

$wgMaxShellMemory = 512 000; 
$wgMaxShellFileSize = unlimited;

But Manual:$wgMaxShellFileSize doesn't mention "unlimited" as a valid value, and also I think "512 000" is not a valid number in PHP. It should generate a parse error. Could you please verify that? (talkcontribs)

G'day, I was following ( suggestion and similar posts elsewhere reporting that this solved their similar problem even when no memory limitation was expected. I did not receive a parser error in MediWiki responses, looking in ~/apache2/error I don't see one, but I also commented out this trial after it did not resolve the problem.

This, that and the other (talkcontribs)

The fact that you didn't get a parser error with that invalid code suggests that your LocalSettings.php file is being ignored altogether... (talkcontribs)

Thanks, but not true. Chances are good that I'm not looking in the right place for a parser error that doesn't report in the MediaWiki. LocalSettings.php is the effective configuration file because if I set #wgEnableUploads = false; then my MediaWiki doesn't allow uploads. I've sequentially tried these fixes, but either it's a 'more than one variable problem' or something else is causing an abnormal exit from ImageMagick. From the active LocalSettings.php

## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";
#$wgSVGConverterPath = "/usr/bin";
#$wgImageMagickTempDir = "IP$/images/temp";
#$wgMaxShellMemory = 300000;
#$wgMaxShellFileSize = 300000;
#$wgMaxShellTime = 220;
#$wgTmpDirectory = "/var/www/html/wikiname/images/temp";
#$wgUseImageReseize = true;
#$wgGenerateThumbnailOnParse = true;
##$wgSVGConverterPath = "/usr/bin";
#$wgTmpDirectory = "$IP/images/temp"; (talkcontribs)

I should have mentioned:

  • MediaWiki 1.23.2
  • PHP 5.5.9-1ubuntu4.5 (apache2handler)
  • MySQL 5.5.40-0ubuntu0.14.04.1
This, that and the other (talkcontribs)

From reading the MW source code (includes/media/Bitmap.php, line 180 or thereabouts, if you're interested), it seems that your invocation of ImageMagick is returning the error code "2".

You could try enabling the debug log: Manual:How_to_debug#Setting_up_a_debug_log_file

The log will contain lines like "transformImageMagick: running ImageMagick: " followed by the exact command line being issued by MediaWiki. You should try running this command manually (at a shell on your server) and see what happens.

In the debug log you may also see lines containing "thumbnail failed on", which may point you closer to the source of the problem. (talkcontribs)

Thank you, that was a helpful suggestion. I made the log file and this is the relevant portion of the log:

File::transform: Doing stat for mwstore://local-backend/local-thumb/9/93/How_Did_you_Hear_About_2014.png/120px-How_Did_you_Hear_About_2014.png FileBackendStore::getFileStat: File mwstore://local-backend/local-thumb/9/93/How_Did_you_Hear_About_2014.png/120px-How_Did_you_Hear_About_2014.png does not exist. BitmapHandler::doTransform: creating 120x68 thumbnail at /tmp/transform_79944211ec2f-1.png using scaler im BitmapHandler::doTransform: called wfMkdirParents(/tmp) BitmapHandler::transformImageMagick: running ImageMagick: '/usr/bin/convert' '-quality' '95' '-background' 'white' '/var/www/html/wikiname/images/9/93/How_Did_you_Hear_About_2014.png' '-thumbnail' '120x68!' '-set' 'comment' 'File source: http://intentionallyremoved/wikiname//index.php/File:How_Did_you_Hear_About_2014.png' '-depth' '8' '-rotate' '-0' '/tmp/transform_79944211ec2f-1.png' wfShellExec: /bin/bash '/var/www/html/wikiname/includes/' 'OMP_NUM_THREADS='\''1'\'' '\''/usr/bin/convert'\'' '\''-quality'\'' '\''95'\'' '\''-background'\'' '\''white'\'' '\''/var/www/html/wikiname/images/9/93/How_Did_you_Hear_About_2014.png'\'' '\''-thumbnail'\'' '\''120x68!'\'' '\''-set'\'' '\''comment'\'' '\''File source: http:// intentionallyremoved /wikiname//index.php/File:How_Did_you_Hear_About_2014.png'\'' '\''-depth'\'' '\''8'\'' '\''-rotate'\'' '\''-0'\'' '\''/tmp/transform_79944211ec2f-1.png'\''' 'MW_INCLUDE_STDERR=1;MW_CPU_LIMIT=180; MW_CGROUP='\'''\''; MW_MEM_LIMIT=307200; MW_FILE_SIZE_LIMIT=102400; MW_WALL_CLOCK_LIMIT=180; MW_USE_LOG_PIPE=yes'[thumbnail] thumbnail failed on star: error 2 "" from "'/usr/bin/convert' '-quality' '95' '-background' 'white' '/var/www/html/wikiname/images/9/93/How_Did_you_Hear_About_2014.png' '-thumbnail' '120x68!' '-set' 'comment' 'File source: http:// intentionallyremoved /wikiname//index.php/File:How_Did_you_Hear_About_2014.png' '-depth' '8' '-rotate' '-0' '/tmp/transform_79944211ec2f-1.png'" [thumbnail] Removing bad 0-byte thumbnail "/tmp/transform_79944211ec2f-1.png". unlink() succeeded User::getBlockedStatus: checking... ForeignAPIRepo: HTTP GET: LoadBalancer::reuseConnection: this connection was not opened as a foreign connection [runJobs] Running 1 job(s) via '/wikiname//index.php?title=Special%3ARunJobs&tasks=jobs&maxjobs=1&sigexpiry=1416866196&signature=e8ce801451b14a3d680b953c8d298293fdffbfeb'

I then tried to run the command as you suggested:

me@place:/var/www/html/wikiname/images$ /usr/bin/convert -quality 95 /var/www/html/wikiname/images/9/93/How_Did_you_Hear_About_2014.png -thumbnail 120x68! /var/www/html/wikiname/images/9/93/bpthumb.png convert: unable to open image `/var/www/html/wikiname/images/9/93/bpthumb.png': Permission denied @ error/blob.c/OpenBlob/2638. convert: WriteBlob Failed `/var/www/html/wikiname/images/9/93/bpthumb.png' @ error/png.c/MagickPNGErrorHandler/1728. me@place:/var/www/html/wikiname/images$

Helpful! So I then changed the permsions of ~/images and all subdirectories so that then MediaWiki user www-data has drwxr-xr-x I was then able to execute the code without an error and thumbnail file was correctly built as I can see when I downloaded it via ftp, but the MediaWiki still give me the same error code 2 and doesn't' produce thumbnails for the images (in say new files special page). I simplified the MediaWiki command to:

/usr/bin/convert -quality 95 -background white /var/www/html/wikiname/images/9/93/How_Did_you_Hear_About_2014.png -thumbnail 120x68! -depth 8 -rotate -0 /var/www/html/wikiname/images/9/93/transform_bp4.png

And I got:

convert: unable to open image `/var/www/html/wikiname/images/9/93/transform_bp4.png': Permission denied @ error/blob.c/OpenBlob/2638. convert: WriteBlob Failed `/var/www/html/wikiname/images/9/93/transform_bp4.png' @ error/png.c/MagickPNGErrorHandler/1728.

So I suspect a permissions error, but I get the same error even when I set the ~/images/9 and ~/9/93 to drwxrwxr-x

This, that and the other (talkcontribs)

Note that the original ImageMagick command seems to be trying to write to your /tmp directory. Try checking the permissions on that directory! Or try running the original ImageMagick command exactly, complete with the output filename in /tmp, and see what messages you get. (talkcontribs)

Thanks. the /tmp directory is drwxrwxrwt. I think it should be open. By setting permissions to 777 I was able to execute the imagemagick line manually. I'm beginning to suspect that the problem is ownership or group membership or something? Most of my directions in ~/wikiname are like

drwxr-xr-x 8 me UNIVERSITY\domain^users 4096 Nov 11 16:17 extensions

but images is

drwxr-xr-x 22 me www-data 4096 Nov 11 16:17 images

because I changed ownership as advised here ( All the subdirectories under images are

drwxr-xr-x 16 me www-data 4096 Nov 24 12:54 9

Is this a problematic permissions configuration maybe?

This, that and the other (talkcontribs)

Unfortunately I know very little about Unix permissions, being a Windows person myself. At least in Windows you get a nice user interface to manage permissions! On Linux-based boxes it seems very confusing.

My only suggestion would be to carefully check what user the server or PHP processes are running under, and make sure they have the correct permissions. Or if you try setting the relevant directories' permissions to 777 (temporarily of course), and everything then works, it is evidently a problem of certain users not having the right permissions on the right directories. Keep checking the MediaWiki debug log for information.

Ciencia Al Poder (talkcontribs)

Confusing? unix permissions are very simple ;)

Try what TTO suggested (777 permissions), and if that also fails, the problem might be that you have some sort of security program blocking "unexpected" file creations. The most common problem is SELinux. Try disabling it.

Ciencia Al Poder (talkcontribs)

Note that every line starting with a "#" character in LocalSettings.php is ignored, since it's a PHP comment.

Note that $wgImageMagickTempDir = "IP$/images/temp"; should be $wgImageMagickTempDir = "$IP/images/temp"; instead. And the value of $wgSVGConverterPath doesn't make sense. Still, all of those configuration variables are commented out, so they aren't being used in your installation. (talkcontribs)

Yes, thank you. I understand the commenting syntax. I was just illustrating my history of trying one fix at a time.

Sergezolotukhin (talkcontribs)

In my case, I had bash error '\r': command not found when running includes/ (this script is using for running convert). So it's easy to fix it with removing trailing \r character that causes this error:

sed -i 's/\r$//' includes/

.digamma (talkcontribs)

Just upgraded to 1.33.0 and this (sed command on my includes/shell/ ^^^ fixed it for me.

Reply to ""Error creating thumbnail: Error code: 2""

You are missing a required extension to PHP that MediaWiki requires to run.

FriFraCologne (talkcontribs)

I get the following error message:

You are missing a required extension to PHP that MediaWiki requires to run. Please install:

mbstring (more information)

fileinfo (more information)s

Both extensions are enabled in my php ini, the extension directory is correct and the dll's are there.

Any sugestions?

Malyacko (talkcontribs)

Which PHP version? Which MediaWiki version?

Ciencia Al Poder (talkcontribs)

Maybe you need to restart apache/IIS after enabling them in php.ini

Kellyincuse (talkcontribs)

Did this ever get resolved? I just kicked up a new MW 1.32 server running PHP 7.3.1 ... I've tested PHP and Apache to make sure they are configured to run tests ... the MW Index.PHP runs and I get the same two extensions listed above as required. In my php.ini file I have the following two lines ...



and I have checked the variable for the 'ext' folder where the DLLs are located.

I've setup two othe WIKI servers using MW but these two extensions weren't required then but they are now.

Any suggestions?

Ciencia Al Poder (talkcontribs)

Create a php file with a phpinfo call to see what extensions are really enabled, as explained in Manual:Php.ini (talkcontribs)

I've had the same issue since upgrading to 1.32. (running php 7.3.2-1). When I run the update.php script i get the following:

Error: Missing one or more required components of PHP.

You are missing a required extension to PHP that MediaWiki needs.

Please install:

* mbstring <>

I have mbstring installed and enabled in php.ini. Any suggestions?

Manishkaujalgi (talkcontribs)


I had the similar issue (requires extention --> mbstring) when running on EC2 - AMI Linux..

Running this resolved my error:

sudo yum install php70-mbstring.x86_64 php70-zip.x86_64 -y

Remember to restart your apache after that

Ciencia Al Poder (talkcontribs)

Are you sure the phpinfo php script displays mbstring as being enabled? (talkcontribs)

I have the same message. mbstring is definitely enabled in php.ini but it's not showing up in the phpinfo.php. I have restarted all already several times. I have installed

- Apache 2.4.39 (win64 VS16)

- PHP 7.3.8

- MySQL Server 8.0.17

Pyton 3.7.4

- MediaWiki 1.27

Any idea what I am doing wrong?

Thank you

Ciencia Al Poder (talkcontribs)

The php.ini you're editing is not the php.ini being used by the server

The ouptupt of phpinfo tells you what php.ini files are being loaded. (talkcontribs)

I get the same problem, only with iconv rather than mbstring. When I navigate to /localhost/mediawiki/index.php, I see the following:

You are missing a required extension to PHP that MediaWiki requires to run. Please install: iconv

I uncommented the iconv module in /usr/share/php/modules and it still says it's not installed.

Here's my setup:

PHP 7.3.8

Apache2 2.4.39

Linux 4.19.66 (Manjaro; problem also on Arch Linux)

MariaDB 10.4.7

Mediawiki any version > 1.31.1

(i.e., 1.31.1 was the last time it worked; i've been downgrading to it for the last few months to keep it running)

Any suggestions ? (talkcontribs)

Did you restart apache after enabling the module? (talkcontribs)

Yes. And to clarify the above: i uncommented iconv and mbstring in the main php config file, /etc/php/php.ini. Then I checked /usr/share/php/modules and found that iconv is there, with the correct permissions. No idea why wiki can't find it.

Ciencia Al Poder (talkcontribs)

Please check the output of phpinfo (information in Manual:php.ini) to see if PHP knows about that php extension installed. This is not MediaWiki not knowing about the extension, but php

Reply to "You are missing a required extension to PHP that MediaWiki requires to run."

Importing text files subtly - edit.php

Summary by AhmadF.Cheema

Through using the --no-rc flag.

Beardedfool (talkcontribs)

I've previously had text files injected into the system through edit.php, but it ends of showing all the edits is recent changes, which masks other people's normal edits.

I'd like some advice of the best way to get around this please, as I can see a few ways to explore.

1) Perhaps I'm just not understanding the recent changes filters and there's some way to exclude these edits, perhaps with a specific user?

2) Use a bot?

3) Iframe from another site - not ideal

4) Setup a whole new wiki and transclude from there?

Many thanks

AhmadF.Cheema (talkcontribs)

The Edit.php has the --no-rc flag to "not show the change in recent changes". Doesn't that work?🤔

Beardedfool (talkcontribs)

Missed that, thank you!!!

From a slightly embarrassed but grateful person.

How can I set closed wiki to open at LocalSettings.php?

Parkyh1974 (talkcontribs)

I've set up mediawiki using Docker image by kristophjunge.

It is successful. but the setup was for closed users. I want to change it to open

as default wiki. But there is no set up for my old LocalSettings.php and docked image's

LocalSettings.php .

How can I change it to be open wiki?

Ciencia Al Poder (talkcontribs)

You probably have this setting in your LocalSettings.php (from, Manual:Preventing access#Simple private wiki)

# Disable reading by anonymous users
$wgGroupPermissions['*']['read'] = false;
# Disable anonymous editing
$wgGroupPermissions['*']['edit'] = false;
# Prevent new user registrations except by sysops
$wgGroupPermissions['*']['createaccount'] = false;

You can simply remove or comment-out those lines.

Error - VirtualRESTService for the document server is not defined

Smokinjo67 (talkcontribs)

I have installed Visual Editor

Upon clicking the edit button to load the document, I get a pop up window saying :

I asked the visual editor help group, and they said that since it seems to be related to RESTBase, that maybe the general support desk might be able to help.

The error is:

Error loading data from server: no_vrs: The VirtualRESTService for the document server is not defined; see Would you like to retry?

I did find one reference to this error. It was in reference to SELINUX:

This error occurs usually on CENTOS 6 / 7 servers running SELINUX. In order to resolve this problem please disable SELINUX

I am running this on Debian 9

Can some one point me in the right direction as to why I am getting this, and possible a solution?

Thanks for your help


MarkAHershberger (talkcontribs)
Smokinjo67 (talkcontribs)


I do not have this variable in my config.

Is this something that should be i the LocalSettings file by default? Or, it needs to be added?



MarkAHershberger (talkcontribs)

You will need to add it.

Misterms735 (talkcontribs)


$wgVirtualRestConfig['modules']['parsoid'] = array(

  // URL to the Parsoid instance

      // Use port 8142 if you use the Debian package

      'url' => 'http://localhost:8142',

      // Parsoid "domain", see below (optional)

      'domain' => 'localhost',

      // Parsoid "prefix", see below (optional)

      'prefix' => 'localhost'


I have added this line, and now the error shows up like this: Error loading data from server: apierror-visualeditor-docserver-http: HTTP 404

Smokinjo67 (talkcontribs)

OK, Misterms got an error. But, you said it needs to be added. What do I add? The lonk you showed has 3 examples of the config:

$wgVirtualRestConfig = [
	'modules' => [],
	'global' => [
		# Timeout in seconds
		'timeout' => 360,
		# 'domain' is set to $wgCanonicalServer in Setup.php since MediaWiki 1.26
		'forwardCookies' => false,
		'HTTPProxy' => null,


These are the default values when Parsoid is registered as a REST service, used when some keys are not defined.

$wgVirtualRestConfig['modules']['parsoid'] = [
	// URL to the Parsoid instance - use port 8142 if you use the Debian package - the parameter 'URL' was first used but is now deprecated (string)
	'url' => 'http://localhost:8000/',
	// Parsoid "domain" (string, optional) - MediaWiki >= 1.26
	'domain' => 'localhost',
	// Parsoid "prefix" (string, optional) - deprecated since MediaWiki 1.26, use 'domain'
	'prefix' => 'localhost',
	// Forward cookies in the case of private wikis (string or false, optional)
	'forwardCookies' => false,
	// request timeout in seconds (integer or null, optional)
	'timeout' => null,
	// Parsoid HTTP proxy (string or null, optional)
	'HTTPProxy' => null,
	// whether to parse URL as if they were meant for RESTBase (boolean or null, optional)
	'restbaseCompat' => null,


These are the default values when a RESTBase service is registered, used when some keys are not defined.

$wgVirtualRestConfig['modules']['restbase'] = [
	// RESTBase server URL (string)
	'url' => 'http://localhost:7231/',
	// Wiki domain to use (string)
	'domain' => 'localhost',
	// request timeout in seconds (integer or null, optional)
	'timeout' => 100,
	// cookies to forward to RESTBase/Parsoid (string or false, optional)
	'forwardCookies' => false,
	// HTTP proxy to use (string or null, optional)
	'HTTPProxy' => null,
	// whether to parse URL as if they were meant for Parsoid (boolean, optional)
	'parsoidCompat' => false,
	// whether to append the domain to the url
	'fixedUrl' => false,
Which one do I use (or a mix of them all?), and are there things to config for my server?

Misterm used another variation as well. What does a newbie mediawiki guy to do/use?


MarkAHershberger (talkcontribs)

Use the parsoid one and and adjust the ports and things to your needs.

Misterms735 (talkcontribs)
MarkAHershberger (talkcontribs)

@Misterms735 404 probably means you have the server and port set up incorrectly. What port is parsoid set up to listen on?

Smokinjo67 (talkcontribs)

Thanks for the suggestion.

Since oru server uses Debian, who should use port 8142 here, right:

'url' => 'http://localhost:8000/',

Because I am using the latest version of mediawiki (1.3.x), I keep it at localhost, right?

// Forward cookies in the case of private wikis (string or false, optional)

How does this apply? Private meaning like internal for a company? Ours will eb visible, but not editable by the general public. Need an approved account to edit

// request timeout in seconds (integer or null, optional) 'timeout' => null,

What is this for?

// whether to append the domain to the url 'fixedUrl' => false,

What is this for?



MarkAHershberger (talkcontribs)

@Smokinjo67: In order:

who should use port 8142
I keep it at localhost
How does this apply? Private meaning like internal for a company? Ours will eb visible, but not editable by the general public. Need an approved account to edit
I've always forwarded cookies on my wikis.
What is this for?
Don't worry about these until you run into problems.
Misterms735 (talkcontribs)
Smokinjo67 (talkcontribs)

So, for the forward cookies, I put "true"?


MarkAHershberger (talkcontribs)


Smokinjo67 (talkcontribs)

I finally had the time to work on this. I added the code and the comnfig we spoke of.

I got the following error:

Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?

What might this mean?



Reply to "Error - VirtualRESTService for the document server is not defined"

When I try using mobile frontend extension, it shows 500 internal error.

Parkyh1974 (talkcontribs)

I've set up mediawiki using docker image at

It is using Mediawiki 1.30 AND PHP7.0

When I load extension by

# VisualEditor


at LocalSettings.php, it shows 500 error.

Is there any lead to solve this?

Thank you.

AhmadF.Cheema (talkcontribs)

The 500 error indicates an issue with the server. Did you check your server error logs?

Parkyh1974 (talkcontribs)

I've checked nginx log files but there is no record. Is there any other log I need to check?

Reply to "When I try using mobile frontend extension, it shows 500 internal error."

Templates largely broken after 1.30 -> 1.33

Scarred Sun (talkcontribs)

I performed an upgrade from 1.30 to 1.33 and as a result seem to have lost a lot of content from the Template namespace from rendering properly; for example, looking at you'll see that many of the templates which support the page are outright broken. How do I recover these?

Reply to "Templates largely broken after 1.30 -> 1.33"

Update script fails with error: DBReadOnlyError

Summary by .digamma

Another support ticket indicated ReadOnly mode is a problem for the update script. Users can be forced into ReadOnly mode while the scripts continues with write access using code from the reply posted here: Support desk Ticket Response

After enabling write access, script ran to completion with no reported errors. Checking upgrade now...

.digamma (talkcontribs)

During the update from 1.25 -> 1.33 I receive the following output:

[24b9ca57e08535368cd8bf8f] [no req]   Wikimedia\Rdbms\DBReadOnlyError from line 1042 of /w/includes/libs/rdbms/database/Database.php: Database is read-only: This wiki is currently being upgraded to a newer software version. Please check back in a couple of days.


#0 /w/includes/libs/rdbms/database/Database.php(1205): Wikimedia\Rdbms\Database->assertIsWritableMaster()

#1 /w/includes/installer/MysqlUpdater.php(907): Wikimedia\Rdbms\Database->query(string, string)

#2 /w/includes/installer/DatabaseUpdater.php(489): MysqlUpdater->doPageRandomUpdate()

#3 /w/includes/installer/DatabaseUpdater.php(453): DatabaseUpdater->runUpdates(array, boolean)

#4 /w/maintenance/update.php(205): DatabaseUpdater->doUpdates(array)

#5 /w/maintenance/doMaintenance.php(96): UpdateMediaWiki->execute()

#6 /w/maintenance/update.php(268): require_once(string)

#7 {main}

Do I need to remove the read-only block from LocalSettings during the update?

Thank you!

Error message after upgrade from 1.25 -> 1.33

Summary by .digamma

Database query error from index.php. Update.php ran silently. Non-existent table during update -> update.php couldn't login to database to create necessary tables.

.digamma (talkcontribs)

I worked through the instructions found here: Manual:Upgrading and performed the recommended backup as described. I ran the update.php command (in fact twice) and it completed very quickly with no output in the ssh PuTTY console. I'm using PHP 7.3, but the Wiki runs on 7.0, and MySQL database version 5.7.23-23

When I visit the main page of the wiki, I get this error:

[X14OUEd0TyMB3I8DpNhbgAAAA8] 2019-09-14 23:31:06: Fatal exception of type Wikimedia\Rdbms\DBQueryError

[XX2T2UvxMo5akr5-@9w1WAAAAA8] /w/ Wikimedia\Rdbms\DBQueryError from line 1587 of /home4/w/includes/libs/rdbms/database/Database.php: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading?

Query: SELECT rev_id,rev_page,rev_timestamp,rev_minor_edit,rev_deleted,rev_len,rev_parent_id,rev_sha1,comment_rev_comment.comment_text AS `rev_comment_text`,comment_rev_comment.comment_data AS `rev_comment_data`,comment_rev_comment.comment_id AS `rev_comment_cid`,actor_rev_user.actor_user AS `rev_user`,actor_rev_user.actor_name AS `rev_user_text`,temp_rev_user.revactor_actor AS `rev_actor`,page_namespace,page_title,page_id,page_latest,page_is_redirect,page_len,user_name FROM `wiki_revision` JOIN `wiki_revision_comment_temp` `temp_rev_comment` ON ((temp_rev_comment.revcomment_rev = rev_id)) JOIN `wiki_comment` `comment_rev_comment` ON ((comment_rev_comment.comment_id = temp_rev_comment.revcomment_comment_id)) JOIN `wiki_revision_actor_temp` `temp_rev_user` ON ((temp_rev_user.revactor_rev = rev_id)) JOIN `wiki_actor` `actor_rev_user` ON ((actor_rev_user.actor_id = temp_rev_user.revactor_actor)) JOIN `wiki_page` ON ((page_id = rev_page)) LEFT JOIN `wiki_user` ON ((actor_rev_user.actor_user != 0) AND (user_id = actor_rev_user.actor_user)) WHERE page_is_redirect = '0' AND page_namespace = '8' AND (page_title NOT LIKE '%/%' ESCAPE '`' ) AND (page_len <= 10000) AND (page_latest = rev_id)

Function: MessageCache::loadFromDB(en)-small

Error: 1146 Table 'wikidb.wiki_revision_comment_temp' doesn't exist (localhost)


#0 /home4/w/includes/libs/rdbms/database/Database.php(1556): Wikimedia\Rdbms\Database->getQueryExceptionAndLog(string, integer, string, string)

#1 /home4/w/includes/libs/rdbms/database/Database.php(1274): Wikimedia\Rdbms\Database->reportQueryError(string, integer, string, string, boolean)

#2 /home4/w/includes/libs/rdbms/database/Database.php(1784): Wikimedia\Rdbms\Database->query(string, string)

#3 /home4/w/includes/cache/MessageCache.php(549): Wikimedia\Rdbms\Database->select(array, array, array, string, array, array)

#4 /home4/w/includes/cache/MessageCache.php(441): MessageCache->loadFromDB(string, NULL)

#5 /home4/w/includes/cache/MessageCache.php(364): MessageCache->loadFromDBWithLock(string, array, NULL)

#6 /home4/w/includes/cache/MessageCache.php(1051): MessageCache->load(string)

#7 /home4/w/includes/cache/MessageCache.php(978): MessageCache->getMsgFromNamespace(string, string)

#8 /home4/w/includes/cache/MessageCache.php(948): MessageCache->getMessageForLang(LanguageEn, string, boolean, array)

#9 /home4/w/includes/cache/MessageCache.php(890): MessageCache->getMessageFromFallbackChain(LanguageEn, string, boolean)

#10 /home4/w/includes/Message.php(1308): MessageCache->get(string, boolean, LanguageEn)

#11 /home4/w/includes/Message.php(863): Message->fetchMessage()

#12 /home4/w/includes/Message.php(955): Message->toString(string)

#13 /home4/w/includes/Title.php(633): Message->text()

#14 /home4/w/includes/MediaWiki.php(120): Title::newMainPage()

#15 /home4/w/includes/MediaWiki.php(140): MediaWiki->parseTitle()

#16 /home4/w/includes/MediaWiki.php(781): MediaWiki->getTitle()

#17 /home4/w/includes/MediaWiki.php(515): MediaWiki->main()

#18 /home4/w/index.php(42): MediaWiki->run()

#19 {main}

Where can I find the log file for the update.php process?

I appreciate any help.


AhmadF.Cheema (talkcontribs)

Did you upgrade your extensions too? Faulty extensions can also cause update.php to not work, temporarily disable all extensions and try update.php again.

.digamma (talkcontribs)

Same error. Update.php exits quickly. The wiki_bot_passwords table isn't there either, added in 1.27.

I solved this error. I added display errors to the top of the update.php script and discovered the script was unable to find the login credentials for the database. After fixing this, the script ran.