Fog Installer - Distro check

[Wayne Workman]

November 24th, 2016
FOG Version 1.3.0 RC-25
Git Commit da8b1a34c333ebf9a1042c72a52d6f66debad233

• Ubuntu 16.04 fully updated - fails when installing as a storage node.
  Inside lib/common/functions.sh line 1546 is a problem:

mysqlver=$(mysql -V | awk 'match($0,/Distrib[ ](.*)[,]/,a) {print a[1]}')

Also, starting the multicast manager later fails in the installation, which causes the installer to stop.

Executing the above line from functions.sh manually without sending it to a variable shows the command mysql is not present in the system:

mysql -V | awk 'match($0,/Distrib[ ](.*)[,]/,a) {print a[1]}'
-bash: mysql: command not found

To Fix both issues:

• Install mysql client and server:

apt-get install mysql-server mysql-client

• Then re-run the installer.

[Tom Elliott]

Sorry removed mysql packages from storage nodes (specifically intended to remove the server as nodes dont need server.)

Readded back.

[Wayne Workman]

November 25th, 2016
FOG Version 1.3.0 RC-26
Git Commit 1de460611f7cdba37cf245652bd4b365add65000

• Arch Linux 2016.10.01 fully updated- Installed without issues.
• Fedora 24 fully updated - Installed without issues per wiki instructions.
• CentOS 7 fully updated - Installed without issues per wiki instructions
• Debian 8 fully updated - Installed without issues.
• Ubuntu 16.04 fully updated - fails on normal installation, looks like it’s php-fpm related.

I did answer “Y” to the question about uninstalling old packages.

This is the line from the installer that shows failure:

 * Updating Database...........................................Failed!

It’s failing at lib/common/functions.sh line 63:

wget -qO - --post-data="confirm&fogverified" --no-proxy http://${ipaddress}/${webroot}management/index.php?node=schema >>$workingdir/error_logs/fog_error_${version}.log 2>&1

After the failure, running the command manually and checking the exit code shows it’s returning 8:

root@ubuntu:~/git/fogproject/lib/common# wget -qO - --post-data="confirm&fogverified" --no-proxy http://10.0.168.46/fog/management/index.php?node=schema
root@ubuntu:~/git/fogproject/lib/common# echo $?
8

I looked it up, and the exit code 8 for wget is: “Server issued an error response.”

After about 3 hours falling down the rabbit hole looking in all the wrong places, I figured out that the fog database is missing:

mysql -D fog
ERROR 1049 (42000): Unknown database 'fog'

Now, I’ve tried this with PHP 7.0, 7.1, I’ve tried ripping out all traces of php, I’ve reverted to a clean snapshot and tried over and over different things - I can’t get the installer to make the database like it should.

[Wayne Workman]

December 1st, 2016
FOG Version 1.3.0 RC-27
Git Commit f300d9d2f888568106ce25f9369910395b64d621

Fedora 25 has been released recently.
I’ve set it up and updated it, and followed the written instructions from the Fedora 24 wiki article, it installs just fine.

Ubuntu 16.04 has issues right now, but they are not FOG related, they are Ubuntu updates related. My advice for Ubuntu 16.04 users is to not update their OS, but if they need the latest FOG release candidate, skip updating the server and just pull the latest FOG source and install it as usual and it should work fine.

[Wayne Workman]

December 6th, 2016
FOG Version 1.3.0 RC-29
Git Commit 3d79051166f0a735902925c861e1e6d078158f74

Below, I installed FOG as a Storage Node on each of the below systems, and defined a pre-existing FOG 1.3.0 RC-29 server as the database server. Below are the results.

• Arch Linux 2016.10.01 fully updated - Installed without issues.

• Fedora 24 fully updated - Installed without issues per wiki instructions.

• Fedora 25 fully updated - Installed without issues per wiki instructions.

• CentOS 7 fully updated - Installed without issues per wiki instructions.

• Debian 8 fully updated - Installed without issues.

• Ubuntu 16.04 fully updated - Installed without issues.

[Wayne Workman]

December 18th, 2016
Branch: working-1.3.0
Git Commit 3e69bbb5f5ea0b573dad81581665fd15f95eda72

• Arch Linux 2016.10.01 fully updated - Installed without issues.

• Fedora 24 fully updated - Installed without issues per wiki instructions.

• Fedora 25 fully updated - Installed without issues per wiki instructions.

• CentOS 7 fully updated - Installed without issues per wiki instructions.

• Debian 8 fully updated - Installed without issues.

• Ubuntu 16.04 fully updated - Installed without issues.

[Tom Elliott]

@Wayne-Workman
December 19th 2016
Branch: working-1.3.0
Git Commit 7c1778971265813fa214318bd661574ff221635a and e436d8a4a6820956cfee6dabe6a0641b89291b74

CentOS 6 fully updated - Installed without issues per wiki instructions. (Only pertaining to iptables off and selinux in permissive mode.)

[Quazz]

