Image not syncing between nodes
-
@msi said in Image not syncing between nodes:
File or path cannot be reached.
What is the output of this command on the master node:
ls -laht /images/Win_10.1709
What is the output of this command on the non-master node:
ls -laht /images
Please remove any sensitive information from the output before posting your reply.
Also, you might want to look over this article as replication is affected by these things:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
Try to test FTP to your storage nodes.Also look over this, try to test the MySQL connection to the storage nodes:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Easy_.26_quick_MySQL_testAlso, we should have a little more of the replication log from the master node - again please remove any sensitive information before posting.
-
@wayne-workman Hi
Created the image from branch node, It hasn’t been transferred to Master yet (Win_10.1709 and Laptop2.1). I think thats the problem.
output for ls -laht /images is:
-
@msi I’m not sure if we have the terminology correct here, but you can only capture to a master node in any single storage group. Images only replicate from master nodes to slave nodes.
If you captured an image at a remote branch, that is only possible if the remote branch has a full fog server. Are you expecting that image to replicate somewhere maybe back to HQ?
-
@george1421 yes, that is correct.
@george1421 said in Image not syncing between nodes:
@msi I’m not sure if we have the terminology correct here, but you can only capture to a master node in any single storage group. Images only replicate from master nodes to slave nodes.
I have 7 node storage that are running fog 1.4.4. One master with the same fog version. I have created two other images (Win_10.1703 and Laptop) from a branch that has one of those 7 nodes. And those got transferred to Master fog server but the latest two aren’t transferring there.
If you captured an image at a remote branch, that is only possible if the remote branch has a full fog server. Are you expecting that image to replicate somewhere maybe back to HQ?
Yes, that what I am trying to accomplish.
-
@msi Where is your master fog server? HQ or the branch?
Did you capture the image created at the branch onto a storage node at a branch? I think I’m missing something when reading your post.
-
@george1421 Yes, I captured it at a branch; which located at NJ. Master is located at CA
-
@msi do you have a multi-master fog system setup? Perhaps both nodes are configured as masters in their very own storage groups and you have setup image sharing between the groups?
-
@wayne-workman no, I have only one master and 7 storage node
-
@msi said in Image not syncing between nodes:
no, I have only one master and 7 storage node
Captures have always and only gone to Master nodes during capture. So capturing to a non-master is not possible.
Please share with us a screenshot from yourweb gui -> Storage Management
page. -
-
@msi Ok, now verify that the image captured properly on the master node. I don’t know your image’s name, but you would check by changing into it’s directory like this:
cd /images/<image name here>/
and then running this command:
ls -laht
-
@wayne-workman the two images doesn’t exist on master. I can see those on NJED45; the place where I created those two images.
Below picture is from NJED45Below picture is from Master
-
@msi Then I would ask you to ensure the IP addresses for your nodes are correct in the Storage Management area. Also check the IP addresses set on the nodes via CLI with this command:
ip addr
-
@wayne-workman
NJED45Master
-
@msi Please verify the IPs via CLI too. The command is
ip addr
-
@wayne-workman
NJEDMaster
It matches. -
@msi What happens when you go to http://10.134.200.230/fog/management using your browser?
-
@wayne-workman Below Message
‘This is a storage node, please do not access the web ui here!’ -
@msi Well then something is really messed up here. Going to ask for help from the @developers and @moderators for ideas.
-
@wayne-workman Sure, thanks