Multicasting - Not The Master Node
-
@Joe-Gill What is 22? What is 17?
-
.17 = fogserver (Where our main fog installation is.)
.22 = fog storage node. (Where FOG Storage Node installation is.) -
@Joe-Gill Does “Where our main fog installation is” have the images as well?
-
@Tom-Elliott
Negative. That /images directory is empty. -
@Joe-Gill So what is the storage node? Is it a nas?
-
@Tom-Elliott
Yes essentially. But it is a running FOG Storage Node. -
@Joe-Gill So it has a full install of FOG?
-
@Tom-Elliott
Yes it does. The storage node version. -
@Joe-Gill Can you check its multicast error logs then? Will be more useful info.
-
@Quazz
This is all that’s on the Storage node multicast.log.[07-27-16 1:10:11 pm] | Sleep time has changed to 10 seconds -
@Quazz
And the log from the server…[06-08-17 10:16:48 am] ================================== === ==== ===== ==== === ========= == === == === === ======== ==== == ==== === === ======== ==== == ========= === ==== ==== == ========= === ======== ==== == === === === ======== ==== == ==== === === ========= == === == === === ========== ===== ==== ================================== ===== Free Opensource Ghost ====== ================================== ============ Credits ============= = https://fogproject.org/Credits = ================================== == Released under GPL Version 3 == ================================== [06-08-17 10:16:49 am] Interface Ready with IP Address: 127.0.0.1 [06-08-17 10:16:49 am] Interface Ready with IP Address: 127.0.1.1 [06-08-17 10:16:49 am] Interface Ready with IP Address: 172.16.1.17 [06-08-17 10:16:49 am] Interface Ready with IP Address: 206.127.121.78 [06-08-17 10:16:49 am] Interface Ready with IP Address: fogserver [06-08-17 10:16:49 am] * Starting MulticastManager Service [06-08-17 10:16:49 am] * Checking for new items every 10 seconds [06-08-17 10:16:49 am] * Starting service loop [06-08-17 10:16:49 am] * No tasks found! [06-08-17 10:16:59 am] * No tasks found! [06-08-17 10:17:09 am] * No tasks found! -
Could I create a new storage node (.17). Give it the IP of our server (.17). Set it to slave. Let the images migrate back to the /images directory on the server. Then after all images are copied set the storage node (.22) to slave mode.
Would this work? Or is their an easier/safer method?
I’m stuck at the moment with Unicast. I’m trying to push 10 images and my time remaining is 6:30:00… I’ve got about 300 more to do!
Thanks!
-
@Joe-Gill Are you sure the “storage node” isntallation is “storage ndoe?” It seems to be looking at it’s own database. (BTW, fogserver should NOT be the same on multiple systems.)
-
@Tom-Elliott
What’s the easiest way to verify? -
Well I can tell you that when I navigate to our 172.16.1.22/fog in the web browser it says this…
This is a storage node, please do not access the web ui here! -
@Joe-Gill so 22 is supposed to be the master node but the logs you’re giving us are for .17? Is 17 the main GUI or the storage node? Please understand I’m trying to help but getting totally conflicting information.
-
@Tom-Elliott
Interesting…
17 is supposed to be the master node.
22 was set to the master node somehow.17 is the main GUI.
22 is the storage node.I think I know what happened. Initially I had a FOG server, a FOG storage node, and a FREENAS storage server setup. FREENAS was giving me problems so I nixed it. When that happened I reset my Storage Node on the server. I believe I misunderstood the syntax of what the Storage Node IP was on the gui and put the wrong IP in there.
Does that help?
-
Any thoughts on this?
I’ve been stuck unicasting all day… My 10 machines still haven’t finished cloning… This lab is only on a 100MB switch though. ugh!
-
@Joe-Gill My my thought are this:
Why do you have 2 fog servers setup on the same subnet? There must be a technical reason for this?
What precisely do you have configured for dhcp option 66 {next-server}?
If you have dhcp option 66 pointing towards 172.16.1.17 how will the storage node 172.16.1.22 ever be used if the location plugin is not installed and the clients homed to that server?
But more to the point why do you have 2 fog (devices) installed on the same subnet?
-
As for the 2 FOG devices on the same subnet… I had no idea it was an issue. We have plenty (256) of subnets available. I never had a single problem multicasting last year with this setup like this. Only occasionally would I have to go in and manually clear the FOG que when I had something else (bad network cable / task didn’t delete properly / ect) fail and needed to reset things.
We don’t have the FOG server serving DHCP. We have a Windows server doing this (I’d rather go Linux but the other admin does not.) So as for option 66, I don’t know. The only thing we set on the DHCP server was for PXE to point to our server IP (172.16.1.17) in DHCP.
