We take these seriously and have incorporated additional error checking/prevention methods. Unfortunately they don't catch everything.
= Reasons for Failure =
Reasons for failure vary, but the most common are:
<ul>
</ul></ul>
= Recipe for Success =
There are some recommendation users can follow to help correct or prevent these problems.
# [[Submit Bug Report|Submit a bug report]]. Provide details to help with [[App_troubleshooting|debugability]] of the issue.
= Failed Install Clean Up =
<!--== MANUAL CLEAN UP ==:'''NOTE:''' We will use '''owncloud''' as an example of the application that failed to install. An application install was unsuccessful, but it appears partially installed. This often happens and repeatedly trying to install without clean up results in multiple failed attempts. For example, 4 failed attempts of [https://www.amahi.org/apps/owncloud ownCloud] would create owncloud, owncloud1, owncloud2, owncloud3. To return your HDA to a safe state for another install attempt, the following may help:* Check Navigate to Network>DNS Aliases in the Amahi Dashboard** Make note of the URL name** Remove entry for the failed application by selecting Delete<ul><li>The next steps must be done from the command line as ''root'' user:</li><ul><li>Navigate to /varetc/httpd/hdaconf.d and determine file name to remove</webli> ls -al<li>Remove ####-apps directory app.conf (substitute the number for #### and look URL name for the app) file</li> cd /etc/httpd/conf. d rm -rf 1001-owncloud.conf<li>Then as ''root'' user, restart apache</li>** The application short URL is the name of the directory. For examplesysemctl restart httpd<li>Next, Adminer would be adminer.navigate to /var/hda/web-apps</li> cd /var/hda/web-apps** <li>Remove the app directory</li> rm -rf owncloud</ul></ul>* Check Finally check the HDA database (hda_production, apps table). The safest way is to use a web application such as [https://www.amahi.org/apps/adminer Adminer] or [https://www.amahi.org/apps/phpmyadmin phpMyAdmin].
** Look to see if there is an entry for the app that failed to install correctly.
** Remove
the row(s) that
row if it exists.exist for the application<br />:'''EXAMPLE'''<blockquote><pre>MariaDB [hda_production]> select id,name from webapps;
+----+------------+
| id | name |
+----+------------+
| 1 | phpsysinfo |
| 2 | cups || 4 | zm owncloud || 5 | zm1 owncloud1 || 6 | zm2 owncloud2 || 7 | zm3 || 8 | zm4 || owncloud3 9 | zm5 || 10 | zm6 || 12 | zm7 || 14 | zm8 |
+----+------------+
11 5 rows in set (0.00 sec)</pre></blockquote>* Check Once these steps are complete, it should be safe to try and install the application. Monitor the '''/etcvar/httpdlog/conf.d directory for a file that is associated with the amahi-app. ** For example, 1001-adminerinstaller.conf would be log''' file for Adminer.progress and errors via command line:** If it exists, remove it.1** Restart httpd.service tail -f /var/log/amahi-app->installer.log
