Install w/ -y Skips Database Now

[dholtz-docbox]

@Tom-Elliott : that’s just for the localhost? I am running that from the machine where FOG is installed. This server is on an isolated network, so it’s easiest to do from the machine itself. Is this invalid? I only thought about trying this, knowing that, when I wget the management page, if the database isn’t installed, I am told that my “FOG database schema is not up to date” and everything else that comes with schemaupdaterpage.php. I suppose the other thing this page mentions is that my database connection appears invalid, and that I should check the credentials. Let me double check these, I assumed they would be fine as I haven’t changed anything other than updating our FOG git mirror.

-Dustin

[Tom Elliott]

@dholtz-docbox 127.0.0.1 = localhost

[dholtz-docbox]

@Tom-Elliott 0.0.0.0 and 127.0.0.1 resolve the same, unless I am mistaken about something. That said, that was just for my sample wget and curl calls, which unfortunately return the same output when switched to 127.0.0.1.

[dholtz-docbox]

Just as an update, as I am not sure what the hitch here is.

In an attempt to quarantine the issue, these are the steps being used.

Pre-installation:

• Starting from a blank Ubuntu 14.04.5 Server LVM installation
• Skipping internal bootstrap

Post-installation:

• Login
• Create /opt/fog directory
• sudo apt-get install git
• sudo git clone https://github.com/FOGProject/fogproject.git /opt/fog/dist
• Copy .fogsettings from configuration server
• cd /opt/fog/dist/bin
• sudo ./installfog.sh -y

After installfog.sh successfully completes - as denoted by the * Setup Complete prompt during FOG installation - I then try to access the fog database, using mysql -u root -D fog. At this point, I am prompted the following, “ERROR 1049 (42000): Unknown database ‘fog’.”

I am unsure what is causing this, but it simply appears, to me, that commons/schema.php isn’t being applied. I have attempted a handful of things, as well as begun digging through the repository in an attempt to better understand this. Unfortunately, I have not figured out a manual way to install the database, nor a way to identify what may be occurring that would cause this.

Further, if there is another variable I can cut down on, please let me know. I am trying to replicate the issue with as few of our own variables mixed in as possible. At this stage, we have not bootstrapped the system, and have only installed the necessary package. I have also tried running sudo apt-get update && apt-get upgrade -y --force-yes before proceeding as well, to no success. This is also using the git HEAD, so there should be no concern about our git mirror of the FOG Project intervening either.

No matter what I do with the latest RC, I cannot get the ‘fog’ database to install - outside of manually running the create+insert script myself.

Is there a way to manually install the database (read, not relying on foginstall.sh) just to validate that everything works. I suppose that’s moot, as I shouldn’t be in control of creating the schema anyway and the installer should always handle it. Just in this current state, I am curious if everything would work if I could install the database. If the -y switch is working as designed, I guess I am curious where this region of logic is handled so that I may further diagnose what the issue might be. My hope in manually doing it was that it would validate whether there was another issue at hand. That said, if there were another issue at hand, you would think the installer would fail.

I feel a little lost with this one, given that RC15 worked without a hitch, and that everything is “installed” successfully with RC21. Yet, when I go to query the ‘fog’ database, am told it doesn’t exist. Thus, indicating to me that some action wasn’t triggered/routed correctly, or that something error’d out and was silently handled.

I will be back on this tomorrow morning - I have to go vote for now.

-Dustin

[Tom Elliott]

@dholtz-docbox this makes me wonder if ufw is running? I don’t know why buy it almost seems, to me, the local link is restricting to a socket, not allowing connection via TCP.

Can you post the contents of your MySQL config file? I don’t know where it will be located. Typically it’s under /etc/mysql/my.cnf or /etc/my.cnf, but it is Ubuntu.

[Tom Elliott]

RC-22 officially released.

I don’t think it will fix the issue as you were seeing it, but one never knows.

I would more prefer a remote session if this is still not fixed for you though.

[Wayne Workman]

@dholtz-docbox For the last month or so, I’ve been quality-checking Ubuntu 16 to see if it installs without issue or not, and the last time I’ve checked it was fine. Is there a legitimate reason you’re still installing Ubuntu 14, or can you move to the new long-term-support version of Ubuntu?

[x23piracy]

@Wayne-Workman said in Install w/ -y Skips Database Now:

@dholtz-docbox For the last month or so, I’ve been quality-checking Ubuntu 16 to see if it installs without issue or not, and the last time I’ve checked it was fine. Is there a legitimate reason you’re still installing Ubuntu 14, or can you move to the new long-term-support version of Ubuntu?

Hi,
i am also still using Ubuntu 14, when i connect with ssh i see the following:

To upgrade to a supported (or longer-supported) configuration:

* Upgrade from Ubuntu 14.04 LTS to Ubuntu 16.04 LTS by running:
sudo do-release-upgrade

OR

* Switch to the current security-supported stack by running:
sudo apt-get install linux-signed-generic-lts-xenial linux-signed-image-generic-lts-xenial

and reboot your system.

someone around who did “sudo do-release-upgrade” from 14 to 16 without any issue? i also would like to update but i am a little bit afraid from getting any crashed, sure i can make a complete backup but i like to talk about in first instance.

Would i be better to switch to current security-supported stack and make a apt-get update / upgrade first?

Regards X23

[Wayne Workman]

@x23piracy Upgrading a FOG server running on Ubuntu scares me. Honestly. So many people have had bad experiences with it.

However, Tom says he has the upgrade issues worked out.

You’ll need to change /opt/fog/.fogsettings to include gawk in the packages list, and you’ll need to move to PHP 7 if you haven’t already, and remove any PHP 5 stuff in the .fogsettings file.

@Tom-Elliott anything else?

[Tom Elliott]

@Wayne-Workman I only said that I know how to perform an upgrade. Each system is different though.

Essentially the best steps to perform,

Do the release upgrade.

remove apache and php entirely by:

rm -rf /etc/{apache,php}*
apt-get purge php5* libapache*

Run the installer and all should work fine.

I know this sounds simple, but it took us “how long” to finally kind of get a track on it? I have not made these assumptions in the installer.

[x23piracy]

@Tom-Elliott if this works can i do the same with a storage node?

[Tom Elliott]

@x23piracy it isn’t a can I it’s a you should. Php and Apache is always installed regardless of node or server install.