@walkerit To expound a bit on @Quazz 's comment, I ran into this yesterday myself. There’s two different config locations that I found needed to be updated. One of them I’m led to believe will only come into play if you update the server, but the other (export? https://wiki.fogproject.org/wiki/index.php?title=Change_NFS_location) is what was causing my permission issues.

Hope that clears it up when you do change your storage location.

Philip

An update, solved.

There were two issues.

The timezone issue was resolved by setting the Centos system to to UTC and Fog’s ‘TZ INFO’ setting to UTC. Don’t know why setting to ‘UTC’ worked and not with the same settings using ‘EDT’ <shrug>. Once we catch up on our imaging I’ll try to revert back to our timezone and see if this is merely an annoying warning or if it still causes a fatal error.

The second issue was the user ‘fog’ passwords were not consistent, system vs. Fog account. So when Fog completed the imaging and during the ‘Updating Database’ routine the ftp login failed and threw ‘Error returned: Type 2’.

0_1528461696724_IMG_0807.JPG

We are now able to image Window 10 clients for the first time! Thanks everyone for your help!

Scott

@timo You can restart apache2, the effects won’t last long though. When you can get into the web gui, you should go to Storage Management -> your storage node -> Max Clients and set this to something like 1 or 2. This will limit how many snapins run at once - and will allow your fog server to operate normally while the snapins run.

@stylus3530 In fact, you can deploy a 1.2.0 image and re-capture with 1.5.2. All you need to do is not allow the image to boot. Once deployed, immediately re-capture and all should work fine.

@kleber I’d recommend removing the background image via the GUI under Settings | iPXE General Config. I just removed the background image name from that field entirely. The default background prevented certain machines from being able to boot for me as UEFI. Figure its a quick enough thing to check.

Are there other machines that do boot ok with your setup or are you not able to boot any machine via iPXE?

Do the machines you have issues on have any BIOS settings specific to PXE booting (enabling it, authentication, etc)? If you you may want to check the configuration there.

Have you tried UEFI boot instead of BIOS boot, I have found sometimes the error is more descriptive in one vs the other (or even that one way has no error and the other does). I have found it especially helpful to have a camera/phone camera with high speed video recording, ie 120/240 fps and record the screen after I make my selection to catch any brief messages on screen.

@tom-elliott Cool, that worked perfectly 🙂

@stylus3530 yes the client does have renaming for Linux, Mac OS, and Windows. Windows has the benefit, however, of the host name early working from the imaging context.

@veresh The commit says the packages were added to enable compilation of iPXE binaries. As far as I understand the compiled iPXE binaries are (still?) pulled from the repository anyway, so I guess it’s to allow for updating (or modifying) the binaries manually without updating FOG

@george1421

I found my mistake

The IP was wrong the old VM snapshot had NAT instead of bridged network interface enabled

Thank you very much for the fast support.

alt text

Something i don’t anderstand is : I’ve got an other highscool to handle and i’m using fog on ubuntu too. I’ve got to upgrade the distribution here (to 17.10) and i’ve got no issue like this or at all…

@jpLeca Could you please send your last answer in your native language as well. Might help us all understand a bit more and could be helpful to other users too.

@george1421 Eh, saying ‘try’ sounds less like orders. I’m a boss of nobody but myself.

Hi,

I found a solution:

kernel tftp://${fog-ip}/boot/ubuntu/trusty/amd64/linux initrd tftp://${fog-ip}/boot/ubuntu/trusty/amd64/initrd.gz imgargs linux auto=true console-setup/layoutcode=fr keyboard-configuration/xkb-keyboard=fr locale=fr_FR.UTF-8 hostname=master domain=maestria.fr url=http://${fog-ip}/preseed_path/preseed_name.cfg quiet initrd=initrd.gz root=/dev/nfs netboot=nfs nfsroot=${fog-ip}:/tftpboot/boot/ubuntu/trusty/amd64/ boot

It’s look to work just need to configure my preseed file correctly.

Thank’s

@zago123 I was talking about the version of the ISO specifically. Apologies for not making that clear the first time.

@george1421

Thanks for that - I’ve got it booting - my menu entry now looks like:

Menu Item: fog.ubuntu-server
Description: Ubuntu Server 16.04
kernel tftp://192.168.0.22/os/ubuntu/16.04/server/vmlinuz
initrd tftp://192.168.0.22/os/ubuntu/16.04/server/initrd.gz
imgargs vmlinuz initrd=initrd.gz root=/dev/nfs netboot=nfs nfsroot=192.168.0.22:/images/os/ubuntu/16.04/server/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb
boot || goto MENU

Many thanks again for your help!

@tom-elliott
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 787M 9.3M 778M 2% /run
/dev/sda1 451G 5.7G 423G 2% /
tmpfs 3.9G 212K 3.9G 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs 787M 60K 787M 1% /run/user/1000
/dev/sdb1 1.8T 614G 1.2T 36% /media/fog/d40b9b49-226e-4e64-b365-0b7b71d9ed3b

i used this and it worked: https://wiki.fogproject.org/wiki/index.php?title=Moving_your_images_directory/Adding_Storage_to_the_Images_directory

Thanks!

Thank you so much! It’s working now!

@wayne-workman
That’s my plan I am copying the entire image directory and going to migrate.

@tom-elliott Oh la la!! works very verry fine 🙂

@tom-elliott I am not quite sure what was wrong. I was working with someone else here on the forums on trying to do the automation and he had me run a script on mysql which ended up messing up a few things (accident). I was trying to work with the persistent groups piece. I ended up having to do a restore of the FOG server and that’s when the issues happened. I think I just had some duplicate entries somehow once I did the restore.

I look forward to a new GUI layout! You guys are rock stars!