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.

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

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

@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.

@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!

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:

@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!

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

@Developers @Moderators Ok, I just opened a pull request to remove the 7156 binaries. Please all keep that in mind. Might cause some minor confusion in the next weeks. But it’s good to get rid of it.

As you all can see the tests of the most recent iPXE version shows that things are back to normal again. I reported back to Michael Brown on the iPXE devel mailing list. So he’s got that in mind as well.

@Avaryan To me this sounds like a different issue. Would you mind opening a new thread on this and posting more details (FOG version, USB ID of the NIC used as shown with lsusb, …).

I’ll mark this solved/closed now. @Psycholiquid Thanks heaps for the great work on testing all the binaries and such!

@Jean-Jacques-Morda Why do you have more than one DHCP server in your network? And why do they offer different information (next-server/option 66) to the clients. This is not strange but kind of expected and it just does not make any sense to me why you would want to have this.

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-rc1-available/

@LOF Seems like your git pull has not gone to the latest version, which is 1.5.9-RC2.11

@Trev-lchs said in HP 250 G7 fails to upload image:

This is now resolved, on checking it appears that the kernel downloaded was the ARM64 instead of 64.

Interesting the ARM kernel gets as far as that on a HP 250 G7…

@LOF said in Failed to start php-fpm.service:

Also, I’ve already pulled down the dev-branch and got the error before my initial post

Which version number is shown by the installer script? Just want to make sure we are on the right track here.

As well make sure this is still in a kind of fresh state and /opt/fog/.fogettings is not created yet. Because if it is then things will behave differently in this particular situation.

Should I delete the previous dev-branch install and download/run it again?

No need to delete. You can re-run the FOG installer as often as you like if it is the same or a later version of what you have installed/run before. Should not cause any trouble.

@astrugatch As far as I remember there was an issue in this part of the web UI which is fixed in the latest release candidate version. Though we can’t be sure if it’s the same unless you update to the latest and test.

@Mightmar I assume you hit ENTER before opening the URL to let it do it’s magic DB schema creation/update.

Well, no problem. Just re-run the installer exactly as you did before. This time it doesn’t matter if you really open the web interface URL at the right point because the schema should be updated already.

@NSD_Network_Admin @neodawg Just in case anyone of you is interested in this. The bug was fixed by this commit: https://github.com/FOGProject/fogproject/commit/66fa6f074c4662098ea38b811077f2ad25c09a46#diff-f21fb2470403477fe0c412911d1227f1

@astrugatch Please run the following two mysql querys on the command line to see if you can find it in the database:

SELECT * FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%';
SELECT * FROM hosts WHERE hostID IN (SELECT hmHostID FROM hostMAC WHERE hmMAC LIKE '%aa:bb:cc:dd:ee:ff%');

Put in the adapters MAC address instead of aa:bb:cc:dd:ee:ff.

I am wondering why you say “Wifi MAC address” at one point. Just a typo?

@Mightmar Did the installer run all the way to the end? Please take a look in the bin directory where you ran the installfog.sh script. Find a subdir called error_logs in there and two log files. Post the last 10 lines of both logs here.

@sudburr Is the partition layout still fine when you see this blkid: error: /dev/sda4 thing on subsequent tries?

May I ask you to do the following: Let it try to capture a few times more. Every time you save a copy of the /images/dev/aabbccddeeff/d1.partitions (this aabb… is the MAC address of the host without colons) file to another location for us to compare those afterwards. Whenever you see the blkid... error you name it d1.partitions_fail_X (put in numbers instead of X) and if you don’t see the error you name it d1.partitions_ok_X.sfdiskPartitionFileName

What kind of VM do you use? I am wondering if I am able to replicate the issue using the same setup?!

@NSD_Network_Admin Probably the best way is to wait for 1.5.9. I was planing to have it released already but work and private projects keeps me from doing so over the last weeks. I am hoping to find more time soon.