Added nodes, updated everything to 3429. Can no longer image.

[Wayne Workman]

@saltlife3122 said:

when I download that what all do i need to do? I go to the GUI then download it. Then what?

FOG Configuration -> Kernel Update -> Download.

That’s it.

[saltlife3122]

save it over the previous bzimage

[saltlife3122]

when I go to the fog configuration even though i went to the 19.3 kernel it still says 4.0.2.
Still won’t work still get a bzimage error. The VM still quick images just fine.

[Wayne Workman]

If it still says 4.0.2, then something is definately wrong…

Can you doublecheck that FTP is functional? FTP is used to get the kernels.

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

[Tom Elliott]

Can you post a pic of the exact error?

[saltlife3122]

FTP is working, its enabled and running and I can get to the fog ftp site

[saltlife3122]

This is the error from physical machines. VM’s do not get any errors

[Tom Elliott]

@saltlife3122 said:

This is the error from physical machines. VM’s do not get any errors

Are you, by chance, using dnsmasq?

[saltlife3122]

not that I know of

[Wayne Workman]

Ok…

The issue is that path… three slashes, see them?

We know the problem now, just need to figure out why.

[Tom Elliott]

Chatted and found out the problem.

This was a two part problem.

Problem number one.

Location Plugin was installed, but no entries were made. I don’t know yet if there’s a bug specifically in this, but there was a location association at one point in time. This lost its association but made it so the default location was not set. This is why the http:///fog/service/ipxe/bzImage was display.

Problem number two.

The FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_PXE_KERNEL setting was literally set to /bzImage instead of bzImage

Any of the files being stated should not have a beginning precursor as such.

Hopefully we’ve helped out and helped figure out other means to troubleshoot.