i'm tryng to install mediwiki on a free hosting machine, so no support is provided from them. I whatn to know if there is a way to intall it with php safe mode active and memory limit set to 10M.
here is the output of the installation:
MediaWiki 1.7.1 Installation
- *Don't forget security updates!* Keep an eye on the low-traffic release announcements mailing listhttp://mail.wikimedia.org/mailman/listinfo/mediawiki-announce.
Checking environment...
*Please include all of the lines below when reporting installation problems. *
- PHP 5.1.4 installed - Found database drivers for: MySQL - *Warning:* *PHP's safe mode http://www.php.net/features.safe-modeis active. * You may have problems caused by this, particularly if using image uploads. - PHP server API is apache; ok, using pretty URLs (index.php /Page_Title) - Have XML / Latin1-UTF-8 conversion support. - PHP's memory_limit is 10M. *If this is too low, installation may fail!* Attempting to raise limit to 20M... failed. - Have zlib support; enabling output compression. - Neither Turck MMCache http://turck-mmcache.sourceforge.net/ nor eAccelerator http://eaccelerator.sourceforge.net/ nor APChttp://www.php.net/apcare 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: /storage0/home/roavia.evonet.ro/www - 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 - Loading class: DatabaseMysql - Attempting to connect to database server as roavia_04...success. - Connected to 5.0.22; enabling MySQL 4.1/5.0 charset mode - Database roavia_04 exists - There are already MediaWiki tables in this database. Checking if updates are needed...
...hitcounter table already exists. ...querycache table already exists. ...objectcache table already exists. ...categorylinks table already exists. ...logging table already exists. ...user_newtalk table already exists. ...transcache table already exists. ...trackbacks table already exists. ...externallinks table already exists. ...job table already exists. ...langlinks table already exists. ...querycache_info table already exists. ...filearchive table already exists. ...have ipb_id field in ipblocks table. ...have ipb_expiry field in ipblocks table. ...have rc_type field in recentchanges table. ...have rc_ip field in recentchanges table. ...have rc_id field in recentchanges table. ...have rc_patrolled field in recentchanges table. ...have user_real_name field in user table. ...have user_token field in user table. ...have user_email_token field in user table. ...have user_registration field in user table. ...have log_params field in logging table. ...have ar_rev_id field in archive table. ...have ar_text_id field in archive table. ...have page_len field in page table. ...have rev_deleted field in revision table. ...have img_width field in image table. ...have img_metadata field in image table. ...have img_media_type field in image table. ...have ss_total_pages field in site_stats table. ...have iw_trans field in interwiki table. ...have ipb_range_start field in ipblocks table. ...have ss_images field in site_stats table. ...already have interwiki table ...indexes seem up to 20031107 standards Already have pagelinks; skipping old links table updates. ...image primary key already set. The watchlist table is already set up for email notification. ...watchlist talk page rows already present ...user table does not contain old email authentication field. Logging table has correct title encoding. ...page table already exists. revision timestamp indexes already up to 2005-03-13 ...rev_text_id already in place. ...page_namespace is already a full int (int(11)). ...ar_namespace is already a full int (int(11)). ...rc_namespace is already a full int (int(11)). ...wl_namespace is already a full int (int(11)). ...qc_namespace is already a full int (int(11)). ...log_namespace is already a full int (int(11)). ...already have pagelinks table. ...templatelinks table already exists No img_type field in image table; Good. Already have unique user_name index. ...user_groups table already exists. ...user_groups is in current format. ...wl_notificationtimestamp is already nullable. ...timestamp key on logging already exists. Setting page_random to a random value on rows where it equals 0...changed 0 rows Initialising "MediaWiki" namespace...
*Fatal error*: Allowed memory size of 10485760 bytes exhausted (tried to allocate 85 bytes) in */storage0/home/roavia.evonet.ro/www/includes/Title.php* on line *135*
On 7/10/06, Ioan Suciu roavia@gmail.com wrote:
i'm tryng to install mediwiki on a free hosting machine, so no support is provided from them. I whatn to know if there is a way to intall it with php safe mode active and memory limit set to 10M.
here is the output of the installation:
MediaWiki 1.7.1 Installation
...
- PHP's memory_limit is 10M. *If this is too low, installation may
fail!* Attempting to raise limit to 20M... failed.
...
*Fatal error*: Allowed memory size of 10485760 bytes exhausted (tried to allocate 85 bytes) in */storage0/home/roavia.evonet.ro/www/includes/Title.php* on line *135*
As you noted, the problem is the 10M limit on PHP. Unless you can raise it, it's not going to work.
Whether or not you can actually raise is going to depend on how php is set up on the server. If it's running php as a cgi, then I think you can have a local php.ini file. Alternately, you might be able to use the php_ini function in LocalSettings.php or somewhere else to raise it:
http://www.phpfreaks.com/tutorials/10/0.php
But this is based on googling, others with more php knowledge might have other ways or clarifications.
As you noted, the problem is the 10M limit on PHP. Unless you can raise it, it's not going to work.
Whether or not you can actually raise is going to depend on how php is set up on the server. If it's running php as a cgi, then I think you can have a local php.ini file. Alternately, you might be able to use the php_ini function in LocalSettings.php or somewhere else to raise it:
I have no acces to php.ini and is a free web hosting service without support or costum config.
I' will try to configure on other linux machine and then to copy all includin the sql to that server.
10X for help
IS
On 7/10/06, Ioan Suciu roavia@gmail.com wrote:
As you noted, the problem is the 10M limit on PHP. Unless you can raise it, it's not going to work.
I have no acces to php.ini and is a free web hosting service without support or costum config.
Here's a couple things you can try:
1. Put this into LocalSettings.php... not sure which file you would want to put this into when trying to setup the Wiki for the first time... DefaultSettings.php maybe?:
ini_set( 'memory_limit', '20M' );
2. Put this into .htaccess in the root of the wiki install:
php_flag memory_limit 20M
Dan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dan Davis wrote:
- Put this into LocalSettings.php... not sure which file you would
want to put this into when trying to setup the Wiki for the first time... DefaultSettings.php maybe?:
I think the installer already tried it:
PHP's memory_limit is 10M. *If this is too low, installation may fail!* Attempting to raise limit to 20M... failed.
- -- #define Name RotemLiss #define Mail mailSTRUDELrotemlissDOTcom #define Site www.rotemliss.com
#define KeyFingerPrint 4AFD 8579 A449 4267 BED9 38E5 6EF8 5B1F EBDE 7AC0
On 7/11/06, Rotem Liss mail@rotemliss.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dan Davis wrote:
- Put this into LocalSettings.php... not sure which file you would
want to put this into when trying to setup the Wiki for the first time... DefaultSettings.php maybe?:
I think the installer already tried it:
PHP's memory_limit is 10M. *If this is too low, installation may fail!* Attempting to raise limit to 20M... failed.
Well, it tried and failed. The question is why. There are several reasons I can think of including:
1) It didn't have the permissions to write the file, quite likely since the OP says he's running on a free hosting machine which probably has the config locked down to one extent or another.
2) php.ini wasn't in the place(s) which the installer expected. Some distros move things around for various reasons.
As I posted earlier, it looks like there are various ways to set the memory_limit depending on how php is configured, but I'm not enough of a php expert to know the details.
mediawiki-l@lists.wikimedia.org