The storms have passed and all sites are back online. I’m not sure how I can verify that the image replicator doesn’t quit if a node is offline. I guess I could setup a test at home but it might not be the same. Because in the real-world OP, the primary group that had the image was MIA. I’m happy you made efforts to solve it but at this moment I cannot confirm or deny they work.

It seems ok this morning

fix after update

thanks a lot !!

@Matthieu-Jacquart yes did so just some seconds ago 😉 working again 😉

alt text

Regards X23

Ok thank you, everything works perfectly, i dont know why it was not working anymore…

The F12 thing didn’t work for me. Ctrl + F5 seems to work.

I probably should have said this earlier but,

at my building, we have a stand-alone fog server. The bandwidth chart for it works perfectly as expected.

At our administration center, we have a large fog setup. The main server has two storage nodes defined for it, and there are 14 other storage nodes that are elsewhere but managed by this main server. Only one of the main server’s storage nodes is “graph enabled”. All other remote storage nodes have their graphs disabled. This is the system with the graph issue.

RC-19 should address this issue for you more appropriately.

@Tom-Elliott Nice - thanks!

@cojohnson said in FOG Registration Error. Hostname with that name already exists:

It renamed and started working properly after i reset encryption data. However, I have had to do that every time

This time isn’t the same if you followed what I asked, because you said you previously had to press the reset button twice, I asked you to press it once.

@Tom-Elliott Using the command you posted fixed the problem. Thanks for the quick fix.

Tom says he has fixed this in RC-17, which is now released because this was a pretty major bug - in terms of hindering everyday I.T. operations.

@Tom-Elliott
Yes I confirm
Thank you

@Tom-Elliott Thanks Tom. I’ll update and confirm.

@Tom-Elliott This fix works for me. Thanks!

Fix is solved in the now released RC 16.

RC - 16 released addresses image membership issues.

@Wayne-Workman That’s fine, I just wanted to make it somewhat documented so others who may need to use it, or are seeing similar type things have something to actually look at and use going forward.

@Tom-Elliott
Thanks Tom - everything seems to be working great!

@Wayne-Workman Yep, and this is also fixed. The files and folders remaining was from order of it doing things. Once it caught a directory of either . or .. it returned without finishing.

Confirmed the issue and hopefully have it fully addressed now.

It was a bit of an issue, but ultimately very simple. The files were deleting at least on one node (where possible) but failing to iterate due to return which was meant to be changed to a continue.

After finding that out, the issue was the folder for images would still exist (the data would be removed though).

After some fairly thorough testing (I tested what I could, when and where possible) it appears I’ve finally addressed the problem. Trailing folders get removed as well as the contents of those folders.

I’m solving this, and the other, for now. Feel free to keep us posted though.