The Installatron Repair Utility is designed to fix most problems that can occur with Installatron Plugin and Installatron Server. This utility can be executed any time difficulties are experienced. There is no harm in executing the utility; it's always the first thing to try.
To perform a repair on Linux/Unix/FreeBSD, run these four commands as the root user:
rm -fr /usr/local/installatron/lib /usr/local/installatron/etc/php.ini curl -O http://data1.liquenox.com/installatron/installatron_setup.sh chmod 755 installatron_setup.sh ./installatron_setup.sh -f --edgeTip: To run repair in interactive mode, remove -f from the last command.
To perform a repair on Windows, re-run the installatron_setup.exe wizard.
Installatron 'Requirements' settings can be used to automatically remove scripts that will not work on your server.
Check your settings in Administration > Settings > Requirements. Disable all filtering to see all installers.
Some recent application version require PHP 5.3 or newer.
Upgrade PHP to 5.3+. Or if you want to keep the current PHP version but allow those versions to be installed anyway, you can disable version-filtering based on the PHP version in Administration > Settings > Requirements (this is not a supported option).
Magento requires the PDO MYSQL PHP extension, which is not standard on all hosting control panels.
Add the PDO MYSQL extension to PHP, or disable Magento in Installatron Admin > Applications > Catalogs.
If the installs appear at Administration > Installed Applications but are not listed for the user's login then there is an error with the install data. This can happen if a user is moved to a server with a different configuration than the one the installs were created on.
The error can be found by logging in as the user, navigating to My Applications, and adding this to the end of the URL:
#cmd=edit&id=INSTALLID
Where INSTALLID is the id of the install (can be found in ~/.installatron/current/). If the error is fixed the install will appear in the user's login.
On a DirectAdmin server this is caused by an incompatibility between DirectAdmin and Zend 3.3.0.
On a cPanel/WHM server this is caused by use of an old version of cPanel/WHM.
First check that it's not caused by an empty php.ini:
head -n 5 /usr/local/lib/php.ini
If the results of that command are empty, you'll need to reinstate DirectAdmin's php.ini file. If it prints content, continue below.
Check the version of Zend your server is running:
/usr/local/bin/php -v
If it is 3.3.0, upgrade to a more recent version of Zend.
Upgrading cPanel/WHM to version 11 or newer will fix the problem (if you also upgrade to a cPanel/WHM 11-style theme).
This type of error can sometimes occur when an account is out of available disk space. However, in most cases a more graceful error is displayed.
Check that the web hosting account has enough available disk space. If additional space is required, contact your service provider directly to add additional disk space.
A .htaccess file is likely interfering with a HTTP request.
Check the installation directory and parent directories (public_html) for a .htaccess file that could interfere with requests to the aforementioned URL. You either can fix the .htaccess file or temporarily rename it and try again.
A few variations of these errors exist. The errors are returned from the control panel software verbatim.
This happens when the control panel software is unable to create a database on behalf of Installatron. Most likely this means the account has no databases remaining.
An existing database can be selected for the install by choosing the "Let me manage the database settings" option on the Database step, or most likely additional databases can be purchased.
A few variations of these errors exist. The errors are returned from the control panel software verbatim.
This happens when Installatron is unable to retrieve a list of user's database via the control panel's plugin API.
Typically logging out of the control panel and re-trying the task will solve the problem.
If problems persist, try changing the "HTTP driver" in Administration > Dependencies. It may be that the default driver is not suitable for your server setup. A CURL binary should be selected whenever possible.
If the the control panel uses https:// then it may be that the CURL options lack functional OpenSSL support. This can be tested for CURL binaries with:
/path/to/curl -v -k 'https://127.0.0.1:2222'
If the control panel is DirectAdmin, and DirectAdmin is not accessible from 127.0.0.1, then run this:
echo "allow_foreign_key=1" >> /usr/local/directadmin/conf/directadmin.conf echo "action=directadmin&value=restart" >> /usr/local/directadmin/data/task.queue
This can happen when PHP is not installed, when the server configuration changes, or when no loaders are found to be compatible with the server.
Try installing a dedicated instance of PHP for Installatron to use:
wget http://us.php.net/distributions/php-5.3.13.tar.gz tar xzf php-5.3.13.tar.gz cd php-5.3.13 ./configure --prefix=/usr/local/installatron/php --disable-libxml --disable-dom --disable-simplexml --disable-xml --disable-xmlreader --disable-xmlwriter --without-pear --with-zlib --enable-mbstring --enable-ftp --with-mysql=mysqlnd --with-mysqli=mysqlnd make make install cd .. rm -fr php-5.3.13 php-5.3.13.tar.gz /usr/local/installatron/etc/php.ini /usr/local/installatron/bin/php
Then re-execute the Installatron Repair Utility at the top of this page.
The selected domain is not resolving correctly to its web hosting space, or there is a networking/firewall issue with the server configuration.
Installatron tests the domain before going ahead with an install or upgrade. The test is performed by creating a file in the install location and then attempting to access the file via a HTTP socket from the server. This check does NOT require DNS to succeed.
Check your /var/installatron/logs/fetch* log files for information on why the tests failed.
The test can be disabled server-wide by running this as root:
echo "domaincheck=no" >> /usr/local/installatron/etc/settings.ini
However, we don't recommend disabling the test. It's better to determine why the domain isn't working.
This can occur when upgrading from a beta version when the log files are large.
Execute this command and then try the update again.
rm -r /var/installatron/logs
The ZIP binary being used by Installatron is unable to extract the archive of the script being installed.
You can change the ZIP binary used by Installatron in Administration > Settings > Libraries. If you only have the one ZIP library you will need to install another one or update the existing library.
The ZIP binary being used by Installatron is unable to extract the archive of the script being installed.
You can change the ZIP binary used by Installatron in Administration > Settings > Libraries. If you only have the one ZIP library you will need to install another one or update the existing library.
The RPM package "file" is missing.
Install the missing RPM package:
yum install file
Then re-execute the Installatron Repair Utility at the top of this page.
This is a known bug in Magento that makes it incompatible with some servers.
If you're the server administrator, disable Magento using the Applications > Catalogs administration tool. It is worth submitting a bug report to Magento to aid in finding a solution.