Multicast config questions (FOG side) and issues and fixes

Server

FOG Version: 1.3.0-RC-14 SVN 5974

OS: Ubuntu 16.04 LTS x64

Client

Service Version: N/A

OS: N/A

Description

I did a fresh install of 16.04LTS with LAMP, SSH server and then did a git pull. The install script installed the base but didn’t install UDPCast package. Oddly enough it didn’t install the services correctly either. However, I was able to get everything working properly after some tinkering. However I’m not seeing any steps on setting this up so here are the steps I took.

If i’ts running, schedule a multicast task and you’ll be good to go. Multicast started working without issue after this.

However, is this procedure correct?

@Tom-Elliott I’m wondering if the new install script is missing something (haven’t had a chance to go through it). This was a clean build to replace my previous FOG VM and it was a comparison between VER 45XX and the one mentioned above.

It actually prompted me to ask which interface to use. It had a default and gave me the option of picking another. So when asked I put in the ensXX entry. The FOG installer did pick this up correctly as I didn’t modify this afterwards.

Actually the way I’ve set mine up is that I have internet access on one interface and the other ties to an unrouted VLAN. Everything assigned into this VLAN is destroyed in one way or another - either imaged or wiped with FOG.

We have outbound ping blocked so I won’t be able to produce those. IP address was manually assigned before and I’ve done a find and replace on the IP addresses but it should give you a pretty good idea.

I updated Ubuntu to the very latest, and I have used git to pull FOG 1.3.0 RC-15.2
I started the installer. The installer chose to use ens3, I wasn’t offered an option to choose. How did you specify an interface?

The installer completed successfully.

So this brings me to some other questions to ask you.

Do you have internet access on both networks connected to the FOG Server?
To test each interface individually using my interface names as an example is:ping -I ens8 www.fogproject.orgping -I ens3 www.fogproject.org

Also, can you give the output of these two commands if you don’t mind please:ip addr showroute -n

This could be what’s causing the issue. I know people have installed FOG trunk on systems with multiple NICs, and I know of at least one person who has a multi-homed fog server that he also uses for a router.

I can setup a multi-homed Ubuntu VM at home and see what happens, this won’t be until Monday night though.

Despite the fact that I had specified the interface the script did have an issue with the apache configuration as it added both IPs although I had picked just one interface.

Apache’s installation is just done with apt-get install apache -y basically. There’s nothing special to it and I don’t believe that FOG adjusts it’s configuration. Both interfaces ended up in the configuration because Apache’s installer put them there.

The interface you are asked is to determine the correct broadcast address FOG should use for multicasting, For DHCP configuration if you enable DHCP, and for automatic Storage Node setup if the box was being configured as a storage node, and the installer writes the interface into the fog installation configuration file. Beyond that I don’t see anything in the installer’s source that uses the interface for other things.

However the only error was in the last step where it failed to start apache.

We need the errors from that. You can go to your fogproject repository location (where you cloned/pulled to) and go into bin/fog_error you will see some files in there, one will be labeled with RC-14. This is the redirected output from the installer, it’ll have the real errors in it. Look towards the bottom of the file and please copy/paste the last 20 or so lines of that file to here please.

@Tom-Elliott Was this file originally missing? It didn’t exist in my git pull. Or is there some process which creates it?

@Wayne-Workman I actually did do sudo -I first then launched screen as root and setup everything inside this.

The only thing is that my VM is dual homed. Despite the fact that I had specified the interface the script did have an issue with the apache configuration as it added both IPs although I had picked just one interface. However the only error was in the last step where it failed to start apache.