Last modified: 2010-05-15 15:56:39 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 5786 - Installation fail on Initialising "MediaWiki" namespace...
Installation fail on Initialising "MediaWiki" namespace...
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.6.x
Other Linux
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 5465 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-02 08:31 UTC by Gabriel
Modified: 2010-05-15 15:56 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Gabriel 2006-05-02 08:31:37 UTC
After set all the parameters it start, create the database in MySql ... then
stop after 30 sec on the message of 'Namspace ...'

    * PHP 5.1.2-1ubuntu2 installed
    * PHP server API is cgi-fcgi; using ugly URLs (index.php?title=Page_Title)
    * Have XML / Latin1-UTF-8 conversion support.
    * PHP's memory_limit is 20M. If this is too low, installation may fail!
    * Have zlib support; enabling output compression.
    * Neither Turck MMCache nor eAccelerator are installed, can't use object
caching functions
    * Found GNU diff3: /usr/bin/diff3.
    * Found ImageMagick: /usr/bin/convert; image thumbnailing will be enabled if
you enable uploads.
    * Found GD graphics library built-in.
    * Installation directory: /var/www/MediaWiki
    * Script URI path: /MediaWiki
    * Environment checked. You can install MediaWiki.

      Generating configuration file...
    * Database type: mysql
    * Attempting to connect to database server as root...success.
    * Connected to 5.0.19-Debian_3-log
    * Created database wikidb
    * Creating tables... using MySQL 4 table defs... done.
    * Initializing data...
    * User wikiDB exists. Skipping grants.
    * Created sysop account WikiAdmin.
    *

      Initialising "MediaWiki" namespace...


