Odd NFS issue

[Wayne Workman]

@pugnacious Take a video, upload it to youtube for us to see. From start to finish.

[pugnacious]

Alright, after a full debug capture, stepping through the steps, it shows no message related to FTP at all. I was thinking it was just too fast, but, it’s simply not there. It says Image Uploaded, restoring MBR, Resizing NTFS Volume, clearing ntfs flag, stopping fog status reporter.

Any suggestions on how I can make it report the error?

[Wayne Workman]

@pugnacious I wonder if Linux FTP commands and Windows FTP commands are the same?

That’d cause an issue.

@Developers Can you help out and give us the FTP commands that are used?

The source directory is /images/dev/<mac> and destination is /images/<imageName>

[pugnacious]

I’ve got three machines that I’ve been waiting to image. We need to put those in production and the work is already done creating the images for them. We just need to do a quick clone. I’m thinking it’s either the ftp commands or possibly the NTFS file system on the NFS share. To bypass the problem, i threw together a system and stashed it under my desk running CentOS 7 and with a decently sized hard drive. Now i’m running into another issue installing fog to the machine. It’s running trunk (svn) and it’s freezing at “Downloading inits, kernels, and the fog client”.

I did notice that the svn build was behind what i’m using on the other server. I did use the command to update the svn, and it said it was the same build. I’m going to try and download a fresh copy through git instead as that seems to be the most updated.

[Wayne Workman]

@pugnacious git and svn have identical files, both are valid. hanging at the downloading inits and such, that could be a DNS problem, or it could just be busy right now, or maybe a slow internet connection. Give it time, be patient. At my work, that normally takes about 30 seconds.

Just to get yourself going, you can manually move the image on the other server. In the web interface, if you look at the image definition, it’ll have a “Image Path” field. Rename your image to that, and just move it from /images/dev/ to /images and then try to deploy the image to those computers you need to image.

[Quazz]

@pugnacious Did you disable the firewall and SELinux on the CentOS one? From what I’ve read, they can cause a host of issues on that OS in relation to FOG.

[Wayne Workman]

@Quazz I’d actually recommend @jbob 's firewalld configuration. I’ve had zero issues with it.

https://forums.fogproject.org/topic/6162/firewall-configuration

for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done
systemctl restart firewalld.service

but yes, SELinux needs set to permissive, instead of being enforcing.
vi /etc/selinux/config
Instructions on using Vi:
https://wiki.fogproject.org/wiki/index.php?title=Vi

Change enforcing to permissive in that file.
Then to change the live setting, issue: setenforce 0

[pugnacious]

Alright, I’ve swapped out the VM to a full machine. Got it working on the latest GIT version, and found a rogue dhcp server causing issues. Now though, after taking an image of a reference machine, it gives me the error while trying to redeploy the same image to the same machine, Image Store Corrupt Unable to locate MBR.

The machine is a single disk resizable running windows 7. Any thoughts?

[Tom Elliott]

@pugnacious what version are you running?

[pugnacious]

Version: 6122 6128
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0

Edit: Just updated to check. Still no go. Rebuilding that machine from scratch and i’ll take a new reference image i guess.