• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

HTTP 500 Internal Server Error

Scheduled Pinned Locked Moved Solved
FOG Problems
3
5
1.6k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D
    Deimos
    last edited by Feb 1, 2018, 1:44 PM

    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 500

    I have no idea. Never had this before and we are running five active FOG Servers at the moment (since 2014).

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Feb 1, 2018, 2:13 PM

      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.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 1
      • W
        Wayne Workman
        last edited by Wayne Workman Feb 1, 2018, 8:17 AM Feb 1, 2018, 2:17 PM

        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.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        D 1 Reply Last reply Feb 2, 2018, 6:09 AM Reply Quote 0
        • D
          Deimos @Wayne Workman
          last edited by Feb 2, 2018, 6:09 AM

          @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?

          1 Reply Last reply Reply Quote 0
          • D
            Deimos
            last edited by Feb 2, 2018, 6:30 AM

            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 then sudo -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).

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              4/5
              Last post

            151

            Online

            12.1k

            Users

            17.3k

            Topics

            155.4k

            Posts
            Copyright © 2012-2024 FOG Project