Just upgraded to Ubuntu 22.04 with PHP 8.1 (from 20.04 with PHP 7.4), also updated FOG from 1.5.9 to 1.5.10 - so I’m not sure quite where this error lies, it might be my code.

I have an application that uses the FOG API. I haven’t changed anything in this and it has always worked before the upgrade.

Specifically, when I use the ‘edit’ path to assign an image to a host:

PUT request
URL host/[host ID]/edit
JSON ["imageID": int]

I get the following in the PHP error log:

[proxy_fcgi:error] [pid 1166] [client 127.0.0.1:42750] AH01071: Got error '
PHP message: 
PHP Warning:  Undefined property: stdClass::$name in /var/www/fog/lib/router/route.class.php on line 623
PHP message: 
PHP Warning:  Undefined property: stdClass::$name in /var/www/fog/lib/router/route.class.php on line 626'

Looking quickly at the code it seems to be something to do with not having a ‘name’ parameter in the JSON, but Ive never needed that before and I’ve no idea what I would set it to. The request does seem to work, but clearly something is wrong somewhere.

@greg-plamondon Yes, I never enable that nonsense

@george1421 Thank you, that’s a very helpful explanation. I think I will start experimenting with using snp.efi as my default and create specific rules for machines where it does not work.

@sebastian-roth Thanks. In the end I found that even realtek.efi didn’t entirely work. The PC is connected to a KVM and using realtek.efi it will only boot if the active KVM port is the one the PC is connected to. Otherwise it gets stuck in and endless loop of retrieving the file, crashing, and rebooting. ‘snp.efi’ does seem to work but I’d really like to know what the difference is. Do you know if it’s documented anywhere or shall I have to rely on the mailing list? I haven’t found anything on the iPXE website.

This is what I came up with in dhcpd.conf

class "Realtek-64Bit-UEFI" {
    match if binary-to-ascii(16,8,":",substring(hardware, 1, 3)) = "1c:69:7a";
    filename "snp.efi";
}

I found another possible solution though I’ve no idea why it works. I switched every instance of ‘ipxe.efi’ in my dhcpd.conf to ‘realtek.efi’. This was a complete guess, but now the USB-C ports work.

How can I work our what to use as the string match so that I can ensure that only this Lenovo PC uses realtek.efi?

Also can anybody explain why this made a difference? The main USB controller is an AMD controller. There is a Realtek USB SD Card Reader and a Realtek NIC but I was never having any issues with those.

Running FOG 1.5.9. I have a specific problem with an AMD-based Lenovo. When booting normally it’s fine but when booting via iPXE all the USB-C ports are disabled. This happens the moment that it downloads the NBP file from FOG.

From searching forums it seems this is a known iPXE problem and the only solution I’ve found is that you need to completely disable usb support in iPXE by rebuilding iPXE with some special options, but I don’t know how to do this using FOG’s buildipxe.sh. I’ve tried just running that to get the latest version of iPXE but that hasn’t helped.

@Sebastian-Roth thanks! I did not know about the postinit scripts. I’ve no problem with them all having the same password so that was really easy.

I’ve noticed that there is an SSH server running on the client machine while it is imaging. I’m wondering what the login details are, or how they can be set?

To explain why, I’ve been running a lot of unattended installs remotely (covid etc) and just occasionally a machine will get stuck, where it sits at the Partclone screen waiting to start but never does. It’s related to using Multicast, but not being able to get to the machines easily it’s been very hard to figure out what’s causing it. If I could SSH in I could at least reboot the machine, instead of having to badger somebody to go and do it for me (or driving for an hour to push a button). It’s only a workaround but it would be a big help.

I’ve just tried an Insider build from the Dev channel, Secure Boot was not required - though is supported by this hardware (Intel NUC). MS are saying that the requirement is actually a TPM - they’re saying ‘Secure Boot Capable’ because that’s more consumer-friendly than talking about TPMs.

The image type in FOG can be set to Windows 10, and I was able to capture and deploy

@pep said in Using a separate NIC for multicast:

web = http: //192.168.1.100/fog/ ftp = 192.168.1.100 storage = 192.168.1.100: / images / dev / storageip = 192.168.1.100

Thanks! That works. I can leave my storage settings as default and Multticast will use eno2, then for anything not multicast I can set the correct parameters for eno3.

Just a note that for deployment the storage variable needs to be ip.address:/images/ (without the dev/)

