You need to CAPTURE the image, not deploy.
There will no file with the name in the address (/bin/fog.download).
The error message you’re seeing is coming from that location in the init.
Open your gui, cancel the curren ttasking for that host.
Go to the host in the gui
Go to basic tasks.
Choose “Capture” which it sounds like you’re trying to do.
@Wirefall said in FOG will not boot - "Failed to get an IP via DHCP!:
@Wirefall Update: Looking at the daemon.log, it appears that the client makes a DHCP request and is provided an IP from the FOG server of X.X.X.11. There is then an error message of “init.tftpd[XXXX]: tftp: client does not accept options.” A new DHCP Discover is then completed and the client receives X.X.X.10 (the first available entry in the DHCP pool).
The “tftp: client does not accept options.” message is a misnomer. It doesn’t mean anything in regards to the problem(s) you’re seeing. The DHCP request appears to be the issue but only within the init itself. This leads me to think the switch is potentially a “power saving” switch?
We’d also need to see ifconfig -a rather than just ifconfig (The latter only shows active devices).
Just a simple question, seeing as you state the device id information is 8086:1539 (which has been in the linux kernels for a very long time), does your registration issues happen on multiple systems of the same model or just this one system? I only ask because this isn’t seeming to make sense. The only things I can think of:
@Sebastian-Roth It’s funny you mention the idea that the kernel is the problem (I didn’t notice the error message until you pointed it out). My Next question was to ask about using older kernels.
To install 1.3.1-RC-1 you will need to change branches with:
git checkout dev-branch
Then run the installer.
If the image is set to the host a choice will be present but the assigned image will be selected. The choice will be auto selected on timeout if left alone.
@joshuaparker What fixed the issue? The removing the id=‘login-info-form’?
I’ve added a schema change for 1.3.1-RC-2 that is addressed under “General Settings” from the fog settings page. This is just a simple checkbox. It’s default status is “checked” of course, but can be adjusted so you don’t consistently need to make changes during updates.
I feel I need to clarify, the asking of the password was blank should still work. However if you are installing with the -y argument this question would not come up.
FOG does not default to installing a repo called 'ppa:~ondrej/ubuntu/php-${php_ver}` as you’re seeing.
Please delete the repo='php-${php_ver}' line from yoru fogsettings file and reinstall.
Try changing the “type” of image (resizable currently) to “not resizable”.
@Steuve68 Are simply trying to request that you can sign in using different domains? This is more a feature request than a problem.
Changing the username attribute really shouldn’t be done. We allow it only because we don’t know how your LDAP will operate. This is why the “template” is there. It defines the defaults that SHOULD work, but allows you to make changes to exactly how your information is.
To my knowledge, you cannot sign in as an Active Directory user using the mail attribute. You CAN sign in using the <username>@<domain> or <domain><username> but this is not at all using the “mail” attribute.
Not a big issue I suppose, but will be fixed for the RC-4 release.
If you absolutely MUST test it out try:
wget -O /var/www/fog/lib/pages/reportmanagementpage.class.php https://raw.githubusercontent.com/FOGProject/fogproject/30b44f6f453a3d7b63994a5be5fe44a2334765bc/packages/web/lib/pages/reportmanagementpage.class.php
@FallingWax Check the other post we’re playing tag between?
Is your Windows 10 image an OEM type or Volume License type?
TO me, this message appears to be coming from the item that’s booting, not a problem with the ipxe file in use. Maybe we can see what it is that’s booting after the ipxe file get’s loaded?
You aren’t the first, and probably won’t be the last. (Hopefully you might be).
I’m taking an approach that is untested a bit, but should fit the bill hopefully.
My change in thought is if that portion is “met”, I will take the partition number and add it to the “fixed size partitions” file. It won’t try to resize the partition and it should get you on to the next partition.
Please install the latest RC (reinstall if you already did install it) and you should have the upload capability back.
Thanks,