Reporting back… latest versions works like a champ!

Reporting back… latest versions works like a champ!

Thanks Sebastian, I’m trying it out today.

I did checkout the dev-branch… but yeah sure I’ll be your huckleberry… err guinea pig.

For reference: https://www.youtube.com/watch?v=R8OWNspU_yE

@Sebastian-Roth Keep forgetting about Snapshots… thats what I get for being in a hurry.

Ok so I’ve got an updated OS and following the steps here: https://wiki.fogproject.org/wiki/index.php?title=Getting_FOG I’ve pulled the dev-branch. So I should be good for the install script yes? (I’m not super experienced with git so I’m not feeling positive I actually have the full dev-branch source)

@Sebastian-Roth Oh it’s exactly as described and exactly what happened the first go-round.
Since it’s in a failed state… let me do this. I’ll re-re-flatten the guest and start over. Fresh 19.10 install, ‘apt update/upgrade’ then I’ll run the fog installer from the dev-branch and see what happens.

Well this is disappointing. So due to an unrelated issue I decided to flatten this guest and build anew. I figured it’d be good since now I know the right version to use.
So flattened, new 19.10 install and the Apache service is still an issue. Even with installing the dev branch.
Manually installed php7.3, apache2, libmodule-apache, etc… not a thing I do now alleviates the failed to restart web services error.

Ah I do see the port listed this way… a vanilla ‘netstat | less’ did not show :69 anywhere. Hence my confusion.

Ok so I was able to successfully PXE boot to a KVM guest, just not on a physical one yet.

So I know FOG works which is great!

Now I need to explore the settings and figure out how to successfully pull an image. Thanks for the help!

Am I correct in assuming that I should be able to see port 69 open via NMAP?

Thanks for the continued help Sabastian.

No, iptables is not configured on this machine:

sudo iptables -L -n -v
[sudo] password for fogadmin:
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
fogadmin@ssi-fog:~/git/fogproject-dev-branch/bin/error_logs$

Admittedly yesterday and previous our DHCP functions were handled at the firewall level. I had thought maybe there was some issue with that and since I’ve been meaning to do this anyway… last night I moved those functions to my domain controller (Server 2016). So the DHCP Options are configures correctly except a test PXE boot on a laptop behind me failed. It’s an HP so I didn’t get much feedback so I’m not sure the exact cause at this time.

fogadmin@ssi-fog:~$ ps ax | grep tftp
  965 ?        Ss     0:00 /usr/sbin/in.tftpd --listen --user root --address :69 -s /tftpboot
25260 pts/0    S+     0:00 grep --color=auto tftp
fogadmin@ssi-fog:~$ systemctl status xinetd
● xinetd.service - LSB: Starts or stops the xinetd daemon.
   Loaded: loaded (/etc/init.d/xinetd; generated)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

Logs attached.fog_error.log foginstall.log