1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Mambo (outside application vault) install failure

Discussion in 'Plesk for Linux - 8.x and Older' started by Lucos, Mar 23, 2005.

  1. Lucos

    Lucos Guest

    Hi there,

    I'm running a dedicated server with Plesk 7.5 (without permission to install application -eiter commercial or free- from Plesk Application Vault).
    I want to install Mambo server (that you may know: www.mamboserver.com).
    I tried both automated web installation and command line manual installation (under SSH with root privileges) and encountered several major problems.

    I wanted to know if someone had been in the same configuration/situation?

    I think that due to the fact Plesk remove the root access to mysal (replaced by admin with the root password), Mambo has problems to connect to mysql (as mambo is php and php is identified as apache user).

    I created a db called mambo, gave localhost, admin and password, mambo database name, to the installer, no success: blank screen.

    My directories/files are writable (the session path is not writable and I have some little problems regarding the requirements on mambo 1st installation page: globals, safe mode), but it seems not to be the cause of the problem.

    Plesk don't see the database created via SSH: mysql -uadmin -ppassadmin create database mambo but prevent me from creating one with the same name (so Plesk knows it but don't display it).

    I gave the correct path to the configuration.php-dist file and other parameters, renamed it to configuration.php and so on ...

    So, I'm stuck in the middle of nowhere :(

    Last try was to install Mambo rpm via yum.
    As yum told me there was an rpm in the local folder (/opt/ ...) i removed it and now I'm about to re-install a Mambo rpm (found at rocket turle) in another folder than the application vault one. But yum checked the dependencies and there are a lot of updates! I'm scared about doing all those updates, as I may not get Plesk access after that.

    I'm thinking about doing a download of the Mambo rpm and manually (rpm command) installing it without checking the dependencies (as it must work because Mambo was installed in the application vault).

    Any help?

    Thanks a lot
  2. zoltar

    zoltar Guest

    safe mode and the session path is an issue.

    Mambo 4.5.1 has a safe_mode patch, but it seems there is no patch for 4.5.2

    but if you have root access then you can disable safe_mode per virtual host.

    your virtual host config file is located at:
    /home/httpd/vhost/your_domain/conf and called httpd.include

    you could modify this file, but this file gets regenerated by Plesk.

    So, create a file called vhost.conf
    and add the folowing line in it:

    php_admin_flag safe_mode Off

    then run this command:
    /usr/local/psa/admin/sbin/websrvmng --reconfigure-vhost --vhost-name=<domain_name>

    restart httpd and start the install again:
    PHP safe mode is off and your /tmp is writeable.

    I hope it helps.
  3. RexAdmin

    RexAdmin Guest

    Also, Mambo built-in package with Plesk is badly configured/installed (talking about 7.5.2).

    No Frontpage component in components menu!

    You should install from the source Mambo if you want full functions of this CMS.

    Good luck
  4. CBiLL

    CBiLL Guest

    Try making your root dir writable .. /httpdocs/ to 775 then you should be able to install mambo using it's installer.

    it is more secure to install mambo into it own folder that is writable then use htaccess rewrite to point your homepage index to the index.php in mambo folder.

    I install and run Mambo that was download direclty from Mamboserver rather than using application package because once you get it up and running then it easier to keep it up to date and do mofitations to it if you wanted rather than having to depend on Sw-Soft to come out with patches if secuirty holes was discovered or breaking mambo trying to mod it ..