Trusted, Bureaucrats, Administrators
12,424
edits
Changes
From Amahi Wiki
Created page with "{{WorkInProgress}} Occasionally Amahi [https://www.amahi.org/apps applications] fail to install properly. This is often noted by error messages in the application install log..."
{{WorkInProgress}}
Occasionally Amahi [https://www.amahi.org/apps applications] fail to install properly. This is often noted by error messages in the application install log (/var/log/amahi-app-install.log).
<screenshot>
Other times, you may receive notice in the Dashboard.
<screenshot>
We take these seriously and have tried to incorporate additional error checking and prevention methods. Unfortunately they don't catch everything.
Reasons for failure vary, but the most common are:
* Slow or sporadic internet connection.
* Install script is taking too long.
* Application source file is unavailable.
There are some recommendation users can follow to help correct or prevent these problems.
<b>DO NOT:</b>
# Refresh your web browser or navigate from the page while an application is installing.
# Try to install an application after it initially fails.
<b>DO:</b>
# Check the log for details of why the app install failed.
# Check the Dashboard Apps tab, Installed section for the app.
# Check /var/hda/web-apps to ensure the app did not partially install.
# File a [https://bugs.amahi.org bug report].
<!--== MANUAL CLEAN UP ==
An application install was unsuccessful, but it appears partially installed. To return your HDA to a safe state for another install attempt, the following may help:
* Check /var/hda/web-apps directory and look for the app.
** The application short URL is the name of the directory. For example, Adminer would be adminer.
** Remove the directory
* Check the HDA database (hda_production, apps table)
** Look to see if there is an entry for the app that failed to install correctly.
** Remove that row if it exists.
* Check /etc/httpd/conf.d directory for a file that is associated with the app. ** For example, 1001-adminer.conf would be for Adminer.
** If it exists, remove it.1
** Restart httpd.service-->
Occasionally Amahi [https://www.amahi.org/apps applications] fail to install properly. This is often noted by error messages in the application install log (/var/log/amahi-app-install.log).
<screenshot>
Other times, you may receive notice in the Dashboard.
<screenshot>
We take these seriously and have tried to incorporate additional error checking and prevention methods. Unfortunately they don't catch everything.
Reasons for failure vary, but the most common are:
* Slow or sporadic internet connection.
* Install script is taking too long.
* Application source file is unavailable.
There are some recommendation users can follow to help correct or prevent these problems.
<b>DO NOT:</b>
# Refresh your web browser or navigate from the page while an application is installing.
# Try to install an application after it initially fails.
<b>DO:</b>
# Check the log for details of why the app install failed.
# Check the Dashboard Apps tab, Installed section for the app.
# Check /var/hda/web-apps to ensure the app did not partially install.
# File a [https://bugs.amahi.org bug report].
<!--== MANUAL CLEAN UP ==
An application install was unsuccessful, but it appears partially installed. To return your HDA to a safe state for another install attempt, the following may help:
* Check /var/hda/web-apps directory and look for the app.
** The application short URL is the name of the directory. For example, Adminer would be adminer.
** Remove the directory
* Check the HDA database (hda_production, apps table)
** Look to see if there is an entry for the app that failed to install correctly.
** Remove that row if it exists.
* Check /etc/httpd/conf.d directory for a file that is associated with the app. ** For example, 1001-adminer.conf would be for Adminer.
** If it exists, remove it.1
** Restart httpd.service-->
