App troubleshooting
From Amahi Wiki
App install should never fail. Period. App install failures are high priority.
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"):
| bash code |
|---|
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:
| bash code |
|---|
mkdir /tmp/app-debug/
|
- Then add things there as necessary for later analysis, like:
| bash code |
|---|
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:
| bash code |
|---|
tail -300 /var/log/amahi-app-installer.log | fpaste
|
- Copy of the app error and access logs (i.e. sabnzbd is the app):
| bash code |
|---|
cat /var/hda/web-apps/sabnzbd/logs/error.log cat /var/hda/web-apps/sabnzbd/logs/access.log
|
- To check if process is running (i.e. sab is the app):
| bash code |
|---|
ps guax | grep sab | fpaste
|
