Hey Tom, take your time and get yourself settled!

I am wondering if this is a good point too where we reach out to the community for people to join into the FOG team to help work on the code, fix issues, improve stuff here and there.

@Tutungzone Maybe there is a quick fix for this issue. It’s been some time since we updated the RAMDISK size and I guess this could fix it: Go to the FOG web UI -> FOG Configuration -> FOG Settings -> TFTP Server and set KERNEL RAMDISK SIZE to 275000. Save settings and try booting into a task again.

https://news.fogproject.org/fog-1-5-8-officially-released/

https://github.com/FOGProject/fogproject/releases/tag/1.5.8

https://news.fogproject.org/fog-1-5-9-officially-released/

@Tom-Elliott, @Developers, @Moderators
I got carried away trying to improve the current iPXE script. Now that I’ve dug into the syntax and found some interesting new stuff I want to see what you guys think about this:

#!ipxe
isset ${net0/mac} && dhcp net0 || goto dhcpnet1
echo Received DHCP answer on interface net0 && goto proxycheck

:dhcpnet1
isset ${net1/mac} && dhcp net1 || goto dhcperror
echo Received DHCP answer on interface net1 && goto proxycheck

:dhcperror
prompt --key s --timeout 10000 DHCP failed, hit 's' for the iPXE shell; reboot in 10 seconds && shell || reboot

:proxycheck
isset ${proxydhcp/next-server} && isset ${next-server} && echo Duplicate option 66 (next server) from DHCP proxy and DHCP server && echo Using IP sent by DHCP proxy ${proxydhcp/next-server} && prompt --timeout 5000 || goto nextservercheck

:nextservercheck
isset ${proxydhcp/next-server} && set next-server ${proxydhcp/next-server} ||
isset ${next-server} && goto netboot || goto setserv

:setserv
echo -n Please enter tftp server: && read next-server && goto netboot || goto setserv

:netboot
chain tftp://${next-server}/default.ipxe ||
prompt --key s --timeout 10000 Chainloading failed, hit 's' for the iPXE shell; reboot in 10 seconds && shell || reboot

Feel free to comment and improve. I’ve tested the script and tried to remember all the issues I came across in the last months but I am sure we’re not there yet.

I want to thank Tom again for this! I tried to assist and help but I just don’t know the code (and its history) as much as Tom does. He’s done all the hard work to find and fix this issue. Along the way he also fixed a couple other things as well.

@Tom-Elliott Don’t say sorry. FOG is work in progress and you are pushing things way forward!! :metal:

@TrialAndError said:

Obviously the development of FOG stopped after a long time of hard work.
It would be friendly by the developers to inform the users about that.

I am not sure what exactly you mean. This is an open source project and we have no time schedule for new releases and we don’t have a set list of features to add or bugs to resolve. We simply do what we can and like.

It’s quite bizarre to state that FOG development stopped… totally wrong!

@Wirefall Great you posted the full kernel messages listing. At first I didn’t notice any issue but looking closer I found the issue:

igb: probe of 0000:01:00.0 failed with error -2

The PCI ID perfectly matches the one you mentioned in your fist post. Didn’t take long to find several reports on this issue that came in just lately:
https://lkml.org/lkml/2016/11/24/172
https://bugzilla.suse.com/show_bug.cgi?id=1009911
https://patchwork.ozlabs.org/patch/700615/

Some say that it might possibly work if you disable PXE boot for this NIC in BIOS. I don’t think this is a great solution as FOG heavily relies on PXE booting the clients. Let’s hope that this will be fixed in the latest kernel fairly soon!

We are working towards a most stable release of the 1.5.x line of FOG and will publish release candidates of FOG 1.5.9 for this over the next weeks. We ask people to participate and help test to get the final release as good as we can.

https://news.fogproject.org/fog-1-5-9-rc2-available/

@sudburr Why not re-install the whole system from scratch?

@SCavender Ahh, I didn’t notice the gateway (in DHCP) is set to your FOG server IP 192.168.22.11 when looking at the dhcpd.conf. Are you sure this is what you want? From what you said so far I would think you want the router to be 192.168.22.1.

If your FOG server is meant to be a gateway it needs things like IP forwarding in the kernel enabled and iptables rules to pass packets through. Not something we provide with the FOG installer.

While looking at the dhcpd.conf once again I also notice that you might wand to change the line range dynamic-bootp 192.168.22.10 192.168.22.254; because the range starts at 10 but your FOG server is at 11. Make it start at 20 for example to prevent from duplicate IP issues.

Make sure you also change the values in /opt/fog/.fogsettings so the installer won’t reset things on the next upgrade!

After changing the config you need to restart the DHCP service or your FOG server altogether.

@mesaman0182 Thanks to @Tom-Elliott this is fixed in dev-branch. So if you want to install FOG on Ubuntu 21.04 you just need to use the latest dev-branch version from github.

@john3892 Best if you open a new topic. Just cross link this forum post here as reference and then send all your details like FOG version, Linux OS/version, steps you took (in detail)…

@tom-elliott said in Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.:

in my testing language translation worked properly using the common provided version

Then it’s all fine. Good that we don’t need that extra package anymore!

@SCavender When you boot up a client, please run ipconfig /all in Windows CMD, take a picture and post here.

Just want to see if it receives the DNS server information from the DHCP or not.

@d2freak82 From the little information we have so far I would expect you run into the issue where Ubuntu started disabling TLSv1.0 and TSLv1.1 in the Apache configuration. Find more details on this here: https://forums.fogproject.org/topic/15151/fog-client-installation-error-cannot-install-ca-certificate

An updated and fixed fog-client installer is available: https://github.com/FOGProject/fog-client/releases/download/0.12.0/SmartInstaller_fixed-tls.exe

@tom-elliott said in Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.:

Issue is ubuntu 21.04 is using php{ver}-common for php-gettext where in the past it was its own package.

When I was looking at this I got the impression the new package is named php-php-gettext (see package repo).

When searching for php-gettext in general (link to search) I find this:

bionic (18.04LTS) (web): transitional dummy package for php-php-gettext [universe]
1.0.12-0.1: all

You are absolutely right, the PHP gettext module is now part of php7.4-common but the mentioned php-php-gettext provides some helper PHP/INC files - not sure if we need those.

@scavender said in No Subnet Declaration for virbr0 After Upgrade to 1.5.9:

192.168.22.1 is the Gateway IP/Subnet for the VLAN 22

Does this gateway provide DNS as well? Either as a DNS service or by relaying the DNS queries to an upstream DNS server?

@cf20corvuss I suppose your are using VirtualBox, right? This is a known issue. If you shutdown the VM and “cold start” it up the issue does not happen.

A quick fix is to change your DHCP config to send ipxe.pxe (instead of the default undionly.kkpxe).

@george1421 said in One central FOG server plus multiple Storage nodes in different locations possible?:

You can only capture images to the central server. The storage nodes are deploy only.

This is the most important point I think. From what @tesparza said so far it sounds as if image capture to storage nodes is wanted.