Thank you everyone, this has been resolved. I will say the replication/node setup was the most confusing thing about fog. Everything else is straight forward. Maybe it was just me but a “Storage Nodes for Noobs” might be a good sticky post that explains how to setup a simple 2 server storage node. Other than that everything has been awesome. Thanks for all your hard work.

@Tom-Elliott the backup was my fault. To gain access to the internet I have to swap cables. When I did the “real” dhcp server gave that server a different ip. The database had the old info.

@george1421 said in FogReplicator and Storage Nodes.:

I wonder if the spike in network traffic your network admin saw was actually image replication between the two fog servers??

This is not the case, I actually have the replication service set on a 24 hour cycle, and restart the service at 2am(iirc). This was the only way to make the replication happen at a given scheduled time.

@Tom-Elliott said in FogReplicator and Storage Nodes.:

Unless you need it, the MHB Server does not need a second node. There is literally no point for it.

It’s only there because George said so

@george1421 said in FogReplicator and Storage Nodes.:

OK we need to get something cleared up. Tom and I have been chatting and we need to understand. At site MHB how many fog servers are installed master or slave nodes. I think we’ve been adding complexity because I misunderstood something

There are a TOTAL of 2 servers in the whole company, SRO-FOG-01 and MHB-FOG-01. Both of these machines are installed on our vmware infrastructures(no not the same ESXI hosts).

@Tom-Elliott said in FogReplicator and Storage Nodes.:

So:
SRO side Needs:
Master (SRO-FOG-01)
Slave (MHB-FOG-01)
MHB Side Needs:
Master (MHB-FOG-01)

Done, SRO has

| MHB-Slave  |        | 10.63.57.42 | fog  | BaLVo | ens160    |
| SRO-Master | 1      | 10.63.76.44 | fog  | RoiYx | ens160    |

MHB has

| MHB-Master | 1      | 10.63.57.42 | fog  | BaLVo | ens160    |

ok…good news…it’s replicating an image…that I dont want it to(it was set to replicate). So i know replication is working now. Now to test if I deploy a machine from MHB to see if it hits SRO at all… I will keep you updated. Need to reach out to someone in MHB

Unfortunately we imaged the same exact computers in a different office with a separate fog server with the exact same image. The office I am in they went as fast as expected. It is something this other location is is just now experiencing

Hello everyone. I am having an issue with one of our fog servers. When imaging laptops we were seeing about 1.5GB/MIN transfer rates, so a 40gb image would take 30mins. This problem seemed to arise when we moved into a new office. I have ruled out a bunch of different variables and came up with nothing, until yesterday. A coworker imaged a Desktop and it was running at 14GB/min.

FOG 1.5.5.1
bzImage Version: 4.19.1
bzImage32 Version: 4.19.1
Linux MHB-FOG-01 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
The server is cut off from all network traffic so updating is hard(thanks to our security team)

Desktop

Laptop

I have my security group wondering if Avahi is required on the Fog server, or can it be disabled. Currently the server is in it’s own vlan so this shouldn’t be an issue. I cannot see a reason this would be required, but wanted to make sure before anything was disabled. Thanks

Running Version 1.5.0-RC-9
SVN Revision: 6080

@tom-elliott any update?

Updates, the fix for enabling https works

./buildIpxe CERT=/var/www/fog/management/other/ca.cert.pem TRUST=/var/www/fog/management/other/ca.cert.pem DEBUG=tls,x509,certstore

Let me just give you a rundown of everything that happened.
Yesterday
Fog 1.5.0 RC7 With SSL with ipxe built with CERT and DEBUG
Image deploy: 1GB/min(Slow)
Host registration fails

This morning
Fog 1.5.0 RC8 without SSL with ipxe built with CERT
Host registration succeded(PC-45)
Image deploy: 8.25GB/min

Fog 1.5.0 RC8 With SSL with ipxe built with CERT
registration detection fails(doesn’t see that it is PC-45)
Host registration fails
attempting to deploy and it takes the username/pass and just drops me back to fog

If you want any more information I can test this all

@sbenson Nope still slow

EDIT: New patch, 3 different ports. Could it be because the content wasn’t actually over https previously… Registering still doesn’t work. Though I am still working off of the “Working” trunk. I will try 1.5.0 RC8 tomorrow with the debugging turned off.

@tom-elliott I’ll swap it out for another, it was working fine the last time I imaged a machine. I’ll let you know

@tom-elliott No, no mac filters setup, this is a new laptop that I have been testing only with fog. I just rebooted the server, and now its going at ~1GB/min

@tom-elliott I will reboot it(its a VM), but I also attempted to register a host and it didn’t work 3 times.
http://www.youtube.com/watch?v=sCV7x1zKBwE

Here’s something else I have found now. Deploying an image is going at 127MB/min, where previously it was going at 8GB/min