@Sebastian-Roth

That fixed it thanks!

@Sebastian-Roth so when we go to the http://10.1.26.88/fog/management/ we get this response

but https://10.1.26.88/fog/management/ we get:

do i have a setting wrong in the master node?

@Sebastian-Roth so I ran the tail -f on the access.log and i saw 1 request come in but none after that.

I have Verified the IP address and DNS it is all correct. I use the IP address to ssh into the storage node.

Would re-running the fog setup in the storage node or the master node help here. also can i ask why we are pulling down 1.5.9-RC2 instead of 1.5.8? It seems odd that the git command is pulling a release candidate instead of the latest stable.

@Sebastian-Roth Thanks for taking a look. I lowered the max bandwidth that the replication can use so it would not crush our link and allowed it to run all night. The images have replicated and traffic has dropped off. again thanks for the help. I think everything is working now.

@Sebastian-Roth I was looking at that log and there are some images that do not need to be replicated to the other node. They are not needed at that site as the systems are not located there. can we not replicate those images and delete them from the storage node or is all or nothing ?

we have 100Mb/s dedicated link between the 2 sites. I’ll send you the links tomorrow when I get back in the office.

@Sebastian-Roth I sent the link in a chat.

are there any logs that I could provide that would help figure out what is going on here. I’m going to need the server as I have about 70 computers to image in the coming months. I would like to get this one fixed or stand up a new server whichever is going to be the easiest solution.

Yes all nodes are running 1.5.5

Then we do not use snapins. I let the replication run all day Saturday and it never stopped. I stopped before it fill the storage node completely.