Problem With MediaWiki Script Installer

8 posts / 0 new
Last post
#1 Tue, 12/15/2009 - 03:53
dtwyman

Problem With MediaWiki Script Installer

Hi,

I have setup a sever template to install MediaWiki on server creation and the MediaWiki installer fails. I get the following:

Installing mediawiki version 1.15.1 .. Configuring Apache PHP settings .. .. already done.

Creating MySQL database progressfundraising_mediawiki .. .. done .. options problem detected : Missing wiki option

Is there a log somewhere that will tell me what 'options' problem was detected?

Thanks.

Tue, 12/15/2009 - 08:27
andreychek

Hrm, I've never heard of that error before :-)

You may want to take a peek in /var/webmin/miniserv.error to see if anything shows up in there.

If not, you can always file a support request using the Support link above.

-Eric

Tue, 12/15/2009 - 08:44 (Reply to #2)
dtwyman

Hi, I’m seeing a lot of this:

chgrp: cannot access /var/lib/mysql/progressfundraising_phpbb': No such file or directory chmod: cannot access/var/lib/mysql/progressfundraising_phpbb': No such file or directory chgrp: cannot access /var/lib/mysql/progressfundraising_roundcube': No such file or directory chmod: cannot access/var/lib/mysql/progressfundraising_roundcube': No such file or directory chgrp: cannot access /var/lib/mysql/progressfundraising_mediawiki': No such file or directory chmod: cannot access/var/lib/mysql/progressfundraising_mediawiki': No such file or directory chgrp: cannot access /var/lib/mysql/progressfundraising_phpmyadmin': No such file or directory chmod: cannot access/var/lib/mysql/progressfundraising_phpmyadmin': No such file or directory chgrp: cannot access /var/lib/mysql/progressfundraising_wordpress': No such file or directory chmod: cannot access/var/lib/mysql/progressfundraising_wordpress': No such file or directory

I moved the MySQL data directory to the home partition (/home/mysql/). I’m assuming that the MySQL data directory is hardcoded in the scripts?? Is there some place I can change it in the scripts?

I guess I can work around that my just creating a symbolic link from /var/lib/mysql to /home/mysql but I guess I would rather update in some configuration screen somewhere.

FYI: I using Virtualmin GPL upgraded to Pro on EC2 and need the databases off the instance partition. So, I attached an EBS volume at /home. Trying to take advantage of the reserved instance pricing in case your wondering why I didn’t go with the paid AMI for Virtualmin Pro.

Thanks.

Tue, 12/15/2009 - 09:02 (Reply to #3)
andreychek

Hmm... I don't think these issues are related.

What you're seeing above is because Virtualmin tries to change the permissions on the databases after creating them, so that they'll be included in the user quotas.

Virtualmin doesn't attempt to directly access the data in them or anything. So long as MySQL knows where it's databases are, you should be okay in that department.

Not that this solves your problem at all, it just seems like the above errors probably aren't the issue :-)

Now, to correct the above errors, if you take a look in Webmin -> Servers -> MySQL -> Module Config -> System Configuration, is the "Path to MySQL databases directory" setting correct?

-Eric

Tue, 12/15/2009 - 08:47
dtwyman

Hi,

Just remembered - I'm using the 'bleeding edge' repository as I need PHP 5.2 for some scripts.

Dan

Tue, 12/15/2009 - 09:07
dtwyman

Hi,

Just tried doing a symbolic link and that didn't fix the mediawiki issue - any suggestions?

Dan

Tue, 12/15/2009 - 09:15
dtwyman

The entries are correct.

It was set to /home/mysql before I tried the link thing. It's now set to /var/lib/mysql and /var/lib/mysql points to /home/mysql

Tue, 12/15/2009 - 09:19
andreychek

Okay, I think you're seeing two bugs then:

  1. Something's up with the MediaWiki installer

  2. The chgrp command Virtualmin runs on the MySQL database isn't correctly using the "Path to MySQL databases directory" setting

I unfortunately can't really assist with those (though the symlink you created will handle #2 for now).

Jamie, however, can certainly get that fixed up... you can file a support request and he'll take a look.

Thanks!

-Eric

Topic locked