FOG 1.2.0 on Ubuntu 12.04 LTS but now want to add Windows 2012 NFS nodes, can't get it working please help!
-
-
Wayne I have this:
-
@Kevin-Talbot Oh then nevermind me, I apologize. The features I’ve teased you with are only available in FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
I swear I don’t do this on purpose, lol. I’ve never used 1.2.0 in production. From the get-go, I jumped straight into the trunk versions due to a specific feature that my organization needed.
Also, there’s a service called FOGImageReplicator. It uses FTP. Verify you can FTP from the master node to the non-master nodes via CLI. There are examples on doing that here: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP
-
I think the issue I have is the second part of this but I cannot edit the my.cnf file (permission denied) on a node:
-
I have tested FTP from “271-fog” (master in “Replication” storage group) to “24066-fog” and it logs in successfully with username “fog” and "password from storage management screen for “24066-fog”
-
Really need to get the replication issue nailed now please if anyone can help?
If I add nodes to Default storage group they replicate from the master fog server but if I add nodes to the Replication storage group they do not, even though there is a master for this group with images present?
-
Root or sudo never gets permission denied. Failures, sure… But permission denied, never. Try with sudo.
sudo su
@Tom-Elliott can you explain how BASIC replication works with a master node and regular node within the same group?
My understanding is the fog replicator manager must be running, and via ftp it looks at the DB and replicates from a master to other members of the group via FTP.
Kevin, ensure firewall and SELinux are off on the relevant nodes. Make sure your pathing is correct for the non-masters, make sure there is space on the non-master destination partition (some distros have several default partitions. Its not like windows at all). Also make sure the pathing on the master is correct. Is the other node a NAS or an actual Linus server or a windows server (yes it matters)?
Anything you can tell us that is unique about your environment would help. External firewall? Intrusion detection system? Proxy?
-
Apologies - the service is called FOGImageReplicator Make sure that’s running, and try to restart it.
-
@Wayne-Workman said:
Apologies - the service is called FOGImageReplicator Make sure that’s running, and try to restart it.
To touch on this. I had this problem and by rebooting this on the node first, then the node master last - it seemed to fix it. But I havent had this issue on the latest updates (trunk versions) of FOG.
-
I’ve also seen where the location plugin can break replication
Remove that, and see if replication will start or not.