Host is NOT Registered! tasks not processed

[Tom Elliott]

@Eldorado If you’re running the latest version, is there a reason you’re not able to use the already installed .iso file?

[Eldorado]

@Tom-Elliott

Hi Tom,

the current .iso i’m using has the embedded script. Sebastian has asked me to run something different other than what I have.

[Eldorado]

@Sebastian-Roth said:

@Eldorado Try using this as embedded script:

#!ipxe
dhcp
chain tftp://ip.of.fog.server/default.ipxe

By the way, you don’t need to burn CD/DVDs every time you change iPXE. You can generate iPXE image to write onto USB key…

Hi Sebastian, thank you for the suggestion.

I tried what you did, and i’m getting this error at boot:

tftp://#.#.#.#/default.ipxe... ok
params: command not found
Cound not boot: Exec format error (http://ipxe.org/2e022001)

Here is the content of my default.ipxe file:

#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain http://#.#.#.#/fog/service/ipxe/boot.php##params

[Sebastian Roth]

@Eldorado Well, add PARAM_CMD when building on rom-o-matic.eu

Tom was asking why you don’t use the ISO provided by FOG? See in your /tftpboot directory on the FOG server. There should be an ipxe.iso file that you can use. It hast got an advanced ipxe script embedded - same as all the other iPXE binaries you see in that directory.

Take a look at the script. It does some checks but essentially it does just get an IP via DHCP and then loads default.ipxe…

[Eldorado]

@Sebastian-Roth said:

@Eldorado Well, add PARAM_CMD when building on rom-o-matic.eu

Tom was asking why you don’t use the ISO provided by FOG? See in your /tftpboot directory on the FOG server. There should be an ipxe.iso file that you can use. It hast got an advanced ipxe script embedded - same as all the other iPXE binaries you see in that directory.

Take a look at the script. It does some checks but essentially it does just get an IP via DHCP and then loads default.ipxe…

Hi Sebastian - When I look at the Fog tftpboot folder, I see:

boot.txt
default.ipxe
ipxe.kkpxe
ipxe.kpxe
ipxe.krn
ipxe.pxe
memdisk
pxelinux.0.old
snponly.efi
endionly.kkpxe
undionly.kpxe
undionly.kpxe.intel
undion.pxe
vesamenu.c32

I don’t see an ipxe.iso file.

[Sebastian Roth]

@Eldorado Oh well, I somehow thought that you are running FOG trunk. But looks like version 1.2.0 by the directory listing you just posted. You can download the latest ipxe.iso here (click ‘view raw’).

[Eldorado]

@Sebastian-Roth said:

@Eldorado Oh well, I somehow thought that you are running FOG trunk. But looks like version 1.2.0 by the directory listing you just posted. You can download the latest ipxe.iso here (click ‘view raw’).

Thanks - I’ll look into that…

having said that - your suggestion in the first post to run the default.ipxe rather than the boot.php file worked! everything is working as expected now once I added the PARAM_CMD file…

Thank you so much for everything!

[Eldorado]

@Eldorado said:

@Sebastian-Roth said:

@Eldorado Oh well, I somehow thought that you are running FOG trunk. But looks like version 1.2.0 by the directory listing you just posted. You can download the latest ipxe.iso here (click ‘view raw’).

Thanks - I’ll look into that…

having said that - your suggestion in the first post to run the default.ipxe rather than the boot.php file worked! everything is working as expected now once I added the PARAM_CMD file…

Thank you so much for everything!

Spoke too soon -

it’s registering the host now (and it shows on the menu screen it’s registered).

I am now successfully able to push down tasks from the server. I’ve started memtest, and tried to trigger an antivirus scan (even though the av scan fails, it still attempts to run at boot).

But now it won’t break out of the task… do the tasks need to complete fully for the server to stop sending it down?

For example, here is my experience:

1. create memtest task.
2. task runs.
3. I break out of task early and reboot.
4. client reboots and runs memtest again.
5. I have to delete the task on the server to allow it to boot back to the menu.

Here is what i’m expecting:

1. create memtest task.
2. task runs.
3. I break out of task early and reboot.
4. client boots back to menu, and server marks task as completed.

Is my understanding correct?

[Sebastian Roth]

@Eldorado What you experience is perfectly fine. The clients shouts back to the server not when it starts a task but when it finishes! You need to cancel the task in the web interface to stop the client from booting into it again and again…

[Eldorado]

@Sebastian-Roth said:

@Eldorado What you experience is perfectly fine. The clients shouts back to the server not when it starts a task but when it finishes! You need to cancel the task in the web interface to stop the client from booting into it again and again…

innnnteresting.
I’ll give it a try… this is great… lol thanks for everything!