Nice! Thank you @Junkhacker and @george1421

I just changed it to work with the clients MAC address and it seems to work like a charm!

So now, i have this config:

iseq ${net0/mac} XX:XX:XX:XX:XX:XX && goto chainboot ||
goto fog.local
:chainboot
set pxeserver:ipv4 XXX.XX.XXX.XXX
set next-server ${pxeserver}
chain tftp://${pxeserver}/pxelinux.0
exit

I will do some testing but i am verry optimistic

Thanks!

@Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry

We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server.

like this:

iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing ||
:testing
set pxeserver:ipv4 FOG-IP
set next-server ${pxeserver}
chain tftp://FOG-IP/default.ipxe
exit

Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option

Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here!

Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …

thank for the help! It solved my problem!

Normally the fog installation script set its own password and normally this worked fine to me! Even in the update logs from an earlier SVN version there was a hint to this created user/ password. But in the new installer i cant find this in the logs. After changing it manually everything seems to be fine!

Thanks!

@Sebastian-Roth thank you for pointing me at the DHCP! I found the problem! All files are fine, but our company DHCP was not! After trying it in a seperated VMware Network it worked like a charm! So all the effort was in vain - i am sorry

We have an old fog running 1.4.4 in our DHCP config for managing the PXE Menu because we are running multiple (i)PXE Services in one subnet. I created a new boot menu item to forward the pxe boot to the new fog server.

like this:

iseq ${net0/mac} a0:36:9f:bd:XX:XX && goto testing ||
:testing
set pxeserver:ipv4 FOG-IP
set next-server ${pxeserver}
chain tftp://FOG-IP/default.ipxe
exit

Got it from here in 2017: https://forums.fogproject.org/topic/9648/add-a-second-pxe-boot-option

Worked fine, until now … And by now, i understand why no certification cmds were availibe because it got stuck in the old fog enviroment. Need sth. to reload the enviroment i think. I will take a look into it to find a way. Maybe i will open a new topic here!

Thank you @Sebastian-Roth for taking the time! Your scrips are fine - it was my fault …

@Sebastian-Roth okay, here is what i tried:

1. Freh install of ubuntu-18.04.1.0-live-server-amd64.iso in VMware. After the server is ready i did this.

sudo -i
apt update
apt upgrade
reboot

sudo -i
cd /root
git clone https://github.com/FOGProject/fogproject.git
cd fogproject/bin
./installfog.sh -C -K -S


cd ..
cd utils/FOGiPXE/
./buildipxe.sh

fog_error_1.5.5.log --> here
foginstall.log --> here
build.log --> here

Looks fine for me - but did not work. I will try it another setup later.

Edit: I am unable to upload my logfiles here - if i select a file for upload nothing happens - so i used pastebin, hope that is okay. Using CodeBlocks in the forum was to big.

@Sebastian-Roth thanks for your time I did the same with the same error … Fresh installation of ubuntu with a fresh fog server. I will try it again on other hardware and another setup later this week.

@Sebastian-Roth thank you for the reply and thanks for the link. I checked it with the apachectl -S but i am running only the two fog hosts - so it is okay. There is no apache default site availibe.

But i am on a new track now:

As you can see here there should be some cmds to check for certificates e.g. certstat - if this option is set in the general.h file. So i got the idea to check if sth. is availible.

After running into the error posted here i can press “s” for the ipxe shell - now i should be able to run the ipxe cmds (i think?!) but they are not availibe e.g. certstat “not found” - so i am not sure if the compiling is right here. Maybe we are missing the https, also selectable in general.h, or/and the whole certification instances.

I am very new to this compiling topic but i am trying to get into it - maybe you can help here or you got an idea to check for enabled modules in ipxe. thx.

@Sebastian-Roth yes, the istaller did rerun without a problem. After sone tests i copied the files from the /fogproject/ folder manualy. Same result!

There were no build errors running the script.

For now i edited the default.kpxe (not sure about the right file name by now) and removed the „s“ from the https connection to try normal http. Then i found the apache rewrite rule - after changing it and removing the rewrite, it woked! Sure, there is no „security“ by now but i know that the ipxe files are good and the chainboot is working.

On monday i will to look deeper in the rewrite rules, because the boot.php could not be found. Could be a certificate error but i am not sure if the ipxe error output should be different then. Could also be a broken link, but therefor it looks right.

Not sure where is the problem by now.

Hi,

is there an update?

i just installed a fresh Ubuntu 18.04.1 LTS and installed Fog 1.5.5 from git. I tried to configure it with SSL so i run the installer with --force-https, --recreate-CA and --recreate-keys and run into the error boot.php could not be found by the ipxe boot. Browsing with a browser works, after accepting the certificate. After a bit of google i found this thread here. So i tried to Re-buildIPXE as provided here in both ways without any luck.

As this thread from 2017 i not sure if it is still recommended?!

@tom-elliott okay, so i tested it with 50-55 * * * * to check if the “-” is a problem.

The fogscheduler.log found a wake on lan task that should run.

[10-25-17 12:49:52 pm]  * Task run time: Wed, 25 Oct 2017 12:49:52 +0200
[10-25-17 12:49:52 pm]  * Found a wake on lan task that should run.
[10-25-17 12:49:52 pm]  | Task sent to COMPUTER

But keeps on going …

[10-25-17 12:58:52 pm]  * Task run time: Wed, 25 Oct 2017 12:58:52 +0200
[...]
[10-25-17 1:00:52 pm]  * Task run time: Wed, 25 Oct 2017 13:00:52 +0200
[10-25-17 1:00:52 pm]  * Found a wake on lan task that should run.
[...]

This would confirm that sth. with the “-” is translated to “*” because than it would be * * * * which should mean “At every minute.” That would also explain why it started at minute 49 …

So i think there is a global problem.

@Tom-Elliott FYI:

If i use the “-” for a range of values e.g. 1-5 there is a problem. If i seperate the values like 1,2,3,4,5 it seems correct.

I will do some more testing…

@Tom-Elliott - thanks for your reply!

Yes, all other days work but only if i use it seperated. If i use it combined like 1-3 it ignores this value and sets it like an * because it takes the whole week.

Server: 14.04.1-Ubuntu x64
Fog: Running Version 1.4.4 | SVN Revision: 6077

Hi,
i have some trouble with the PowerManagement scheduled power tasks.

If i use the d-o-w option e.g. 1-5 for Mon-Fri like 15 8 * * 1-5 for a WOL-task it ignores the dow 1-5 and keeps starting on weekends.

If i use only one day linke 20 11 * * 2 it works fine and shows right in the fogscheduler.log.

If i use sth. like 20 11 * * 2-5 it shows next task

Task run time: Mon, 23 Oct 2017 11:41:18 +0200

But as the 2-5 says it should be 11:20 on every day-of-week from Tuesday through Friday.

I assume it is sth. with the syntax oder with the code. Could not find sth. similar in the forum or the wiki.

Some ideas here? My server-date is correct

Thanks!