Difference between revisions of "App troubleshooting"
From Amahi Wiki
| Line 15: | Line 15: | ||
Then add things there as necessary for later analysis, like: | Then add things there as necessary for later analysis, like: | ||
| − | + | {{Code|cp -a /var/log/amahi-app-installer.log /tmp/app-debug | |
| − | + | cp -a /etc/httpd/conf.d /tmp/app-debug}} | |
ALso the user can provide this information: | ALso the user can provide this information: | ||
Revision as of 01:59, 23 March 2011
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: httpd -t - should say "Syntax OK"
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
|
ALso the user can provide this information:
- tail -300 /var/log/amahi-app-installer.log | fpaste
- To check if process is running (i.e. sab is the app):
| bash code |
|---|
ps guax | grep sab | fpaste
|
