HTTP 500 Internal Server Error
-
FOG 1.4.4, Ubuntu 16.04.
I cannot connect to the WebUI. The browser returns the following error message:
This page does not work
10.XXX.XXX.7 can not handle this request right now.
HTTP ERROR 500I have no idea. Never had this before and we are running five active FOG Servers at the moment (since 2014).
-
We’ve seen a sharp uptick in these issues related to ubuntu in the last weeks. There is a document that should give you guidance. https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy
You can confirm by checking the apache error log
tail /var/log/apache/error.log
If you see an errors that have pdodbc and insert field failed. That is a good indication that ubuntu has been tweaked. -
I’d suggest any new fog servers that you build use Debian 9 or whatever the latest Debian is. FOG has the simplest installation on Debian, and over the time that I’ve been monitoring - Debian has had the least amount of problems with FOG.
-
@wayne-workman said in HTTP 500 Internal Server Error:
I’d suggest any new fog servers that you build use Debian 9 or whatever the latest Debian is. FOG has the simplest installation on Debian, and over the time that I’ve been monitoring - Debian has had the least amount of problems with FOG.
Thanks for the quick response. So, just running the install.sh again will help? The data is retained?
-
So, the mysql-fix postet by Tom Elliot helped. No need to rerun the fog installer.
@tom-elliott said in Ubuntu is FOG’s enemy:
TLDR; … or run the ALTER USER syntax shown below.
As a note, it seems this problem is specific only when the mysql account is the
'root'
user AND the password is blank.The “fix” if you must do it manually is to open a terminal and obtain root:
Super (Windows Key) + T thensudo -i
(in most cases).From there, open mysql with
mysql -u root
NOTE: MySQL MUST be run with ROOT.
Run:
ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY '';
AND
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';
It’s okay if one of them fails. This is going to fix Most people’s issues.
I would highly recommend removing the unattended-upgrades as many of these “sudden” issues came as a security patch ubuntu pushed out. By default Ubuntu typically set’s this for you as enabled and it can cause havoc on you as you (the admin) may not have “done” anything.
To prevent this problem from happening in the future you could run:
apt-get -y remove unattended-upgrades
(AS Root again).