@Tom-Elliott So the PHP thingy is fully resolved on Centos 6? (sorry if it has been for ages, just want to be sure)

[Tom Elliott]

@Quazz Yes. Under the working-1.3.0 branch of course.

[Wayne Workman]

December 30th, 2016
Branch: master
Git Commit f23fb06ace4df6e9e69f974244baa032d1be4e04
Release Version: FOG 1.3.0

There is a minor hiccup in the FOG 1.3.0 installer that causes problems with detecting the router address on Arch, Fedora 24, Fedora 25, CentOS 7, Debian 8, and Ubuntu 16.04. While using the -y argument of the installer, most of these distributions will go into an infinite loop on a fresh installation. They will install without the -y argument but you will need to answer n for setting a router address or type in the actual router address when it asks. Ubuntu doesn’t seem to loop for me but still the router address is wrong in the settings.

There is a workaround for all of the distributions for using the -y argument. You would simply fill the routeraddress variable manually while you start the installer. My router address is 10.0.0.1 thus the answer is:

routeraddress=10.0.0.1 ./installfog.sh -y

You can use this method for a successful unattended installation.

Other than that, everything appears to be fine.

[Wayne Workman]

Janurary 31st, 2017
Branch: master
Git Commit: 7bde5a208dc9b681a22946c3788c5f8242da9f3a
Release Version: FOG 1.3.4

Debian 8.7 - fully updated - installed without issues.
Ubuntu 14.04 - fully updated - installed without issues
Ubuntu 16.04 - fully updated - installed without issues
CentOS 7 - fully updated - installed without issues per wiki instructions

Fedora 25 - fully updated - failed
@Tom-Elliott

* Setting up and starting RPCBind.............................Failed!

Below is the error log.
0_1485920319584_fog_error_1.3.4.log

This is what shows in journalctl -xe after I run systemctl restart rpcbind

-- Unit rpcbind.service has begun starting up.
Jan 31 21:39:21 localhost.localdomain rpcbind[10604]: rpcbind: /run/rpcbind/rpcbind.lock: No such file or directory
Jan 31 21:39:21 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 21:39:21 localhost.localdomain systemd[1]: Failed to start RPC Bind.
-- Subject: Unit rpcbind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit rpcbind.service has failed.
-- 
-- The result is failed.
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Unit entered failed state.
Jan 31 21:39:21 localhost.localdomain systemd[1]: rpcbind.service: Failed with result 'exit-code'.

Also have tried uninstalling rpcbind, the service still will not restart.

[Wayne Workman]

Just so people are aware, I’m still testing the distributions. I’ve automated this & the results are available daily to the fog team only. I’ll post here with concerns.

Right now - Fedora 25 is broke, it’s a bug in the OS, nothing we can do about it. It’s related to rpcbind.

And it appears that starting last night something is wrong with the fog installation on Ubuntu 16. It’s related to the alter user command in MySQL.

[Wayne Workman]

After re-running the tests, Ubuntu 16 appears fine. Must have been a fluke. Anyone want to donate a server? I’m using an old Poweredge r410.

[Wayne Workman]

Fedora 25 and 26 are not working with the installer right now, something to do with rpcbind.

I’ve not found the time to look at it. The failure logs are here if anyone want’s to take a peek:
http://perpetuum.io:20080/fog_distro_check/Fedora25/fog/2017-07-31_04-14_fog.log
http://perpetuum.io:20080/fog_distro_check/Fedora26/fog/2017-07-31_04-22_fog.log

Of course, I’m still testing the Linux distributions that FOG tries to support, it’s all automated now. You can find daily results in the dashboard link in my signature.

[Sebastian Roth]

Seems like they had several issues with rpcbind over the last year or so: https://bugzilla.redhat.com/show_bug.cgi?id=1401561 and https://bugzilla.redhat.com/show_bug.cgi?id=1415496 (Not sure if those are related or not!)

@Wayne-Workman SElinux is disabled on those machines I suspect?!

[Tom Elliott]

@sebastian-roth I suspect it was my “fixing” code that is now “fixed” but causing a problem with latest updates. Just a guess. My fixing code just made it so fedora could install, and basically all it did was make sure the path it was looking for during startup existed. Now it looks like it’s the reverse, it’s trying to create a file that already exists, hence permission denied… (as it’s likely in use then too).

[Wayne Workman]

@sebastian-roth said in Fog Installer - Distro check:

SElinux is disabled on those machines I suspect?!

I forgot to disable it on those two VMs… that is my bad. I’ll get that fixed.

[Wayne Workman]

The issues appear to have been non-issues in the latest tests. SELinux was not set to permissive (my fault).

[Wayne Workman]

Soon, the fog installer dashboard (see my signature) will have streak counts for each item. There will be a current success streak and a record success streak.

I’ve been wanting to do this for a while, I think it’ll be fun to watch the counts stack up. I’m monitoring the files for a couple days to be sure everything is working right before I put the values into the tables.

[Wayne Workman]

Streak counts are now public.