@Sebastian-Roth OK thanks for the reply. It’s no biggie but I’ve got all these NICs and nothing to use them for

As an idea, could I create another storage group for the images I might want to multicast, where all the settings except the interface and IP address are the same as the default group? If I set that to use eno3, and multicast to use eno3, that might achieve what I want?

I’ve a FOG server on Ubuntu 20.04, latest version of FOG. My server has 3 NICs all connected to the same subnet. I want to use eno2 for imaging and eno3 for Multicast, but I can’t get the multicast bit to work.

I’ve configured my storage node to use eno2 and set the IP address to the IP of eno2 and normal imaging works.

I then went fo FOG Settings->Multicast and set the interface to eno3. But when I start a multicast task the hosts all get stuck at the Partclone screen. I can see from the server logs that FOG is starting the multicast task using eno2.

If I change the config to use eno2 for multicast then my multicast tasks work, but I was hoping to utilise the extra bandwidth of the 3rd ethernet port I feel sure I’ve missed something obvious… but what?

@george1421 Thanks for the help … ohh Apple… on booting to the debug kernel I’m asked to ‘press Enter to continue’. However, it appears that as well no driver for the nvme, there’s also no driver for the keyboard. So, locating a USB keyboard I was able to determine the following:

[Wed Apr 03 root@fogclient ~]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    1  1.9G  0 disk 
`-sda1   8:1    1  121M  0 part 
[Wed Apr 03 root@fogclient ~]# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3ec4] (rev 07)
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 07)
00:01.1 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x8) [8086:1905] (rev 07)
00:01.2 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x4) [8086:1909] (rev 07)
00:12.0 Signal processing controller [1180]: Intel Corporation Device [8086:a379] (rev 10)
00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a36d] (rev 10)
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a36f] (rev 10)
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a360] (rev 10)
00:1b.0 PCI bridge [0604]: Intel Corporation Device [8086:a340] (rev f0)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a338] (rev f0)
00:1e.0 Communication controller [0780]: Intel Corporation Device [8086:a328] (rev 10)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a313] (rev 10)
00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a324] (rev 10)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e3)
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:aae0]
02:00.0 Mass storage controller [0180]: Apple Inc. Device [106b:2005] (rev 01)
02:00.1 Non-VGA unclassified device [0000]: Apple Inc. Device [106b:1801] (rev 01)
02:00.2 Non-VGA unclassified device [0000]: Apple Inc. Device [106b:1802] (rev 01)
02:00.3 Multimedia audio controller [0401]: Apple Inc. Device [106b:1803] (rev 01)
03:00.0 Network controller [0280]: Broadcom Limited Device [14e4:4464] (rev 03)
04:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] (rev 06)
05:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:01.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:02.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
05:04.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
06:00.0 System peripheral [0880]: Intel Corporation Device [8086:15eb] (rev 06)
07:00.0 USB controller [0c03]: Intel Corporation Device [8086:15ec] (rev 06)
7a:00.0 PCI bridge [0604]: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] [8086:1578] (rev 06)
7b:00.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:01.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:02.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7b:04.0 PCI bridge [0604]: Intel Corporation Device [8086:15ea] (rev 06)
7c:00.0 System peripheral [0880]: Intel Corporation Device [8086:15eb] (rev 06)
7d:00.0 USB controller [0c03]: Intel Corporation Device [8086:15ec] (rev 06)

@Tom-Elliott That’s just command-line system_profiler, which is used by the GUI version and only gives me the exact same info I posted in the images earlier. No hardware IDs at all.

@george1421 Thanks, but no chance. I don’t have a license to install Windows, Linux won’t boot, and MacOS system profiler no longer displays hardware IDs.

It’s really like Apple don’t want people to mess with their hardware

@Sebastian-Roth I think this is the answer. No drivers for Apple’s nvme controller in the kernel yet

https://askubuntu.com/questions/1052373/install-ubuntu-bionic-18-04-on-macbook-pro-2018

@Tom-Elliott unfortunately this is in a production environment and we can’t currently afford the down time, but I appreciate your efforts and thanks for the reply - at least it has given me confidence that I’m not doing it “wrong”.

As it happens I’m currently automating the entire FOG process by writing entries directly into the database and that is working fine for now, but I was looking at moving to the API as I’m sure it will be better for forwards compatibility - so when time allows I’l update my test server for 1.6 and work with that until we can update the production server.

Thanks for the advice.

@Sebastian-Roth Hmmm. Good call. Ubuntu 18.10 won’t even boot let alone recognise a disk. I get the initial GRUB menu but then very little after that. Black screen now for ~ 5 minutes.

@Tom-Elliott Sorry, should have mentioned that, 1.5.5

@Tom-Elliott By “I can’t clear them” I mean that I’d expect sending an empty array would clear all snapin associations from that host, but it doesn’t, as evidenced by me looking in the FOG GUI and seeing the snapin association still there.

Here’s your GET command after my PUT with an empty array.

{ "id": "52", "name": "HPProDesk", "description": "Created by FOG Reg on April 1, 2019, 2:19 pm", "ip": "", "imageID": "85", "building": "0", "createdTime": "2019-04-01 14:19:01", "deployed": "0000-00-00 00:00:00", "createdBy": "fog", "useAD": "", "ADDomain": "", "ADOU": "", "ADUser": "", "ADPass": "", "ADPassLegacy": "", "productKey": "", "printerLevel": "", "kernelArgs": "", "kernel": "", "kernelDevice": "", "init": "", "pending": "", "pub_key": "72c8515c7251f909e54b10ccfa26776a118fba25c333f7f9c3c3021c6d53e8f6", "sec_tok": "c3cd9236c7c2f3ea4d8f90e93b4b910179759f30af2cf47b4a3b3b2b24ea2afc6419d0ede3a0b465f354299c7a027999defd59bd11f93902382f3e827c8a3aa4", "sec_time": "2019-04-01 15:25:55", "pingstatus": "<i class=\"icon-ping-down fa fa-exclamation-circle red\" data-toggle=\"tooltip\" data-placement=\"right\" title=\"Connection timed out\"><\/i>", "biosexit": "grub", "efiexit": "refind_efi", "enforce": "", "primac": "a0:d3:c1:4e:49:45", "imagename": "HPProDesk_Win8_64_Pro_Prepped", "hostscreen": { "id": "", "hostID": "", "width": "", "height": "", "refresh": "", "orientation": "", "other1": "", "other2": "" }, "hostalo": { "id": "", "hostID": "", "time": "" }, "inventory": { "id": "50", "hostID": "52", "primaryUser": "fog", "other1": "", "other2": "", "createdTime": "2019-04-01 14:19:01", "deleteDate": "0000-00-00 00:00:00", "sysman": "Hewlett-Packard", "sysproduct": "HP ProDesk 405 G2 MT", "sysversion": "", "sysserial": "CZC43626MJ", "sysuuid": "8d1f307a-6b12-7ee0-d0c5-d2601e0e7c03", "systype": "Type: Desktop", "biosversion": "02.28", "biosvendor": "AMI", "biosdate": "09\/05\/2018", "mbman": "Hewlett-Packard", "mbproductname": "2240", "mbversion": "1.0", "mbserial": "CZC43626MJ", "mbasset": "CZC43626MJ", "cpuman": "AuthenticAMD", "cpuversion": "AMD A4-6250J APU with AMD Radeon R3 Graphics", "cpucurrent": "Current Speed: 2000 MHz", "cpumax": "Max Speed: 2000 MHz", "mem": "MemTotal: 3440588 kB", "hdmodel": "Hitachi HDS721616PLA380", "hdserial": "PVE331Z9RYDSZU", "hdfirmware": "P22OAB3A", "caseman": "Hewlett-Packard", "casever": "", "caseserial": "CZC43626MJ", "caseasset": "CZC43626MJ", "memory": "3.28 GiB" }, "image": { "imageTypeID": "1", "imagePartitionTypeID": "1", "id": "85", "name": "HPProDesk_Win8_64_Pro_Prepped", "description": "", "path": "HPProDesk_Win8_64_Pro_Prepped", "createdTime": "2018-11-21 09:49:17", "createdBy": "fog", "building": "0", "size": "366997504.000000:19634143232.000000:", "osID": "7", "deployed": "2018-11-21 12:15:29", "format": "0", "magnet": "", "protected": "0", "compress": "6", "isEnabled": "1", "toReplicate": "1", "srvsize": "4096", "os": {}, "imagepartitiontype": {}, "imagetype": {} }, "macs": [ "a0:d3:c1:4e:49:45" ]