PXE boot failed 1.5.6

[astrugatch]

@Sebastian-Roth

Welcome back!

Attaching a log file from my ssh session that should have all the info you asked for.

20190625_084305.SSH.w0t0p0.5D9392E8-A16D-40C6-B829-79E0F6F88A28.36728.3482263491.log

[Sebastian Roth]

@astrugatch Great! Well that looks interesting. Building looks fine so far but it seems to not copy the files over to /tftpboot for some unknown reason. So far I’ve only had a quick look at the log. Maybe something I missed there.

[Sebastian Roth]

@astrugatch Are you sure you are on 1.5.6? From the output it looks more like you have 1.5.5 really because in ~/trunk/ directory you only have binaries...zip files up to 1.5.5…

Just asking because there was an issue in the iPXE build script that I fixed between 1.5.5 and 1.5.6 if I remember correct.

Please run and post output here:

cd ~/trunk/
git branch -v

[astrugatch]

@Sebastian-Roth

root@fogimaging:~/trunk# git branch -v
  dev-branch 71b77da [behind 252] Release 1.5.2 to fix install bugs and new item creation bugs.
* master     d75b1d3 Merge branch 'dev-branch' of github.com:FOGProject/fogproject into dev-branch
  working    f3fe2ce [behind 67] Add testing of Redhat < 7 for maintaining native php handling vs. FPM
root@fogimaging:~/trunk#```

[astrugatch]

@Sebastian-Roth

[astrugatch]

@Sebastian-Roth

Its odd because I’ve re-run the 1.5.6 installer recently too which from what I understand also runs the build.

[Sebastian Roth]

@astrugatch Strange. Please run ls -al ~/trunk/bin/error_logs/ and post output here.

[astrugatch]

@Sebastian-Roth said in PXE boot failed 1.5.6:

ls -al ~/trunk/bin/error_logs/

root@fogimaging:~/trunk# ls -al ~/trunk/bin/error_logs/
total 516
drwxr-xr-x 2 root root 4096 May 3 20:20 .
drwxr-xr-x 5 root root 4096 May 3 20:12 …
-rw-r–r-- 1 root root 45530 Mar 1 2018 fog_error_1.5.0.log
-rw-r–r-- 1 root root 37941 Nov 13 2017 fog_error_1.5.0-RC-10.log
-rw-r–r-- 1 root root 41473 Jan 26 2018 fog_error_1.5.0-RC-11.log
-rw-r–r-- 1 root root 58 Feb 15 2018 fog_error_1.5.0-RC-12.log
-rw-r–r-- 1 root root 39477 Feb 15 2018 fog_error_1.5.0-RC-13.log
-rw-r–r-- 1 root root 41019 Apr 25 2018 fog_error_1.5.2.11.log
-rw-r–r-- 1 root root 42209 Apr 11 2018 fog_error_1.5.2.log
-rw-r–r-- 1 root root 41937 May 30 2018 fog_error_1.5.3.log
-rw-r–r-- 1 root root 43541 Aug 13 2018 fog_error_1.5.4.log
-rw-r–r-- 1 root root 45401 Nov 20 2018 fog_error_1.5.5.log
-rw-r–r-- 1 root root 64951 Jun 19 08:40 fog_error_1.5.6.log
-rw-r–r-- 1 root root 15208 Jun 19 08:32 foginstall.log
root@fogimaging:~/trunk#

[astrugatch]

@Sebastian-Roth Install 156 error log.log

[Sebastian Roth]

@astrugatch Thanks for posting this log as well. Having a closer look I just found this:

make: Nothing to be done for ‘/opt/fog/snapins/ssl//CA/.fogCA.pem’.

I am not quite sure what is going wrong here. But seems like we are on the right track here.

Please run echo $SHELL && lsb_release and post output.

[astrugatch]

@Sebastian-Roth said in PXE boot failed 1.5.6:

echo $SHELL && lsb_release

/bin/bash
No LSB modules are available.

[Sebastian Roth]

@astrugatch Whoops, what I meant is lsb_release -a

[astrugatch]

@Sebastian-Roth

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial```

[astrugatch]

@Sebastian-Roth

Gotta go pick up my kids. I’ll take another swing at this tomorrow.

[Sebastian Roth]

@astrugatch Ohhh no, there is a bug in the scripts which I somehow must have overlooked. Obviously my testing has been terrible back then when I last changed that script.

Forget what I wrote last. I even deleted the post so people don’t get confused. I will push out a fix in dev-branch in a minute. That should then be part of 1.5.7 which should come out soon.

Edit: Fix is out: https://github.com/FOGProject/fogproject/commit/1bf321d399a3af664faab580fe81379051bf6eaf

[astrugatch]

This post is deleted!

[astrugatch]

@Sebastian-Roth

Still getting errors on iPXE with the new build

(note to anyone with this issue, I only did a buildipxe.sh on dev-branch and that didnt work, a full reinstall on dev-branch fixed it)

[astrugatch]

@Sebastian-Roth

Full rebuild on dev-branch works.

Thanks for looking into this so deeply!