Can't access FOG Management Portal after clean OS and FOG install

[acole]

Server

• FOG Version: 1.3.0
• OS: Ubuntu LTS 14.04

Client

• Service Version:
• OS:

Hey guys,

I’ve been banging my head against the wall for a day or so on this one.
I ran into an issue with a storage node earlier this week, so instead of trying to troubleshoot and diagnose, I decided I’d just start over from scratch since we did not have any prod images uploaded as of yet. I reinstalled Ubuntu and then FOG on top of it, and am running into an issue where I cannot access http://FOGSERVER/fog/management from any web browser. Of course, I installed Ubuntu without a GUI so I cannot test from localhost. However, this was working perfectly before in the same environment yesterday.

I assigned a static IP on eth0 and can ping an IP address, but no hostnames despite settings dns-nameservers. However, I can ping the FOG server via hostname and IP address from another host.

We are running this VM in VCenter5 on an ESXi host.

Any help is appreciated!

Thanks,
Alex

[Tom Elliott]

The first thing that comes to mind is firewall.

Could you please run:
sudo ufw status

[Wayne Workman]

@Tom-Elliott I’ve just created a Ubuntu 14.04 Server virtual machine at the house and tried to install FOG 1.3.4. The installation fails on “Updating Database”.

Because we’ve seen this before on Ubuntu, the first thing I checked was if a fog database was made, there is no database in MySQL called fog.

Both mysql -h 127.0.0.1 and mysql -h localhost works.

I’m guessing when you fixed this exact issue in Ubuntu 16.04, that broke the installation for Ubuntu 14.04.

[Wayne Workman]

@acole said in Can't access FOG Management Portal after clean OS and FOG install:

I decided I’d just start over from scratch since we did not have any prod images uploaded as of yet. I reinstalled Ubuntu and then FOG on top of it

If you’re starting from scratch, please use the latest long-term-support release of Ubuntu, 16.04. We know FOG 1.3.4 will install on it without any issues.

[Tom Elliott]

@Wayne-Workman What’s the cause of Updating Database failing? Have you tried the url we call?

http://fogserver/fog/management/index.php?node=schema&confirm=1

[Tom Elliott]

You must remember, the “updating database” failing on a fresh install would ultimately mean the database didn’t get created.

I’d start by taking a look at the apache error logs.

[Tom Elliott]

Please pull the latest master branch:

sudo -i
ufw disable
cd
mv fogproject fogproject_bak
git clone https://github.com/fogproject/fogproject.git
cd fogproject/bin
./installfog.sh -y

I’ve added a few more “checks” and balances to the PDODB class that should prevent the errors (if indeed you were seeing updating database failed.)

With any luck the server will install properly.

I’m still on the fence that this is a firewall issue though. This is why the command set above includes the ufw disable command.

[acole]

Thanks for all your replies.

The firewall is disabled (confirmed with sudo ufw status). I pulled the latest master branch and re-ran ./installfog.sh -y, but received the same Updating Database… Failed! message.

I confirmed that the fog database was never created in MySQL.

I can try upgrading to Ubuntu 16.04, but ran into the same issue when I installed FOG on a 16.04 VM a few days ago. Perhaps pulling the latest master branch and disabling the firewall will do the trick on 16.04. Stay tuned…

[Quazz]

@acole Could you post the foginstall error log here?

Located in your git folder/bin/error_logs

[Tom Elliott]

Is your mysql root user password blank? If it is, would you mind trying:

mysql -u root
ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '';
ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY '';
quit

[acole]

I finally got the installation to finish successfully by:

• Upgrading Ubuntu to 16.04
• Completely uninstalling FOG and deleting the fog user
• Creating the FOG database manually
• Modifying the credentials for the MySQL user in /var/www/html/fog/lib/fog/config.class.php to match the root password.

I was able to create the schema and login to FOG, so now it looks like it’s working again. No idea why FOG had trouble creating the DB on a clean install of Ubuntu…

[Wayne Workman]

@acole said in Can't access FOG Management Portal after clean OS and FOG install:

Modifying the credentials for the MySQL user in /var/www/html/fog/lib/fog/config.class.php to match the root password.

Not a good idea. You set mysql credentials and all other things inside of /opt/fog/.fogsettings
Without modifying it in this place, the next time you re-run the installer the custom changes inside of config.class.php will be erased. Without doing it right, you’re just going to have the exact same issues the next time.

See these articles for details:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings
https://wiki.fogproject.org/wiki/index.php?title=Password_Central

[acole]

This post is deleted!

[acole]

@Wayne-Workman

So, If I modify /opt/fog/.fogsettings to reflect the correct MySQL password, will that take care of it?

[TRex]

FOG version: 1.3.4
OS: Ubuntu Server 16.04 (virtual under Hyper-V)

Clean install of Ubuntu Server (partitions formatted)
Clean install of FOG

The install process seems okay except for:

• Copying new files to web folder…OK
  find: `/home//fog_web_1.3.4.BACKUP/management/other/´: No such file or directory
• Creating config file…OK

But when I get to:

• You still need to install/update your database schema.
• This can be done by opening a web browser and going to:

http://IPaddress/fog/management

• Press [Enter] key when database is updated/installed.

I use a browser to go to the IP address and get the default Apache page, but if I add /fog/management I get a blank page with a 500 error.

Firewall is disabled.

The only databases listed in MySql are (1) information_schema, (2) mysql, (3) performance_schema, and (4) sys

[TRex]

Perhaps a factor:
/images
is mounted at /dev/sda6

[Tom Elliott]

It has nothing to do with the /images location.

The problem is to deal with localhost vs. 127.0.0.1

Something switched on us apparently, as the code for handling alter user appears to have now changed in some way (even though the scripts handling this interaction hasn’t).

I’ve added a bit of a fix hopefully in the working-1.3.5:
https://github.com/FOGProject/fogproject/commit/9acc65bcb9fa6ea50facfc38615f7400b0afcc26#diff-c7d534e343a3d117623765442be0d709

I don’t know if it will work, but I suspect it will make things a little bit more managable.

[Wayne Workman]

@acole said in Can't access FOG Management Portal after clean OS and FOG install:

@Wayne-Workman

So, If I modify /opt/fog/.fogsettings to reflect the correct MySQL password, will that take care of it?

Changing stuff inside of /opt/fog/.fogsettings and then re-running the fog installer will make the settings you set become ‘in use’, plus the installer will re-use these settings the next time it’s run, be it this version of FOG or a future one.

[TRex]

@Tom-Elliott
Would installing an earlier version (after re-installing OS) work? I’m not sure how I would install a RC, don’t even know if your addition has been added to RC.

[Tom Elliott]

@TRex No.

I think if you’re willing to jump around, please jump to what will be released soon, vs going back and forth. I don’t jump back and forth unless I absolutely have to and only to find a specific cause of a change.

Since I know the ALTER user stuff hasn’t changed for quite a while, the only other thing I can think is a change in Ubuntu’s layout structures. This caused a change in representation to mysql for localhost which is why you see the code change I’ve added in the earlier posting. I’ve made this change based on my own findings in an attempt to help correct any potential issues in the future regarding localhost/127.0.0.1 representation.