ipxe login after upgrading to latest trunk + no such file or directory
-
@Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:
nd the fog version?
version: 8093
-
@Cavender Oh sorry… I must be blind. It’s been a long day.
Where does it say “no such file or directory” ? Can you give a photo or screen shot?
-
I see this at quick registration and image download. -
@Wayne-Workman
it says:loglevel=4… No such file or directory (http://ipxe.org/2d0c613b)
Could not boot: No such file or directory (same ipxe url)
Same error at quick registration and image download -
@Wayne-Workman
…here’s the screen shot -
@Wayne-Workman
…a screen shot you can actually read… -
@Wayne-Workman
I’ve gone through:
cat /etc/vsftpd.conf
sudo iptables -L
sudo passwd fog
/opt/fog/.fogsettings
Interface = eth0
FTP Path
Permissions - set to 777 for testing
Hide Menu is un-checkedAll looks good, though I still am prompted for menu login and registration / image download says “no such file or directory”. I know I’m completely missing something…just don’t currently see what it is.
-
@Wayne-Workman
I do see:
PHP Warning: fopen(./languages/en_US/gpl-3.0.txt): failed to open stream: No such file or directory in /var/www/html/fog/lib/pages/fogconfigurationpage.class.php on line 58
and
PHP Warning: ftp_rename(): Rename failed. in /var/www/html/fog/lib/fog/fogftp.class.php on line 168 -
@Cavender the ftp rename error would indicate most likely an FTP credentials issue. This article has everything you need to solve that: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
For this other error, well it’s really vague. Firstly, it would appear the background image is being loaded properly because it’s white.
What boot file do you have set in DHCP?
-
@Cavender Can you please pull up the GUI->FOG Configuration Page->FOG Settings->TFTP Server
Please post a screenshot of the values there?
-
@Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:
What boot file do you have set in DHCP?
I’ll go through the article. Where do I look to see what boot file is set in DHCP?
-
@Cavender It depends on what is doing DHCP. For windows, it’s just DHCP option 067.
-
-
@Wayne-Workman
Fog serves DHCP on a separate network -
@Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:
@Cavender the ftp rename error would indicate most likely an FTP credentials issue. This article has everything you need to solve that: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
I’ve gone through:
cat /etc/vsftpd.conf
sudo iptables -L
sudo passwd fog
/opt/fog/.fogsettings
Interface = eth0
FTP Path
Permissions - set to 777 for testing
Hide Menu is un-checkedAll looks good, though I know I’m completely missing something…just don’t currently see what it is.
-
@Cavender Well if all that has been set and verified, then it should be fixed. If you can upload successfully, then it’s fixed.
-
@Wayne-Workman said in ipxe login after upgrading to latest trunk + no such file or directory:
@Cavender Well if all that has been set and verified, then it should be fixed. If you can upload successfully, then it’s fixed.
That’s why I’m stumped. Registration / Imaging still says “no such file or directory” and I still get a login prompt for the main menu.
-
@Cavender Well the two are separate issues. However in another thread we may be onto something… Another person is having the same issue: https://forums.fogproject.org/topic/7774/default-ipxe/2
-
-
@Wayne-Workman said in [ipxe login after upgrading to latest trunk + no such file or directory](/topic/7763/ipxe-login-after-upgrading-
What boot file do you have set in DHCP?
subnet 172.16.0.0 netmask 255.255.255.0{
option subnet-mask 255.255.255.0;
range dynamic-bootp 172.16.0.10 172.16.0.254;
default-lease-time 21600;
max-lease-time 43200;
option routers 172.16.0.1;
option domain-name-servers 8.8.8.8;
next-server 172.16.0.33;
class “Legacy” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00000”;
filename “undionly.kkpxe”;
}
class “UEFI-32-2” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00002”;
filename “i386-efi/ipxe.efi”;
}
class “UEFI-32-1” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00006”;
filename “i386-efi/ipxe.efi”;
}
class “UEFI-64-1” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00007”;
filename “ipxe.efi”;
}
class “UEFI-64-2” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00008”;
filename “ipxe.efi”;
}
class “UEFI-64-3” {
match if substring(option vendor-class-identifier, 0, 20) = “PXEClient:Arch:00009”;
filename “ipxe.efi”;
