Difference between revisions of "Platform troubleshooting"
From Amahi Wiki
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | = Diagnose = | ||
To diagnose issues with the platform, the first step is to look at the platform log: | To diagnose issues with the platform, the first step is to look at the platform log: | ||
| − | + | <blockquote><u>Fedora</u></blockquote> | |
| + | tail -300 /var/hda/platform/html/log/production.log | apaste | ||
| − | < | + | <blockquote><u>Ubuntu</u></blockquote> |
| + | tail -300 /var/hda/platform/html/log/production.log | apaste | ||
| + | |||
| + | It's possible that ''/etc/http/conf.d/10*.conf'' files are wedging the web server (httpd/apache) configuration. Restart apache and check the '''error_log''' (''/var/log/httpd'' or ''/var/log/apache2''). | ||
| + | |||
| + | = Dashboard Error = | ||
| + | * You will see a message that states: | ||
| + | <pre>The Dashboard has encountered an exception! | ||
| + | Woopsie. Sorry about that! | ||
| + | It could be due to a bug, or very low memory, or very low disk in the root (/) partition. | ||
| + | If your disk or memory are not critical, it's likely a bug.</pre> | ||
| + | * You can verify disk space by doing: | ||
| + | df -h | ||
| + | * If it reflects very little or no space on '''root (/)''', then you need to clear some space. Best way to do this is remove large files from shares. | ||
| + | |||
| + | |||
| + | Back to the [[Troubleshooting]]. | ||
Latest revision as of 00:37, 25 May 2017
Diagnose
To diagnose issues with the platform, the first step is to look at the platform log:
Fedora
tail -300 /var/hda/platform/html/log/production.log | apaste
Ubuntu
tail -300 /var/hda/platform/html/log/production.log | apaste
It's possible that /etc/http/conf.d/10*.conf files are wedging the web server (httpd/apache) configuration. Restart apache and check the error_log (/var/log/httpd or /var/log/apache2).
Dashboard Error
- You will see a message that states:
The Dashboard has encountered an exception! Woopsie. Sorry about that! It could be due to a bug, or very low memory, or very low disk in the root (/) partition. If your disk or memory are not critical, it's likely a bug.
- You can verify disk space by doing:
df -h
- If it reflects very little or no space on root (/), then you need to clear some space. Best way to do this is remove large files from shares.
Back to the Troubleshooting.
