@Oleg said:

I don’t know if it has to do something with the timeout issue but in /etc/default/grub I added

We don’t use GRUB for PXE booting hosts usually! Seems like you have customized your setup a fair bit. I may ask you to tell us more about the customization to we are able to properly help you!

I changed manually the kernels in /var/www/html/fog/service/ipxe/ to the 4.15.2 Kernel.
With the older kernel the issue with the timeout is gone.

That’s interesting. So it seems like a Linux kernel network driver issue from what we know so far. Let’s start by trying to find out what driver is used. Please boot Windows on that machine, open device management and get us the device ID from there. Usually in the form 12c4:5f78.

@88fingerslukee said in FOG Server cannot connect to storage node:

I have put the correct mysql connections into the fogsettings file.

The fogsettings file is only used by the installer. Did you re-run the FOG installer after adjusting fogsettings? Or you can manually edit /var/www/html/fog/lib/fog/config.class.php for the DB settings.

The URL called is http://fog.server.ip/fog/status/kernelvers.php - be aware that this URL is called from your FOG master node. So if you can open this URL from your browser it doesn’t necessarily mean that it does work when called from the master node as well.

@beardedfool Which Linux OS and version do you use? Older versions of FOG before 1.5.8 did run with an empty DB root password. So you find a lot of dated information on this. We were adding more security in 1.5.8 but it hat minor issues on some Linux OSes. Will provide detailed information for you when we know what you use.

@mechalas Nice to see you’re still around! I remember having looked into this for quite a while but then decided I’d just use the cert store search as implemented to fix this. It’s working great and I don’t see any drawbacks. We have moved forward and released new fog-client versions since then.

Nevertheless there are new things to look at and figure out. It would be really great if you’d help us on the fog-client.

Thanks. It’s helped.

@dirtysoc Thanks for posting. This is fixed in dev-branch already. As well we have fixed another issue on Raspbian Buster in dev-branch (compiling udpcast).

Both fixes will be in the next release.

@binglingyu Anything more we can do to help you on this? Please provide more information as requested by George.

I have a tutorial on how to (reuse) fog to be used as a netboot server here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

For PXE booting you need to have a dhcp server where you can configure dhcp options 66 and 67. If you are in a home lab with a soho router then you should install dnsmsaq onto your fog server to provide pxe boot info in place of your soho router. Your soho router will still provide dhcp services, just dnsmasq will provide the netboot into.

https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server

As for virtual box settings, I don’t know.

@danieln So if you key in http://10.50.0.218/fog does it display any page or error message? Displaying the default apache page is great. That tells you the web server is installed and operational.

@adrien17 Good to hear. I just updated the wiki article: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Installing_-_Linux

Reporting back… latest versions works like a champ!

@Sebastian-Roth I was hoping for a completely new one. Mine is less of a script and more of a realm join in a bash file

@jhumpf Have you tried the scripts? Can we mark this closed or do you need any further help with this?

Okay, now the client gets the information from the server without error and can execute a task launched from the server.
Thanks a lot.

I believe you have to modify the client OS to support being booted over iSCSI, though I have limited experience with it.

I could be wrong, but I think by default iSCSI isn’t included in the initramfs of Ubuntu.

Perhaps this https://apfelboymchen.net/gnu/notes/booting ubuntu iscsi.html could be helpful. (at least the client info)

All that said, NFS boot is likely to be a lot more straightforward to implement and I use that method quite often.

@Daniel-Miller Thank you, I’m learning both Cent and Fog at the same time, challenging but interesting, I couldnt find why I had 127Gb total storage but only 27Gb was being shown in Fog GUID so I ended up re-building the server. Appreciate the info though.

@Dv27842 said in Installing FOG on Ubuntu 18.04 Desktop:

Synology NAS

Setting this up is fairly advanced! You are better off just using a simple setup with just one FOG server (including it’s own storage) in a VirtualBox I’d say. Play with this and when you are ready take the next step.

@Base2Nathan Good to hear you figured it out. You might wonder why the config George suggested doesn’t use option tftp-server-... and option bootfile-name at all. There are two places in DHCP packets where PXE boot information can be placed. One is DHCP options as you have used them. But there is also next-server and filename what are fields within the DHCP header information. Take a closer look at the wireshark dump…

@brehuffm said in Centos7 hostname change not working:

Is it safe to assume that this fix will be in the next Fog image?

Not sure what you mean by fog image. The next fog-client version will have that fix included, sure…

If this is accurate shouldn’t broadcast be 192.168.1.255?