Kernel Update Failed transfer

[Trev-lchs]

hmm having logged into the server using putty, giving myself sudo -s, copying and pasting /opt/fog/.fogsettings, i get access denied.

[Trev-lchs]

@george1421

root@fog-03:~# /opt/fog/.fogsettings
bash: /opt/fog/.fogsettings: Permission denied
root@fog-03:~#

[george1421]

@Trev-lchs you may need to be root or sudo it to view the file sudo cat /opt/fog/.fogsettings

[Trev-lchs]

@george1421 thank you, that worked

[Trev-lchs]

@george1421 it is asking me to enter a new password for fogproject (in the putty command line) is that the one i just copied from the file less the ’ at each end?

[Trev-lchs]

@george1421 i do notice that the password in settings, tftp is completely different to the one in the file, can i just paste the one copied from the file into the gui on fog settings, tfpt?

[Trev-lchs]

@george1421 Magic, George i did paste the password found in the file into the GUI at settings/ TFTP password, and it worked. fab the kernel updated.

[george1421]

@Trev-lchs Sorry I had to step away for a bit, it looks like you have it. The password found in the .fogsettings file should always be considered the master password since the fog installer/upgrade script will always reference this password when making system adjustments. If for some reason the web ui passwords get out of sync with this password you will get random failures as you saw.

[Trev-lchs]

@george1421 Thanks George, just have to work out why the laptop wont boot info fog using uefi but i have raised another question on that, that was why i was trying to update the Kernel in the first place.

[george1421]

@Trev-lchs OK just for clarity the kernel is the FOS Linux kernel that does the imaging. That is independent of the pxe boot loader (that creates the FOG iPXE menu). Difficulty pxe booting then should be focused on undionly.kpxe for bios and ipxe.efi for uefi based systems.

[Trev-lchs]

@george1421 Yep thanks for your help George, we have it pixie booting now, unfortunately, on checking it this morning the Tech had not switched secure boot off in the laptop bios. due to the other issue i had been having i thought it was FOG, FOG is blameless in this instance.