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!
-
@Kevin-Talbot I’ve deleted your post… security. Please use PM.
-
/images was not gone. The windows NFS share was mounted on top of the /images folder. No data was lost. Unmounted and bam all the images were back.
-
@Kevin-Talbot Back to your original question, since your only requirement is to “utilize Windows 2012 server”
install Hyper-V, create a VM, install linux on them, install fog in normal mode - change the mysql settings in /opt/fog/.fogsettings to point to the primary fog server. Change DHCP/ProxyDHCP at each site to point to the newly created fog VMs. Add the new storage nodes to the primary server.
Snapshot along the way.
-
Thanks to Tom who found all my images, life saver!
I have scrapped the windows NFS idea and just made a standard node on Ubuntu which I now have running at a remote site on a separate subnet but now need a little help/advise please?
I have added the Location Plugin
I have created a second storage group and put this node into it.
I then added a new location and added the node to it.
I have copied 1 image over manually to this new storage node, configured the DHCP at the site to point at the main fog server.
Went to site with a box and attempted to image it, PXE was intermittently loading from the main server across the WAN but did load and allow Full Registration albeit it was slow.
I chose the new location during registration.
It started imaging but it was slow, around 500m/min
So question is was it actually pulling from the new local node or pulling accross the WAN?
Only other thing which I should mention, I did not tick the TFTP from this node box under the location?
Please help?
-
@Kevin-Talbot said:
Only other thing which I should mention, I did not tick the TFTP from this node box under the location?
It was probably pulling from across the WAN.
Can you give us a screenshot of what you see when you click “Storage Management” ?
Can you also give us a screenshot of what you see when you click the Location Plugin ? -
Hi Wayne, see attached:
-
Just realised the Images can’t be in more than one Storage Group and the image I was trying to use is tagged to the Default storage group. Could that be the issue?
-
@Kevin-Talbot said:
Just realised the Images can’t be in more than one Storage Group and the image I was trying to use is tagged to the Default storage group. Could that be the issue?
Images can belong to more than one storage group - but you have to set this -but do not just pounce on this statement like it’s your answer - it’s not the answer.
Both of your storage nodes are in their own storage group. This means that replication will not occur between the master and the others. Change it so that both storage nodes are in the same group - and then the master node in the group will replicate images to all other nodes in the group.
OR - under the image’s membership (on the Image Management page), you can assign the image to several storage groups. However - it will only replicate to master nodes, and you don’t have 24066-fog set as a master of it’s storage group, that would need changed.
You cannot do BOTH things I’ve suggested here - that will break stuff and probably cause data loss. You have to pick one method or the other.
-
Thanks Wayne however I can’t see how you can add an image to more than one storage group under Image Management, its a drop down box that only allows you to choose one storage group?
Also can someone tell me what the “TFTP from node” check box does under Location Management please?
I assume if I tick “TFTP from node” the node needs the TFTP parameter adding to the node install script otherwise it won’t work?
-
Also, I have now got further:
I have setup another node called “271-fog” and created a storage called “Replication”
Added 271-fog and 24066-fog to the “Replication” storage group
Set “271-fog” as the master for the “Replication” groupI have created a test image and tagged it to the “Replication” storage group
Run an upload from a host tagged to the test image
Image has successfully appeared on “271-fog” but it is not replicating to “24066-fog”Any ideas why its not replicating?
-
-
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.
