@Sebastian-Roth Thank you again for your reply.

I believe I found the fix. The colleague was not using “quick registration” to register the MAC addresses into the database before imaging. It seems that the Master needs to have the MAC address of each client in the database to delegate imaging tasks to each node.

I have a full bench of computers now (registered) and they are now pulling from all 8 nodes equally and tasks are showing. Thank you again.

@Sebastian-Roth It does not show up on the dashboard or in the task list, no.

But the bigger issue is that all of the computer imaging is only pulling from the Master when I have 8 other storage nodes. It is flooding the master when the master is only supposed to have an 11 client maximum. And the deployment task seems to not be created although it is deploying.

@Sebastian-Roth Thank you for the reply!

I can manually schedule tasks and they show up in the task list. But when I pxe-boot computers to the FOG network and depoy an image, it doesn’t show any active tasks for the deployment even though it’s deploying 25 copies of the same image from the master server.

Hello,

Before I begin, here are my specifications:
OS: Linux/Debian
FOG Version 1.5.8

I’m kind of at a loss here. I have a FOG setup with a Master and eight storage nodes. As of this morning I noticed that whenever I started imaging, all of the computers would connect and deploy from one of the storage nodes. Thinking this was odd, I disabled this node in the Storage Node settings of the FOG Dashboard just to see what would happen. Then the computers all began connecting to only the master node and began to oversaturate it. I currently have ~25 computers connected to FOG and imaging from the master node and they’re all pulling about 150MB/min (very slow compared to how it usually runs).

What even more bewildering is that there are no tasks showing up on the FOG dashboard either. It’s still showing that theres 68 free spots available and no activity at all. I also only have an 11 Max Client limit on the master and like I said, I easily have 25 computers connected to it pulling from the master. I have tried rebooting the master and every node and no luck.

All Linux and FOG services seem to be up and running after running sudo systemctl

Any ideas on what may be going on?

Thanks in advance,

@george1421 Thanks for that info!

So, disabling the Ubuntu firewall shows Apache2 Ubuntu Default page showing that it works. It is stating "This is the default welcome page used to test the correct operation of the Apache2 server after installation on Ubuntu systems. "

But still no fog managment dashboard page. This would be the WEB_SERVER right? Doesn’t it automatically generate this at setup?

My colleague and I are having difficulty getting our FOG server dashboard to generate and we’re wondering if it may be something with our current Static IP/DHCP setup.

We just installed FOG on Ubuntu Server LTS and we wanted to reserve the IP address(es) of the nodes to be static IPs. We are adding this FOG network to an already existing business network connection and we are not using FOG for DHCP and we wanted to defer to our regular DHCP server for the office. Sorry if this is a dumb question, but can we set static IPs on the computer side or would it need to be done on the DHCP server side?

We ran sudo nano 01-netcfg.yaml and our netplan is as follows:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp59s0f1:
      dhcp: no
      addresses: [10.50.0.218/24]
      gateway4: 10.50.0.1

I am able to ping 10.50.0.218 with no packet loss, but when I attempt to go to 10.50.0.218 or 10.50.0.218/fog/management in a web browser I get no connection. Isn’t the dashboard managment link supposed to automatically generate once installation is complete? What could possibly be going on here?

Thanks all!

@george1421 Interesting. Thank you for that info. I have only ever done Quick Registration with FOG which seems to identify and register the hosts by their MAC addresses. I figured since FOG was handling DHCP and assigning IPs to MAC addresses anyways (is this even how it works?), it wouldn’t need DNS.

So it uses the MAC addresses as a DNS name?

@george1421 Thanks for the reply! That info is helpful. I am currently integrating a separate FOG server at my work. The first one was set up by someone who doesn’t work here anymore and it has a DNS server.

But even if FOG is on an isolated imaging network, I’m still struggling to understand why DNS would matter? What would it possibly need DNS translations for?

Please excuse my ignorance as I am fairly new to servers/networking in general, but why would FOG need a DNS server if it’s set up for just local imaging? Isn’t it just assigning MAC addresses to IP via DHCP and pushing the image that way? Why would FOG need to translate IPs into domain names and vice versa? Is it for the FOG dashboard maybe?

Thanks all!