@Quazz After updating the bandwidth to 10000, I can now update it to 0 in order to remove the limit. The replication is now working fine and I can track it on the disk Usage on the dashboard.
I should have been more careful about the settings before posting … Thanks for your help guys !
@george1421 Yes there’s a little issue on that point : If the Node you just installed is added automatically in the GUI (it appears in the list of storage nodes with its IP) then the bandwidth is set to 0 by default and no problem with that.
But if you have to create the new storage node manually (it was the case for my second one) then you’ve got the following error :
So my trick was to set a value like 10000, update the Node, then reset to 0 manually and Update again.
@Quazz After updating the bandwidth to 10000, I can now update it to 0 in order to remove the limit. The replication is now working fine and I can track it on the disk Usage on the dashboard.
I should have been more careful about the settings before posting … Thanks for your help guys !
@quazz Damn yes you’re right for the bandwidth, I set it to 1 because ONLY for this node, it doesn’ allow me to let it to 0. But when thinking about it that was stupid ahah.
I did that because when I installed the first node, it appears automatically on the GUI with his IP address. Then I just had to rename it adn the bandwidth was automatically set to 0 (no limite if i’m right).
But for the second node, I don’t know why but I have to create it manually with all its settings, and with this method I can’t let the bandwidth to 0… So I let it to 1
Anyway I try to make the installation again with a valid value and keep you in touch 
@Sebastian-Roth Yes I can admit that it doesn’t look like an error like this, but I did exactly the same process for the first node I installed. There were about 6 images on it and the replication on the node took about 15 minutes. This new node’s got only 2 images and replication is still running after 30 minutes what makes me say that there’s something wrong.
@george1421 There it is :
Hello,
I have a FOG master server with two “internal” storage nodes, one mounted on /images and the other on a /images2 repository that i’ve created.
I added an external storage node associated to the primary master node (/images) : Replication works fine
But then I have to add a second external storage node associated to the secondary master node (/images2). When I proceed, I can see it on the dashboard :
In the fogreplicator.log, I can see that the replication start between the two nodes because of the following lines :
And on the side of the /images repository of the node, I can see that folders have been created for each images to replicate :
But unfortunately, it seems that the replication fails during processing because the Node usage disk stays on 100% Free on the dashboard. When I come back to the fogreplicator log after waiting 10 minutes for it to rerun, it appears that the replication is running and doesn’t want to finish :
Any suggestions would be helpful 
PS : Sorry for the red frames but I can’t disclose all of the information
Ok I don’t know why, but creating a new user on the GUI made the disk usage come back !
Maybe it has updated the db ? Really don’t know but IT WORKS ! You can mark it as “Solved”.
Thanks for your help
@tom-elliott That’s my master server so yes, this is the same node that I access the GUI from.
@george1421 @Tom-Elliott Hi guys, just successfully reran the script after adding the fog_server_ip for the $no_proxy variable.
So I’m now on 1.5.0-RC-6 but still the same problem, no Sotrage node disk usage on Dashboard …
@tom-elliott I don’t have access to the server now but my problem is exactly the same as this post, only difference is that in my case that’s a fresh install and not an upgrade :
What do you mean by Information stored on the GUI ?
And we talked about proxy because of the “Backing up database” failed that I have when trying to rerun the script.
@george1421 Yes the problem is that I have no longer access to the server until monday morning… I did this config on a VM to post you the result but that’s not the real server (http:// is set on the good one).
So I will add the fog_server_ip for the no_proxy variable on Monday and i’ll keep you in touch