@Sebastian-Roth Thank you for your advice. What you said seemed to be my issue. All I did was uncomment option routers and replace the IP with my DHCP server IP. I can get into the FOG splash screen now. Thanks!

@imt_fog If you boot the machine in question in debug mode, you should be able to run parted -l manually and check the flags.

I don’t think this is caused by such, however, but interested in seeing the results.

Worth noting that partitions that go through the checks but fail to resize get marked as fixed size as well (to prevent issues during deploy)

@Jedi exactly this.

@Leigh-Elgar said:

is there an option to or could there be an option to, allow identical MAC addresses to be added as additional MAC addresses

As of now the MAC address table has a UNIQUE constraint in the database. Sure something we could (and need to) change in the long run. I am afraid to say that there is no quick solution to this.

I have reboot the server yesterday,
Now updating database is very fast.
And I receive mails for task results…

I think the problem appeared when I set “FOG_EMAIL_ACTION”.

Thanks for your answers

Sorry for the late reply… Tried on another computer, and I cannot get the FOG menu to appear (this computer has never registered on that FOG server).

@george1421 You weren’t kidding about the 10 minutes, that was easy! There was another article on DNSMASQ that I had looked at before putting up this post, which looked mega complicated. Likely it was intended to do more than just PXE stuff. I haven’t deployed anything, but I registered a computer successfully after booting to PXE, so now I just have to migrate from laptop to server. w00t!

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

Hello,

My problem is solved by a modification of the bios.
I unchecked the PCI Express Power Management box and the Extended Idle Power States box.

Thanks.

@Louis-CSUSA Well this time we see that apache cannot communicate with php-fpm:

AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed AH01079: failed to make connection to backend: 127.0.0.1

Probably a firewall issue. Run iptables -L -n -v and post output here. If you are not an expert with SELinux I’d advise you to set to permissive (aka disable) it!! Should have asked you about this earlier.

Now it works perfectly, thanks!

@Minxster @Vanlue-IT-Guy Have you search the forums yet? There have been many discussions on various Surface devices (2, 3 and 4) where some seem to have very similar issues. Here is an interesting one you might want to read from start to end: https://forums.fogproject.org/topic/11635/microsoft-surface-pro-4-using-dock-has-issues-with-dhcp-for-imaging-task

Solved:

Rebooted the server to get the Snapin Hash working

I migrated an old database of hosts onto this server and it seems the snapin service settings didnt come over with them. So all of the services were disabled.

Thanks for the help, the .exe-file is installed. Now I can try to capture my first image. Hope I dont run in to any more problems?

Found and fixed a typo in the IP address of the DB connector on the storage node.

@Sebastian-Roth
Ok, I see. Time is limited! I totally understand this. Well, I’d like to help but I’m have no developing skills at all. I’l try to further investigate the problem (saw some errors in the fog.log)
For the moment this issue can be closed.

@Sebastian-Roth

Sorted!

As soon as i imported the hostMAC table they all appeared in the web portal.

For anybody reading in the future:

To Migrate just your Host list, you will need to export both the “hosts” and “hostMAC” tables from the old database using mysqldump, then import them both into the new database. Just doing the hosts table will not make them show in the web portal.

@george1421 Thanks, that is helpful to know.

Some reports, like “imaging log”, don’t have pre filters and try to show all the entries in the database, normally you have a lot of entries in the database and the server doesn’t have memory to run it.

In the dev-branch, not stable branch, I made some changes in the reports to have some pre-filters, with these pre-filters you can limit more the search parameters and be more exhaustive and use less memory 😉

@luiztpd said in WOl Broadcast not work:

my server fog is with network ip address 192.168.x.x / 24;
the workstations are in a vlan 172.x.x.x / 24 and other 172.x.x.x / 21!

That is probably part of your issue. Unless your vlan router support directed broadcasts the WOL messages are probably not traversing your vlan router. As a test install a workstation on the 192.168.x.x network and then test.

Then I would suggest you test WOL with a third party application (install on the 192.168.x.x subnet) and see if it can wake up a workstation on the 172.x.x.x subnet. Lets try to understand where the problem isn’t before we focus on a solution (maybe).