This is now fixed in svn/trunk/git whatever you want to call it.

I confirmed that it stores the IP and knows that it’s valid.

SVN 3861, FOG Version in cloud is: 4353.

Thank you,

@Wayne-Workman Sorry guys, was doing a Core switch replacement at my job. Imaging still works perfectly, in fact just uploaded an image about an hour ago.

@Isaac-Meidinger What, exactly, is the same issue?

Were you already in the process of imaging when you updated? Can you provide a screen shot? What kind of hdd’s are these? If they’re ssd’s, they need to be preformatted as most SSD’s require GPT structures, and my guess is the image you’re working with is MBR.

@Albatros Correct.

The Version of SVN is 3827, the Version in the cloud is different.

GIT 4274 has everything back in running order.

Correct.

Group reset encryption data added.

It is fixed at 4250.

The technician administering this particular FOG server has reported that the latest revision has resolved the issue.

Thank you @Developers !

I was able to fix the issue. It was looking for the file in http://10.105.2.253//service/ipxe/boot.php instead of http://10.105.2.253/fog/service/ipxe.boot.php. Fog was somehow stripped out in default.ipxe.

@Tom-Elliott Testing now.

As I’m setting the password variables in .fogsettings with single quotes as opposed to double quotes, this should be resolved even with $2 or other funny symbols that may have a different meaning in bash/csh/ksh/zsh/tsh/etc… shells. Hopefully this helps. I’m just solving for now. If you see the issue again, please just let us know.

I don’t know what you mean timeout?

Can you provide some screenshots?

My other guess is the webroot issue. Maybe try rerunning the install with, after updating to latest pull please:
./installfog.sh -y -D /var/www/html

The webroot issue should be fixed in SVN/GIT so I’ve solved this thread.

TO ALL: If you’re still having the webroot issue, and you’re on Ubuntu >= 14.??, try running the installer with:

If you access with http://IPADDRESS/fog
./installfog.sh -y -W /var/www/html/ -D fog/

If you intend to access with out the fog trailing:
./installfog.sh -y -W /var/www/html/fog/

I’m solving this. I added the very code to remove duplicates to the schema. So it is still possible, in the future, to have this same issue. However, for the time being this should be fixed.

@Tom-Elliott Ya that did the job. Tx for the info!

@el-psycho the new client can only be used with the development versions of fog. This is because the new client was coded along side the development versions. And believe me there are a lot of changes to make it work. The compatibility of legacy and new clients is still present, but 1.2.0 will NOT work with the new client.

@Wolfbane8653 said:

@Tom Elliott:

[fogproject:dev-branch] 1 new commit by Tom Elliott:
447a131: Update ipxe files to latest. Maybe fix escape sequences particularly frustrating to printers and file names. - Tom Elliott

Tom’s latest update has updated your ipxe files. If you use the kkpxe or any of the other pxe files please try testing around the other pxe files to see if this helps.

If not then we will have to report your Machine hardware (Make/Model) so the ipxe team can look into it.

Fixed.

@Wayne-Workman I actually created a fog database from MySQL Workbench with no problem, however, I didn’t realize my account doesn’t have a MySQL password, but the mysql and root accounts do and fog was using one of those! So, that’s why there was a permissions problem. I installed the trunk and built it and it worked! I did however, have to comment out the configureMySql call because it wasn’t defined in the trunk. I guess someone removed its definition so it failed because the installation.sh script still called it!
"I’m so happy… " I can now go on with my PXE thing and proceed with the software phase of my new server.