The Installatron Repair Utility is designed to fix most problems that can occur with Installatron Plugin. 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 https://data.installatron.com/installatron-plugin.sh chmod +x installatron-plugin.sh ./installatron-plugin.sh -f --quickTip: To run repair in interactive mode, remove -f from the last command.
To perform a repair on Windows, re-run the installatron-plugin.exe wizard.
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 https://data.installatron.com/installatron-server.sh chmod +x installatron-server.sh ./installatron-server.sh -f --quickTip: To run repair in interactive mode, remove -f from the last command.
To perform a repair on Windows, re-run the installatron-server.exe wizard.
Double check that the "Installatron" feature is enabled within WHM's Feature List tool for the feature lists where it should be enabled.
Within WHM's Feature List tool, the first entry ("Installatron") refers to the Installatron system itself and must be enabled to activate Installatron, and the second entry ("Installatron Widget") activates the dashboard section that lists top apps and installed apps right on the main cPanel menu.
Try clearing the task queue by executing this command as root:
rm -fr /var/installatron/tasks/*
A crontab process may be active that is designed to terminate PHP processes that are executing "too long".
Disable the offending crontab process, or replace it with a crontab process that grants immunity to Installatron-created processes.
The below bash code, when executed as a crontab process every so often, will only kill PHP processes that have been executing longer than 600 seconds and show up in the output of "ps -eo command" as containing "/usr/bin/php". This will work without modification on most fastcgi environments. Feel free to modify this code to match your environment.
ps -eo uid,pid,lstart,command |
tail -n+2 |
while read PROC_UID PROC_PID PROC_LSTART_WDAY PROC_LSTART_MONTH PROC_LSTART_DAY PROC_LSTART_TIME PROC_LSTART_YEAR PROC_COMMAND; do
SECONDS=$[$(date +%s) - $(date -d"$PROC_LSTART_WDAY $PROC_LSTART_MONTH $PROC_LSTART_DAY $PROC_LSTART_TIME $PROC_LSTART_YEAR" +%s)]
if [[ "$PROC_COMMAND" == */usr/bin/php* ]]; then
if [ $PROC_UID -gt 0 -a $SECONDS -gt 600 ]; then
echo $PROC_PID
fi
fi
done |
xargs kill
Some recent application versions 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).
A number of apps require the PDO MYSQL PHP extension, which is not standard on all hosting control panels.
Add the PDO MYSQL extension to PHP, or disable affected apps within Installatron Admin > Applications > Access Control.
If installed applications do not appear at the My Applications tab then there is an error within cached data. This can happen if a user is moved to a server with a different configuration than the one the installs were created on. Typically no action is necessary when this occurs; the issue will automatically correct itself the next time the daily Installatron Update process executes.
Execute these commands:
/usr/local/installatron/repair -f --quick /usr/local/installatron/installatron --repair --recache /usr/local/installatron/installatron --send-update-report
For Installatron Plugin only: If the first solution does not remedy the problem, execute these commands:
/usr/local/installatron/repair -f --quick mv -f /var/installatron/data.db /var/installatron/data.db.bak20170103 rm -f /var/installatron/data.db-* /usr/local/installatron/installatron --repair --recache /usr/local/installatron/installatron --send-update-report
On a DirectAdmin server this is caused by an incompatibility between DirectAdmin and PHP/Zend.
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, tell Installatron to apply a workaround:
touch /usr/local/installatron/etc/zend_fix
Upgrading cPanel/WHM to version 11 or newer will fix the problem (if you also upgrade to a cPanel/WHM 11-style theme).
Execute these commands:
/usr/local/installatron/repair -f --quick /usr/local/installatron/installatron --repair --recache /usr/local/installatron/installatron --send-update-report
Execute these commands:
/usr/local/installatron/repair -f --quick mv /var/installatron/data.db /var/installatron/data.db.bak20170103 rm -f /var/installatron/data.db-* /usr/local/installatron/installatron --repair --recache /usr/local/installatron/installatron --send-update-report
Firewall configurations that whitelist addresses must allow outgoing port 80 connections to these addresses.
dal01.installatron.com (North America - Dallas) dal02.installatron.com (North America - Dallas)
Based on a server's geographic location, or for added redundancy, additionally allowing connections to these addresses is recommended. When multiple addresses are available the closest geographically will always be tried first.
nue01.installatron.com (Europe - Nuremberg) sng01.installatron.com (Asia - Singapore) syd01.installatron.com (Oceania - Sydney)
It's also possible to create an internal mirror for your company following the FAQ here: How do I create an Installatron Fast Update server?
The SSL connection to data.installatron.com could not be established. To verify, test with this command:
curl -v https://data.installatron.com/manifest.md5
If the server is older, the server root certificates may be out of date.
If you're unable to get the server to accept this certificate, add a --no-check-certificate argument to the original command.
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.
Try changing the "Fetch/HTTP driver" in Administration > Settings. 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:
curl -v -k 'https://127.0.0.1:2222'
By default Installatron uses a system PHP instance. In the vast majority of cases this works flawlessly. However, in rare cases this instance may not be compatible with Installatron.
When this occurs, compiling a dedicated PHP instance just for Installatron is the most reliable solution.
Try installing a dedicated PHP instance just for Installatron. The PHP instance used by website owners will not be modified.
mkdir -p /usr/local/installatron cd /usr/local/installatron curl -O http://php.net/distributions/php-5.5.37.tar.gz tar xzf php-5.5.37.tar.gz cd php-5.5.37 ./configure --prefix=/usr/local/installatron/php --disable-libxml --disable-dom --disable-simplexml --disable-xml --disable-xmlreader --disable-xmlwriter --enable-posix --enable-mbstring --enable-ftp --enable-sockets --without-pear --without-iconv --with-zlib --with-gd --with-jpeg-dir --with-png-dir --with-mysql=mysqlnd --with-mysqli=mysqlnd --with-pdo-mysql=mysqlnd --with-gettext make make install cd .. rm -fr php-5.5.37 php-5.5.37.tar.gz /usr/local/installatron/bin/php
Next, follow the steps at the top of this page to execute a "repair" of Installatron.
That's it! Installatron should now be working.
There is a problem communicating with MySQL.
If databases are actually being created, try specifying a MySQL socket value in /usr/local/installatron/etc/php.ini. For example:
mysql.default_socket = /var/lib/mysql/mysql.sock
While Installatron doesn't require domains to resolve prior to use, Installatron does check for any domain misconfiguration that would prevent the installed application from functioning, including IP mismatches and firewall problems.
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.
To enable interaction with non-resolving domains, including the "url-ip" argument with Installatron Server API queries, which will inform Installatron Server where it should resolve the domain.
The cPanel API failed to create a database for Installatron Plugin.
Check if either of the below values exist in /etc/my.cnf:
skip-name-resolve skip-host-cache
If either value exists, comment the value out, restart mysql, and then try the action within Installatron Plugin again. If the problem is still not solved, check if the user has their own my.cnf file within their home directory.
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, deactivate Magento using the Applications > Access Control administration tool. It is worth submitting a bug report to Magento to aid in finding a solution.
The Zend Guard extension under PHP 5.3 causes Gallery 3 to produce only a blank screen. More information: http://forums.zend.com/viewtopic.php?f=57&t=11953
If you're the server administrator, deactivate Gallery 3.x using the Applications > Access Control administration tool.