Replication not working. Says storage node "does not appear to be online"
-
What does the storage node configuration look like for the “Park City FOG VM Server”? Can the master fog server ping that server at the IP address listed in the storage node configuration?
Is the “Park City FOG VM Server” a real fog storage node or is it a NAS configured to look like a storage node? (I probably already know the answer, but it never hurts to ask).
-
Also, what is the “latest fog trunk build?”
I need exact versioning to properly help you.
-
@kafluke said in Replication not working. Says storage node "does not appear to be online":
and when I was done the storage node immediately showed up on my master FOG server.
@george1421 when this happens, it means the fog installer did it. When you run the fog installer and choose storage node mode and supply the correct information, the fog installer will add the new storage node automatically to the list of storage nodes. It’s a feature of the FOG Installer I helped out with.
-
@tom-elliott Web interface says 1.5.0. I checked out dev-branch and installed today.
-
@george1421 It’s a VM running CentOS 7 and I ran the installer and chose “storage” when prompted. Yes I can ping both ways
-
- Did you set SELinux to permissive as the CentOS 7 tutorial outlines?
- Did you configure FirewallD as the CentOS 7 tutorial outlines?
Tutorial:
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7 -
@wayne-workman Yes it has been set to permissive on both servers
-
Okay I feel really stupid. Replication was not working because the server system time was not set correctly. Go ahead and marked this solved
-
@kafluke You don’t need to feel stupid. I wouldn’t have expected system timing to have mattered either. Just another tool in the arsenal that is helping us troubleshoot and fix people’s issues.
-
Yeah I’m really surprised time has anything to do with it?? @Tom-Elliott is time involved anywhere? I know that checksums are not affected by access/modification times at all.
