@Tom-Elliott said:

If you don’t mind opening a separate thread please regarding this now new issue. With the new thread can you post the fog servers Apache error logs?

No problem: https://forums.fogproject.org/topic/5822/checking-in-error-on-git-7428

Thanks for your help again!

@Uncle-Frank Excellent! I tried that and it worked! Thanx so much.

Ask for WiKi access here: https://forums.fogproject.org/topic/1341/requests-for-wiki-access-ask-here. That’s where Tom keeps track of it.

Also, take a look at this: https://wiki.fogproject.org/wiki/index.php/WiKi_To-Do_list

that fixed it thanks

lol I need a Fedora 22 article now… just copy and paste I suppose, and replace yum with dnf lol

@salginer Not a problem at all. When this happens - 99% of the time it’s due to dual DHCP or Rogue DHCP setup. That’s why I asked this first. Glad you got it going! 🙂

@Tom-Elliott Yes reenabling capone fixed the iPXE issue

@xcvtop said:

@Wayne-Workman Hi I am going to try fedora. Is there a link to fedora 21 you would recommend as safe to download? or is it literally as simple to to install on Fedora 22 and change “yum” to “dnf” in the commands?

The FedoraProject hosts torrent files for Fedora 21 and YES they are COMPLETELY legal to use - because the software is open source and free, and p2p is legal as well when used legally. The torrents hosed there are safe - and come with hash values of what the files should have. So what you get would be legit.

Also - you can use Fedora 22 as well - and just change yum for dnf - and skip the MySQL stuff, the installer will install mariaDB instead of MySQL for Fedora 22. There are notes on this at the bottom of the article.

@kverkiss said:

@Wayne-Workman I have set a DHCP reservation for this laptop in W2K8 server. I am able to define a bootfile for this specific laptop, in this case to boot realtek.kkpxe. This should solve the problem for the laptop not able to boot over pxe.

Great! Just a hint on this: ipxe.kkpxe should have the realtek driver included. Just undionly.kkpxe comes without native drivers.

That said I still think that you are good to go with your solution. Some buggy BIOS versions just won’t run with the normal kpxe files and you just have to come up with a special solution for those.

@Wayne-Workman @Tom-Elliott Solved the problem. Somehow curl had a problem with me being behind a proxy, no idea why though, never had this problem before. As a result, bzimage, bzimage32, init.xz and init_32.xz were not downloaded correctly. I solved this problem by using wget to manually download those files (the download links are in /lib/common/functions.sh).

Also another problem in /lib/common/functions.sh: I was not able to add the repository for php5-5.6, so I had to comment out those lines. In my case this is not a problem, as I’m now using Ubuntu 15.04, which already has php 5.6 preinstalled (at least if you dist-upgrade and update).

Thanks again for the very fast help. 🙂

@Junkhacker Technically yes.

Problem totally solved.

Imaging client work now.

@Jordonlovik With the exception of the /etc/exports file and creating the /dev folder and the .mntcheck files

If the storage that you add is local, You not only add the new directory to the Storage Management area as a new storage node, you also have to add entries to /etc/exports and create the /dev folder and the .mntcheck files

4696 should fix this for you now.

Thanks for reporting.

@sarge_212 What version?

this problem is believed to be resolved now, thank you for the bug report.

@lebrun78 There are no files to change.

The advanced menu is purely a GUI item. From the GUI goto FOG Configuration Page->PXE Settings->Advanced Menu

@Wayne-Workman I have. I can open into ftp on any device to the one node but not the node or server. As far as I can tell all of the config files match.

@Tom-Elliott said:

Can you try reupdating your kernels/ and/or re-running the install if you’re running dev version? I’ve updated the kernels to simply remove the qmi_wwan drivers from the mix. From my reading this should essentially keep the GOBI card from loading with the FOG inits.

Hi
same problem for me
using the kernel 4.2.0 of September 14, 2015 doesnt change
When i’m doing a quick registration and inventory (or quick image) it loops on starting wwan0 interface
Any ideas ?

What has changed in your environment between now and the last time you were able to image? Server change? DHCP change? New firewall? Perhaps it’s an IP Conflict? Did the V-LAN assigned to the fog server change?

Have you tried a different host? Are all hosts doing this?

And the final question is, do you have a reason why you are still using .32 ?