App troubleshooting

Application installs should NEVER fail. Period. App install failures are high priority to the Amahi Team.

Debugability

Debugging app install issues is very important, so any time something permanently destructive is attempted, it should be done with care to preserve the ability to analyze and debug what happened:

• Preserve as much as possible from the existing (buggy) environment

• Make sure httpd configuration is sane (result should be "Syntax OK"):

httpd -t

• The idea is to not delete anything permanently - copy or move things to, say, a folder in /tmp if you have to get something out of their place. For example:

mkdir /tmp/app-debug/

• Then add things there as necessary for later analysis, like:

cp -a /var/log/amahi-app-installer.log /tmp/app-debug
cp -a /etc/httpd/conf.d /tmp/app-debug

The user can provide this information:

• Copy of the app install log:

Fedora

tail -300 /var/log/amahi-app-installer.log | fpaste

Ubuntu

tail -300 /var/log/amahi-app-installer.log | apaste

• Copy of the app error and access logs (i.e. Adminer is the app):

cat /var/hda/web-apps/adminer/logs/error.log
cat /var/hda/web-apps/adminer/logs/access.log

• To check if process is running (i.e. sab is the app):

Fedora

ps guax | grep sab | fpaste

Ubuntu

ps guax | grep sab | apaste