Difference between revisions of "Troubleshoot Web Interface"
(→Fatal error: Allowed memory size of xxxxxxxx bytes exhausted) |
|||
| Line 1: | Line 1: | ||
Page under construction. Below you'll find notes that are being collected to make into an article. | Page under construction. Below you'll find notes that are being collected to make into an article. | ||
| + | |||
| + | = Apache Error Logs = | ||
| + | |||
| + | You can manually view the apache error logs by either using vim, cat, or tail. The most popular way is with tail so we will demonstrate that way. Often times, problems with the web interface will have associated errors in apache's log file. Researching this error normally leads you to the corrective action necessary - or at least provides you with an error you can post on the forums with your issue. | ||
| + | |||
| + | RHEL/CentOS/Fedora: | ||
| + | <font color="red">tail -n 100 /var/log/httpd/error_log</font> | ||
| + | |||
| + | Debian/Ubuntu: | ||
| + | <font color="red">tail -n 100 /var/log/apache2/error.log</font> | ||
| + | |||
= Fatal error: Allowed memory size of xxxxxxxx bytes exhausted = | = Fatal error: Allowed memory size of xxxxxxxx bytes exhausted = | ||
Revision as of 22:21, 28 August 2016
Page under construction. Below you'll find notes that are being collected to make into an article.
Contents
Apache Error Logs
You can manually view the apache error logs by either using vim, cat, or tail. The most popular way is with tail so we will demonstrate that way. Often times, problems with the web interface will have associated errors in apache's log file. Researching this error normally leads you to the corrective action necessary - or at least provides you with an error you can post on the forums with your issue.
RHEL/CentOS/Fedora: tail -n 100 /var/log/httpd/error_log
Debian/Ubuntu: tail -n 100 /var/log/apache2/error.log
Fatal error: Allowed memory size of xxxxxxxx bytes exhausted
Reference: Fog Version 5507 Cannot Access Host Management
Solution: Raise the web interface's memory limit: FOG Configuration -> FOG Settings -> General Settings -> FOG_MEMORY_LIMIT
It’s done in megs, so 128 = 128M, 256 = 256M etc…
After changing this, a reboot is recommended.
Manually test WOL
This is the web address to manually test FOG's WOL functionality:
http://x.x.x.x/fog/management/index.php?sub=wakeEmUp&mac=aa:bb:cc:dd:ee:ff
Where x.x.x.x is your FOG server's IP address, and aa:bb:cc:dd:ee:ff is the MAC address of the host you wish to wake up.
For instance, if my FOG server's IP is 10.0.0.7 and the target host's MAC is 14:fe:b5:df:fc:7e I would then put the below web address into the address bar of a web browser and then press enter / click go.
http://10.0.0.7/fog/management/index.php?sub=wakeEmUp&mac=14:fe:b5:df:fc:7e
After doing this, the target host will be sent a WOL packet from the FOG server.
High CPU load from web interface
There is a tool called apachetop that will list the amount of requests every file served by Apache receives, along with the total amount of data sent via that file. This tool will prove invaluable in solving web load issues.
To install apachetop on Fedora 23:
dnf install apachetop -y
Then to run it, simply type:
apachetop
apachetop is probably available for other distributions too.
High CPU load from apache
Here are threads about high CPU load:
fog-svn-5020-and-above-cpu-hammered-thread
not-sure-if-its-a-bug-or-a-feature-high-fog-server-cpu-on-dashboard
high-cpu-usage-from-multiple-httpd-processes-version-5800
high-cpu-fog-services-after-update-r5029-v6759
after-update-of-fog-trunk-php-errors
high-cpu-php-errors-after-update-to-trunk-github-7234
fog-3396-high-cpu-utilization-when-auto-update-is-running-on-the-active-tasks-page
