Installing third-party scripts

Submitted by emcali on Fri, 07/31/2009 - 02:22

Installing third-party scripts ..

  Installing phpmyadmin version 2.11.9.5 ..
  PHP module mysql is required ..
  .. automatic module installation is not available on your system.

.. done

mmm

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Fri, 07/31/2009 - 12:54

How was Virtualmin installed on your system originally? It is a Joyent accelerator?

In some cases, PHP modules like mysql have to be manually setup, as Virtualmin doesn't know about the package system..

Submitted by emcali on Mon, 08/03/2009 - 09:26

Install package "Optimized Open Source Software Stack (Cool Stack)" of SUN.

This installs all in /opt/coolstack/... this must be the error...

Possible solution to this would be to create symbolic links ...

What is the location of the packages that virtualmin normally looks?

Submitted by JamieCameron on Mon, 08/03/2009 - 19:12

So you installed Virtualmin GPL from this "Optimized Open Source Software Stack", and then upgraded to Virtualmin Pro?

If that case, you will need to install the mysql PHP module manually .. how to do this would depend on your operating system and PHP distribution.

Submitted by emcali on Mon, 08/03/2009 - 22:10

!!!CoolStack!!! is = " apache, mysql, php, perl para solaris"

http://cooltools.sunsource.net/coolstack/

I do not understand what I mean by this """So you installed Virtualmin GPL from this "Optimized Open Source Software Stack", and then upgraded to Virtualmin Pro?"""

my system has the module mysql installed and many others...

this error not only happens with phpmyadmin ...

please... answered my question ...

What is the location of the packages (php, apache, mysql) normally look virtualmin?

Submitted by CharlesMason on Tue, 08/04/2009 - 00:34

Not sure if this is related, but just went to install Joomla 1.5.13 on my server and I'm getting the same error. Yet, Joomla is installed on another one of my sites... the interesting part is that the site that has joomla and phpadmin, the php modules list under "Website Options" "PHP Information" is a lot larger then the server that is providing the same described error. I think what emcali is asking is where do we configure these modules, so we can install or point php to recognize the missing module.

Submitted by emcali on Tue, 08/04/2009 - 01:00

yes...

Installing third-party scripts ..

  Installing b2evolution version 1.9.2-2007-01-22 ..
  PHP module mysql is required ..
        Enabling module in PHP configuration ..
        Failed to create virtual server : Missing file to open at WebminCore::../web-lib-funcs.pl line 2678

The following link will cree:

ln -s /opt/coolstack/php5/lib/php.ini /etc/php.ini

and showed me the following:

  Installing b2evolution version 1.9.2-2007-01-22 ..
  PHP module mysql is required ..
        .. automatic module installation is not available on your system ..

I think that is the path of the software.

because of that my question:

"What is the location of the packages (php, apache, mysql) normally look virtualmin?"

clarified that this happens in the creation of a virtual server.

Submitted by JamieCameron on Tue, 08/04/2009 - 02:00

Normally, Virtualmin attempts to install missing PHP modules from a package update system like YUM or APT, using a command like : yum install php5-mysql

However, if your system doesn't have APT or YUM, it has no way to install the missing module automatically, hence you get the error "automatic module installation is not available on your system".

The fix is to install the mysql PHP module, and to enable it in /etc/php.ini or the domain's ~/etc/php*/php.ini file with a line like :

extension=mysql.so

Submitted by CharlesMason on Tue, 08/04/2009 - 18:05

Hi Jamie,

I hope that I'm not treading on this thread... Why would installing a script on domain A work but not domain B? It would have to be in the domain's php5.ini file, yet upon search of domain A (which installs and working) .ini file doesn't make any reference to mysql.so. I am not at a location that my server will allow me access, but I will perform a broad based search for mysql.so and see if I can isolate the issue.

Based on my search on the support, this isn't the first time this has occurred, so I hope I can find a solution to help everyone.

Best regards, Charles

Submitted by CharlesMason on Wed, 08/05/2009 - 12:36

Hi Guys,

Ok, here is the solution that I found:

On the server that was providing the error, in this case domain B the extension_dir was defined as

; Directory in which the loadable extensions (modules) reside.
extension_dir = "/usr/lib/php/modules"

However, on the domains that did not that installed script fine, in this case domain A extension_dir was defined as

; Directory in which the loadable extensions (modules) reside.
; extension_dir = "./"

The difference of course being that domain A having commented out the extension_dir, which would default the php to the default php.ini setting versus domain specific domain php.ini settings. Once, I commented out the extension settings on domain B, the install went without any problems.

Also as a side note, domain B has extension=mysql.so in it domain specific php.ini file, even though it was the domain that wouldn't install the script.

I hope that this help someone! ;-)

Best regards, Charles