Installatron Repair Utility
The Installatron Repair Utility is able to fix most problems that can occur with Installatron. This can be run any time the server is upgraded or any time that Installatron is experiencing difficulties. There is no harm in running the repair utility, so it is always the first thing to try.
Linux/Unix/FreeBSD
To perform a repair on Linux/Unix/FreeBSD, run these three commands as the
root user:
wget http://data1.liquenox.com/installatron/installatron_setup.sh
chmod 755 installatron_setup.sh
./installatron_setup.sh -f --release
Tip: To run repair in
interactive mode, remove
-f from the last command.
Windows
To perform a repair on Windows, re-run the
installatron_setup.exe wizard.
Check the troubleshooting guide below if
repair does not solve the problem. If the guide doesn't help,
open a ticket.
Installatron Troubleshooting
Known Issues
Installatron Error Messages
Operating System Error Messages
Install Error Messages
Known Issues
One or more installers are missing
CAUSE
Installatron 'Requirements' settings can be used to automatically remove scripts that will not work on your server.
SOLUTION
Check your settings in Administration > Settings > Requirements. Disable all filtering to see all installers.
php-pdo-mysql-version-minimum v1 (detected: OFF)
CAUSE
Magento requires the
PDO_MYSQL PHP extension, which is not standard on all hosting control panels.
SOLUTION
Add the PHP_MYSQL extension to PHP, or disable Magento in Installatron Admin > Applications > Catalogs.
Joomla is missing some versions
CAUSE
The 1.5.x branch of Joomla requires PHP 4.4.7 or better.
SOLUTION
Upgrade PHP. 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).
User's installs are missing from Installed Scripts
CAUSE
If the installs appear in Administration > Installs Overview but are not listed in 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.
SOLUTION
The error can be found by logging in as the user, navigating to Installed Scripts, and adding this to the end of the URL:
#cmd=edit&il0=install_id
Where
install_id 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.
The 'Installatron Script Installer' and 'Installatron Admin' links are missing in the control panel
CAUSE
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, or by a theme that does not support Installatron.
DIRECTADMIN SOLUTION
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 not 3.3.0 then
contact us.
If it is 3.3.0, you can downgrade to an earlier version with:
cd /usr/local/directadmin/customapache
./build clean
./build update
./build zend
And then run a
repair (see top of page) to ensure there are no remaining problems. The Installatron links should now appear in the DirectAdmin control panel.
CPANEL/WHM SOLUTION
Upgrading cPanel/WHM to version 11 or newer will fix the problem (if you also upgrade to a cPanel/WHM 11-style theme).
The 'Installatron Script Installer' and 'Installatron Admin' links go to a blank page
SOLUTION
This is easily fixed by re-compiling:
cd /usr/local/installatron/lib
curl -O http://data1.liquenox.com/installatron/suexec/suexec.c
make suexec
../repair -f
When installing a script, it never gets past acceptance of the license
CAUSE
If the install process gets stuck after accepting the license agreement only on scripts that use a database then the CURL libraries are segfaulting. This can occur with old libraries, or when PHP is updated without also updating CURL.
SOLUTION
You can change the CURL library used by Installatron at Administration > Settings > Libraries. If you only have the one CURL library you will need to install another one or update the existing library.
Installatron Errors
You have exceeded the maximum allowed databases.
A few variations of these errors exist. The errors are returned from the control panel software verbatim.
CAUSE
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.
SOLUTION
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.
Unable to get list of databases. There is a communication problem with the control panel API.
CAUSE
This happens when Installatron is unable to retrieve a list of user's database via the control panel's plugin API.
SOLUTIONS
Try changing the "HTTP driver" in
Administration >> Dependencies. It may be that the default driver is not suitable for your server setup. You should select a CURL option rather than a WGET option, and if no PHP CURL Extension is listed you could consider adding CURL to PHP as an addition option.
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
Error: Can't Download Core Tarball
CAUSE
This happens when the
Check & Update System Files button, in administration, is clicked on an old 3.x.x server that is unable to use the new 5.0 resources.
SOLUTION
Manually run an
Installatron Update.
Error: Installatron bytecode loader failed
CAUSE
This can happen when the server configuration changes.
SOLUTION
Run an
Installatron Update should update Installatron to match the server changes.
Error: A test of the selected domain has failed
CAUSE
The user's domain is not resolving correctly to the web hosting account, or if there is a networking/firewall issue with the server configuration.
Installatron tests the domain before going ahead with an install or upgrade. This was added to stop problems caused by non-working domains. 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. If that test fails it then attempts to access the file from the Installatron licensing server via HTTP, and only if both of those attempts fail will it give this fatal error message.
SOLUTION
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.
File size limit exceeded
CAUSE
This happens when upgrading to 5.0 from a beta when the log files are large.
SOLUTION
Execute this shell command and then try the
update again.
rm -r /var/installatron/logs
archive extracted no files - try a different zip driver
CAUSE
The ZIP binary being used by Installatron is unable to extract the archive of the script being installed.
SOLUTION
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.
Operating System Error Error Messages
Site error: the file .../kernel.php requires the ionCube PHP Loader (etc)
CAUSE
The ionCube loaders are PHP-version specific, so this error will appear any time PHP is upgraded on the server.
SOLUTION
First, try the Installatron repair utility detailed at the top of this page. That will fix the problem if Installatron is using its own ionCube loaders.
If you still see the error, then it's likely that Installatron is using the server's loaders (only one set of loaders can be installed, so if they exist on the server Installatron must use them). Check to see that the server's copy of the installers are updated to match the current PHP version.
Then you need to either edit Installatron's php.ini so that it loads the server's ionCube loaders:
/usr/local/installatron/etc/php.ini
Or if your server's php.ini has ionCube configured correctly you can copy that php.ini over the Installatron one.
Script Error Messages
Drupal: You have an error in your SQL syntax{...}/includes/menu.inc on line 315
CAUSE
This is a known bug in the 6.x branch of Drupal that makes it incompatible with some servers.
SOLUTION
You can disable the Drupal installer using the Access Groups administration tool. It is worth submitting a bug report to Drupal to aid in finding a solution.
Magento: Error in file:{...}/sql/sales_setup/mysql4-upgrade-0.9.24-0.9.25.php{...}SQLSTATE[23000]
CAUSE
This is a known bug in Magento that makes it incompatible with some servers.
SOLUTION
You can disable the Magento installer using the Access Groups administration tool. It is worth submitting a bug report to Magento to aid in finding a solution.
Magento: Error in file:{...}/sql/catalogrule_setup/mysql4-upgrade-0.7.4-0.7.5.php{...}SQLSTATE[42S01]
CAUSE
This is a known bug in Magento that fails the upgrade process on some servers.
SOLUTION
Check the Magento forums for potential fixes. It is worth submitting a bug report to Magento to aid in finding a solution.
shopping cart (