#####################
PHP.ini
#####################
;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 3000     ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing
request data
memory_limit = 20M      ; Maximum amount of memory a script may consume (8MB)
Comment 1 andre mandler 2006-05-03 21:57:44 UTC
i encountered the same problem and bugs 5465 and 3842 seem to be of the same
ilk, and unresolved, too.
i'm trying this on the server of a professional hoster, freenet.com, its running
php 5.0.4 on a nonspecified linux server, and it has a sql database.
everything works fine, then netscape says the page is 'done' (e.g. completely
loaded) and nothing happens anymore, i waited for some ten minutes. trying
again, the script comes up with the info that all the pages already existed...
and stalls at the same point, the namespace initialisation.
before anybody suggests any running of occult scripts, let it be known that i'm
quite a newbee, so just 'run xyz' won't be sufficent, i have to know where to
put what file and then say what to whom in which environment (i do all the ftp -
stuff by windows commander, and otherwise interact via netscape browser over the
index.php, more i don't know about)
the log:
    * PHP 5.0.4 installed
    *
      Warning: PHP's register_globals option is enabled. Disable it if you can.
      MediaWiki will work, but your server is more exposed to PHP-based security
vulnerabilities.
    * PHP server API is cgi; using ugly URLs (index.php?title=Page_Title)
    * Have XML / Latin1-UTF-8 conversion support.
    * PHP is configured with no memory_limit.
    * Have zlib support; enabling output compression.
    * Neither Turck MMCache nor eAccelerator are installed, can't use object
caching functions
    * GNU diff3 not found.
    * Found GD graphics library built-in, image thumbnailing will be enabled if
you enable uploads.
    * Installation directory: /web/wiki
    * Script URI path: /wiki
    * Environment checked. You can install MediaWiki.
    * Warning: $wgSecretKey key is insecure, generated with mt_rand(). Consider
changing it manually.

      Generating configuration file...
    * Database type: mysql
    * Attempting to connect to database server as U225326AA...success.
    * Connected to 4.1.10a-standard-log
    * Database U225326AA exists
    * Creating tables... using MySQL 4 table defs... done.
    * Initializing data...
    * Created sysop account loonquawl.
    *

Initialising "MediaWiki" namespace...

Comment 2 Martin ZPC 2006-06-15 08:18:04 UTC
I have the same problem:

    * PHP 4.4.1 installed
    *
      Warning: PHP's register_globals option is enabled. Disable it if you can.
      MediaWiki will work, but your server is more exposed to PHP-based security
vulnerabilities.
    * PHP server API is apache2handler; ok, using pretty URLs (index.php/Page_Title)
    * Have XML / Latin1-UTF-8 conversion support.
    * PHP's memory_limit is 8M. If this is too low, installation may fail!
Attempting to raise limit to 20M... ok.
    * Have zlib support; enabling output compression.
    * Neither Turck MMCache nor eAccelerator are installed, can't use object
caching functions
    * GNU diff3 not found.
    * Found GD graphics library built-in, image thumbnailing will be enabled if
you enable uploads.
    * Installation directory: /home/www/xxxxxx.cz/www/wiki.xxxxxx.cz
    * Script URI path:
    * Environment checked. You can install MediaWiki.
    * Warning: $wgSecretKey key is insecure, generated with mt_rand(). Consider
changing it manually.

      Generating configuration file...
    * Database type: mysql
    * PHP is linked with old MySQL client libraries. If you are using a MySQL
4.1 server and have problems connecting to the database, see
http://dev.mysql.com/doc/mysql/en/old-client.html for help.
    * Attempting to connect to database server as xxxxxx01...success.
    * Connected to 4.0.27-log
    * Database xxxxxx01 exists
    * Creating tables... using MySQL 4 table defs... done.
    * Initializing data...
    * Created sysop account XXXX.
    *

      Initialising "MediaWiki" namespace...
Comment 3 Simon Hollingshead 2006-08-15 21:38:19 UTC
i get the same:

Checking environment...

Please include all of the lines below when reporting installation problems.


      Warning: set_time_limit() has been disabled for security reasons in
/home/www/<XXX>/wiki/install-utils.inc on line 29
    * PHP 4.4.1 installed
    *
      Warning: PHP's register_globals option is enabled. Disable it if you can.
      MediaWiki will work, but your server is more exposed to PHP-based security
vulnerabilities.
    * PHP server API is cgi-fcgi; using ugly URLs (index.php?title=Page_Title)
    * Have XML / Latin1-UTF-8 conversion support.
    * PHP's memory_limit is 16M. If this is too low, installation may fail!
Attempting to raise limit to 20M... ok.
    * Have zlib support; enabling output compression.
    * Neither Turck MMCache nor eAccelerator are installed, can't use object
caching functions
    * GNU diff3 not found.
    * Found GD graphics library built-in, image thumbnailing will be enabled if
you enable uploads.
    * Installation directory: /home/www/<XXX>/wiki
    * Script URI path: /wiki
    * Environment checked. You can install MediaWiki.

      Generating configuration file...
    * Database type: mysql
    * PHP is linked with old MySQL client libraries. If you are using a MySQL
4.1 server and have problems connecting to the database, see
http://dev.mysql.com/doc/mysql/en/old-client.html for help.
    * Attempting to connect to database server as bhaikido_wiki...success.
    * Connected to 4.1.18-log; You are using MySQL 4.1 server, but PHP is linked
to old client libraries; if you have trouble with authentication, see
http://dev.mysql.com/doc/mysql/en/old-client.html for help.
    * Database bhaikido_wiki exists
    * Creating tables... using MySQL 4 table defs... done.
    * Initializing data...
    * Created sysop account <XXX>.
    *

      Initialising "MediaWiki" namespace...
 
and it stops.  When you look in the source, it shows it has terminated because
the line has no close tag:

<li>Initializing data...<li>Created sysop account <tt>NOT SAYING</tt>.</li>
<li><pre>Initialising "MediaWiki" namespace...
--END--
No close tag or a <body> or <html>
Comment 4 Simon Hollingshead 2006-08-15 21:58:45 UTC
*** Bug 5465 has been marked as a duplicate of this bug. ***
Comment 5 Simon Hollingshead 2006-08-16 01:47:20 UTC
With all the duplicates I am surprised na answer has yet been found.  This bug
is a problem as my site needs the wiki.
Comment 6 Rob Church 2006-08-16 02:45:57 UTC
Could affected users check the PHP error logs to find out what's causing the
suspension? No answer has been provided because there's insufficient debugging
information, and no-one's had a chance to attempt to reproduce it.
Comment 7 Simon Hollingshead 2006-08-16 16:13:37 UTC
I did not do anything except attempt to install it by opening the config file
after putting them all in one directory.  I can reproduce the bug just by
uploading it again.
Comment 8 Simon Hollingshead 2006-08-16 16:50:06 UTC
just to let you know i cant run newest 1.6 or 1.5

stops at same place.
Comment 9 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-08-16 18:38:39 UTC
Quote:

> Could affected users check the PHP error logs to find out what's causing the
> suspension? No answer has been provided because there's insufficient debugging
> information, and no-one's had a chance to attempt to reproduce it.

Do your error logs show anything?
Comment 10 Simon Hollingshead 2006-08-16 18:50:18 UTC
i dont have an error log as i run it on a remote hosting server.
Comment 11 Zachary Vance 2006-08-16 23:53:20 UTC
My logs don't show any errors.
Comment 12 Simon Hollingshead 2006-08-18 23:18:56 UTC
so what could it be?
Comment 13 Tim Starling 2006-11-19 04:06:38 UTC
The problem is probably just that the script is reaching PHP's
max_execution_time. The simplest workaround is to skip initialiseMessages(), the
wiki should work just fine without it. Open maintenace/InitialiseMessages.inc.
After this:

  function initialiseMessages( $overwrite = false, $messageArray = false,
$outputCallback = false ) {

Add the line:

  return;

As for a long-term solution, I've been thinking about various ways to make
initialiseMessages() very fast, such as using a text storage class that stores
its text in a single concatenated blob, or simply refers to the language files. 

Another option would be to do away with initialisation altogether, and to
instead to pre-fill the edit box on article creation.
Comment 14 Zachary Vance 2006-11-19 04:13:13 UTC
No, my execution times were ridiculously high.

I can't recall, but I think I maybe got the new version working at some point?
I'm not even running a server now (University uses private IPs) and I'm using a
different OS, so it would be difficult for me to keep the same conditions while
checking.
Comment 15 Tim Starling 2006-11-19 04:27:41 UTC
Right, ridiculously high. So the solution is to make it faster. I don't care if
it was max_execution_time, the idle timeout in MySQL, an HTTP proxy or your
browser that eventually put a stop to it, the solution is the same. We just had
a report on IRC of the same problem, and that guy checked here for a solution
before he went to IRC. So it's useful to have a workaround documented. If you're
not experiencing the bug anymore, then take yourself off the CC list.
Comment 16 Rob Church 2006-11-19 12:08:07 UTC
(In reply to comment #13)
> Another option would be to do away with initialisation altogether, and to
> instead to pre-fill the edit box on article creation.

Don't we do that already for the MediaWiki namespace?

Comment 17 Rob Church 2007-04-02 07:52:50 UTC
As of 1.9.0, we no longer populate the MediaWiki namespace, so this issue should
disappear from the radar.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links