Multicasting - Not The Master Node

[george1421]

@Joe-Gill Please rerun the FOG installer for 1.4.0, there was a patch applied to the inits, but that shouldn’t address your issue (you’ll need that fix anyway, so run the installer again).

Could you post screen shots of your storage group(s), and for any storage nodes you have? These will be screen shots of the web gui pages showing the settings. I have a dev setup with 1.4.0 and it multicasts properly between subnets. This setup has one fog server as master node and a windows server as a storage node.

[Tom Elliott]

If you’re rerunnign the 1.4.0 installer, please remove the binaries1.4.0.zip file from the installer root:
(eg. from bin folder run rm ../binaries1.4.0.zip THen run the installer.

[george1421]

@Tom-Elliott Yeah, what Tom said, I forgot about the cached binaries.

[Wayne Workman]

@Tom-Elliott said in Multicasting - Not The Master Node:

If you’re rerunnign the 1.4.0 installer, please remove the binaries1.4.0.zip file from the installer root:
(eg. from bin folder run rm ../binaries1.4.0.zip THen run the installer.

#wiki worthy

[Joe Gill]

@george1421
@Tom-Elliott
@Wayne-Workman

I did rerun the installer as described.

Here are the screenshots…

I’m using Ubuntu 14.04 for the FOG server master node and a second Ubuntu 14.04 VM for the storage node. This worked fairly good last Summer with the 1.3.5 version. I had a few issues with things not getting cleared properly but I was able to do a work around and get the multicast imaging to work.

[Wayne Workman]

@Joe-Gill try to restart the service and then watch the log.
service FOGMulticastManager restart;tail -f /opt/fog/log/multicast.log

[Quazz]

I don’t know if this is strictly necessary or even related, but you may have to assign the default storage group for the image definitions.

Click on the image definition, on the left hand side select Storage group, then check the checkbox for your storage group.

[Joe Gill]

@Tom-Elliott
Well I finally tried pushing MultiCast images again…

I did run the update again before I tried the steps listed below…

@Quazz
I thought you might have been onto something with this… I went into one of my base images to check the primary group and as you noticed the primary group was unchecked. So I selected that and updated it. Than I restarted the service. It still gives me the same error…

@Wayne-Workman
I also tried running:

service FOGMulticastManager restart;tail -f /opt/fog/log/multicast.log

I got the same result… The server still says “This is not the master node” in the FOGMulticast.log file…

I tried stopping and starting things and I got the same message.

root@fogserver:/var/log/fog# tail /var/log/fog/multicast.log                    
[06-08-17 8:27:32 am] Interface Ready with IP Address: 127.0.0.1
[06-08-17 8:27:32 am] Interface Ready with IP Address: 127.0.1.1
[06-08-17 8:27:32 am] Interface Ready with IP Address: 172.16.1.17
[06-08-17 8:27:32 am] Interface Ready with IP Address: 206.127.121.78
[06-08-17 8:27:32 am] Interface Ready with IP Address: fogserver
[06-08-17 8:27:32 am]  * Starting MulticastManager Service
[06-08-17 8:27:32 am]  * Checking for new items every 10 seconds
[06-08-17 8:27:32 am]  * Starting service loop
[06-08-17 8:27:32 am]  | This is not the master node
root@fogserver:/var/log/fog# tail /var/log/fog/multicast.log
[06-08-17 8:38:43 am]  | This is not the master node
[06-08-17 8:38:53 am]  | This is not the master node
[06-08-17 8:39:03 am]  | This is not the master node
[06-08-17 8:39:13 am]  | This is not the master node
[06-08-17 8:39:23 am]  | This is not the master node
[06-08-17 8:39:33 am]  | This is not the master node
[06-08-17 8:39:43 am]  | This is not the master node
[06-08-17 8:39:53 am]  | This is not the master node
[06-08-17 8:40:03 am]  | This is not the master node
[06-08-17 8:40:13 am]  | This is not the master node
root@fogserver:/var/log/fog#

Any advice is helpful! I’ll be working on this issue today. If any of the Dev’s want to remote in to take a peak, let me know.

Thanks!!!

[Quazz]

@Joe-Gill Do you have the Location plugin installed per chance?

[Tom Elliott]

@Joe-Gill Is fogserver the actual dns name of the server? What’s the IP set to in the Storage Node’s definition?

[Tom Elliott]

Mind you the pictures you provided show the FOG Server’s IP address as 172.16.1.22 but the multicast log file you’re providing shows the IP address as 172.16.1.17

[Joe Gill]

@Quazz
I’m assuming not because I’m unaware what that is. LOL!

@Tom-Elliott
I just double checked our DNS server and it’s set to “fogserver”

[Joe Gill]

@Tom-Elliott
172.16.1.22 is the storage node IP.

[Tom Elliott]

@Joe-Gill So what is:

[06-08-17 8:27:32 am] Interface Ready with IP Address: 127.0.0.1
[06-08-17 8:27:32 am] Interface Ready with IP Address: 127.0.1.1
[06-08-17 8:27:32 am] Interface Ready with IP Address: 172.16.1.17
[06-08-17 8:27:32 am] Interface Ready with IP Address: 206.127.121.78
[06-08-17 8:27:32 am] Interface Ready with IP Address: fogserver

[Quazz]

@Joe-Gill What’s the storage node like? One installed by FOG installer or a NAS?

[Joe Gill]

@Quazz
So the storage node is a FOG storage node separate from our Fog Server.

@Tom-Elliott
That is on the Fog Server.

[Tom Elliott]

@Joe-Gill I’m confused.

The server you’re trying to have multicast is not the server you’re looking at the logs on. So of course the “fogserver” server is NOT the master node right?

[Joe Gill]

@Tom-Elliott
I’d say that’s probably our problem.

The IP Address below is the IP for the server or the storage node? I’m assuming this is wrong and needs to be changed to our server IP?

[Tom Elliott]

@Joe-Gill For multicast, yes. If .22 server is a NAS, the nas would only work for unicast images.

[Joe Gill]

@Tom-Elliott
I’ll adjust that and it sounds like it should fix this.

I’ll let ya know! Thank you!