@abulhol Fixed in working branch, will be in the next release. Let’s see if we are able to get this out in time so people upgrading their servers from 16.04 to 18.04 won’t run into the same issue as you did.

@lucycle
I used to have an issue with some Realtek cards behaving weird and throwing errors in IPXE and later in the boot process, but it’s been a while. With these two HP models and an integrated Realtek card I had to use a different boot firmware, long shot but maybe you can try that?

HP210 Legacy Test

pxe-service=tag:HP210,X86PC, “HP-210 Working”, realtek.kpxe

HP430 UEFI Test

pxe-service=tag:HP430,X86-64_EFI, “HP 430”, realtek.efi

@lucycle said in NFS over TCP not available from x.x.x.x:

In my case the driver in question was dm9601.ko and I also compiled it into my initrd.img which did not fix the issue and behavior persists.

I’ve added another USB dongle, this time a Lenovo 2.0 Ethernet Adapter based on the asix driver, however it didn’t work, then I checked with modinfo and noticed I was missing a dependency (usbnet.ko)

modinfo asix .... depends: mii,usbnet modinfo usbnet filename: /lib/modules/4.15.0-34-generic/kernel/drivers/net/usb/usbnet.ko

Just to be sure, you said initrd.img, I added it to initrd.lz

That’s about all I’ve got to suggest at this point

@george1421
Thanks george1421,
I have no issues with mine but thank you 🙂

@Boyan-Biandov yes, but I prefer to use the working branch because it uses Ubuntu’s PHP7.2, which makes it more compatible with other software.

@geardog Sorry for the long delay. Will be ready fairly soon. Are you still interested, I hope?!

I added it yesterday but also had to put in some major work to fix issues in our kernel build environment… https://github.com/FOGProject/fos/pull/12

@abulhol Fixed in working branch.

Hello Sebastian!
Just realized my response stayed as a draft for this long.
Thank you so much for this very useful pieces of advice. I will look into that.
To be honnest, scripting was on my list of skills to develop and improve on a short term scale and that is the perfect occasion to do so!
I shall get back to you when I have moved forward enough.
Regards.

You have to set a (very strong) mysql password first, topic:

https://forums.fogproject.org/topic/12445/please-help-ubuntu-updates-screwed-up-my-mysql-root-password/7

@george1421 Great you’ve been helping out so much here and figured it all out.

@mstumpo Marking this solved as I think the initial question(s) is/are solved. Please feel free to open new topics as you run into new issues. Good to keep topics clean so other people can find this and profit from the answers as well (details not lost in a 5 page topic).

First let me say that FOG will not work as you have it defined. FOG will only image using a single IP address on the FOG server. Your FOG server can have more than one network interface but will only image using a single IP address.

I know I’m mixing what I’m saying. FOG does support network bonding (using two or more physical network interfaces to add additional lanes of bandwidth). But those bonded interfaces MUST have a single IP address assigned. And typically the bonded interfaces go to a single network switch.

Your drawing appears you want a multi-homed FOG server (multi-homed means multiple network interfaces each with their own IP address). That is not supported for FOG imaging.

@jtyler Have you had a look into the mentioned error_logs? Let us know what you get.

I managed to make a simple symlink on the /usr/lib/systemd/system/ folder
php-fpm.service -> /usr/lib/systemd/system/rh-php56-php-fpm.service and this seemed to clear the problem.

thank you

@george1421 It’s now working, as i’ve installed so many times this time around I forgot to open the web panel and import the configuration 😉

thanks for your help

@unltdlove2u How did you create that ubuntu-16.04.img in the first place? Sounds to me as if this is just your KVM image file, right? Well with FOG the steps to create an image is: register the machine (as well KVM should work if all network and DHCP is setup properly), schedule a capture/upload task and let the client upload its disk contents.

What you are asking for is a way to convert your KVM disk image into a FOG image. Might be possible but it’s not supported. Search the forum for convert vmdk and such VM disks. I think some people have done it but it’s probably a lot of work and I am not sure it’s worth it.

For dm-crypt/LUKS you need to let FOG do a sector by sector copy (also called dd) as it can’t read the encrypted filesystem stuff. The FOG image will be very big as it contains unused sectors as well.

I’m having the same trouble with 18.04. Was curious if you found a work around. Booting the ISO itself works fine, but PXE booting doesn’t work. My guess is that the network, obviously, has to start sooner in order to pull over the files via NFS, and this is somehow mucking up the traditional order of operations.

@hvaransky I also recommend you open a new thread unless your fog server and configurations are exactly the same as the OP’s I don’t want to confuse posted information because we are talking about different setups.

@kte Read through this: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Use the built in kernel upgrade tool in FOG Settings -> FOG Kernel to install the down level kernels.

In the past I’ve had issues with the FOG server being able to connect to the internet through our departments firewall/proxy systems. I have managed to get it working this time tho thankfully and have downgraded the kernel!

I have also edited the php values and changed the client check in settings to 300. This has helped the CPU load on the server although it still seems a little high than what we are used too. At least it is a lot more responsive now on the web interface!

We are now having a GPT issue deploying an updated image that was captured after the upgrade (pre-upgrade images seem to deploy fine). I have started a new forum post on this though.

there isn’t anything there yet:
anthony@fogserver2:/opt$ ls
1.5.4.tar.gz fogproject-1.5.4

@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