Topic on Project:Support desk

Setting up internal property indices ...
   ... space for internal properties already allocated.
   ... writing entries for internal properties ... done.
Internal properties initialized successfully.
...site_stats is populated...done.
...Update 'populate rev_len and ar_len' already logged as completed.
...Update 'populate rev_sha1' already logged as completed.
...img_sha1 column of image table already populated.
...protocol-relative URLs in externallinks table already fixed.
...fa_sha1 column of filearchive table already populated.
...*_from_namespace column of backlink tables already populated.
Failed to set the local repo temp zone container to be private.
Purging caches...done.

Why do I get this error: Failed to set the local repo temp zone container to be private

It is from here, but I failt to get the direction or file that is supposed to create the problem.

I have exactly the same error message when running update.php. any results on your efforts. mail to: jfoster81747@gmail.com

Basically, MediaWiki does a check on the temp/ folder inside your zone container. Usually that is the folder images/temp/. Inside that folder, MediaWiki might store sensitive data. That is why this folder should be protected by an .htaccess file. At the point where you get this error message, MediaWiki failed to create this file.

The .htaccess file, which should be created, contains two things: It disallows access to the folder (DENY) and it disallows displaying the Directory Listing.

Maybe someone can look up, what the content of this file should be! I guess the easiest solution might then be to manually create this file.

it creates an .htaccess with only this line:

Deny from all

Note that it will create it using the user account running the upgrade script. If you're running the web updater, the error shouldn't happen, and if it does, then the web server doesn't have permissions to write to that folder (which may result in errors when you upload a file). If you're running the update.php maintenance script, then it may fail because of the same (permissions for webserver, not for the user running the script).