@Tom-Elliott
For the record, I restarted the service on the server and the problem is now fixed. Thanks!

Problem solved!

Thanks!

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

I’ll let ya know! Thank you!

@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?

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

@Tom-Elliott
That is on the Fog Server.

Thanks again for providing such an excellent product!! Thank you!

I just noticed that their is not a way to set the Primary Storage Group either globally or as a group. The way I vision this feature would be a page with a drop down menu to select Primary Storage Group (IE which group you want to set as primary). Than a list of all of your images below that with check boxes on the side. At the bottom of the page would be an update button.

That would be a huge help!

Joe Gill
Townsend K-12 Schools

@Tom-Elliott
172.16.1.22 is the storage node IP.

@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”

@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!!!

Yes we do Enterprise enrollment via Google Admin.

Can you “Power Wash” them remotely?

Thanks!

I’m just curious what technique other sysadmins are doing to “image” their Chromebooks? I did lots of digging on this topic and the common way is to use a USB stick and wipe them that way. I’m looking for a way to wipe all users from the devices and “power wash” them… I’m hoping their is some kind of remote method but I’m doubtful due to what I’ve read…

Any ideas would be helpful! We added 600 this year alone and likely more next…

Thanks!

Joe Gill
Townsend K-12 Schools

@Wayne-Workman

How difficult is it to migrate from an existing FOG server / FOG storage node running Ubuntu to Centos from a FOG perspective?

@Wayne-Workman

Thanks!!

@Wayne-Workman

Your suggestion worked!

You might add something to the WIKI to remind those who have passwords on their MYSQL databases to adjust the command accordingly. It took me a minute to figure that out.

mysql --user=FOG_USERNAME --password=YOUR_PASSWORD -D fog

Thanks!

@Wayne-Workman
@Tom-Elliott

Ugh… Yes, I had a password set. I figured out how to get in now. MAN pages are great, when we read them. LOL!

Thanks for making me think!

Cheers,

Joe Gill
Townsend K-12 Schools

@Joseph-Hales

I have not tried a different kernel yet.

Is their a wiki on how to change the PXE kernel?

Thanks!

Joe Gill
Townsend K12 Schools

@george1421

Well the firmware upgrade did not resolve the issue. I did notice their was an old post on this subject from 2005. It sounds as though the HP NIC’s didn’t function the best with FOG PXE booting. I only have 3 of these machines so I may just rebuild them the long way. At this point, it probably makes most since.

Is their any way possible to PXE boot to a wireless card? They have one of those as well…

Any other ideas, please shoot them my way. Thanks!

Cheers,

Joe Gill
Townsend K-12 Schools

@george1421

Good call! I’ll try that.

@george1421

The funny thing is they all share the same switch as other models that PXE boot fine. All of the ports are configured the same way.

Server

• FOG Version: 1.4.0
• OS: Ubuntu 14.04

Client

• Service Version: 0.11.12
• OS: Windows 7 Pro

Description

I seem to be experiencing issues with PXE booting on one segment of our network. I don’t know whether it’s network related or not. I have other machines near by that seem to network boot fine. I can boot the same machine type from another segment of our network fine as well.

Here are the errors…

This one never finishes loading. It locks at the step below.

Thanks!!

@Tom-Elliott
I didn’t think so… I checked my settings file and it didn’t have any listed. The crazy thing is I unicasted just fine from the FOG server with this going on. I can’t seem to get multicast to work but that appears to possibly be something else.