@callcenter good, thanks!

Restarted FOGMulticastManager and it is working properly now

@Wayne-Workman : I will try as per your suggestion and update it

@Tom-Elliott Thanks Tom. I went ahead and deleted all the columns and just left the <mac> and <hostname> and they imported successfully.

@Quazz

Update to 1.4.0 seems to have fixed the issue with imaging.

So found the issue. Individual taskings would work, but group taskings wouldn’t. This is due to some checks added to ensure only valid taskings can be generated. The tests were looking for “Imaging tasks”, then “Snapin Tasks”, then “init needed taskings”. The memtest tasking is not considered an init needed tasking.

I’ve made the checks simpler with:

“Imaging tasks” -> “Snapin Tasks” -> All other and tasks appear to be working properly from the group page. Thanks for informing.

@Tom-Elliott

Well it does appear that it finished… I just didn’t see the play by play like the full wipe… SO that’s my fault!!

Feel free to close this ticket! Thanks!

I think Quazz is right. I was trying “sudo dnsmasq” to troubleshoot. Sorry - am very new to Linux. I think this issue is resolved, though PXE is not working, but I’ll ask about that in a new thread. For anyone reading about this issue, the steps in here will help set up dnsmasq, and answered my question.

@Thiago I think that’s what I needed to know.

If you need the directory listing, you might be better creating an index.php file that will generate the list of files for you.

You can even make them links so you could test downloads.

The idea is we use an API now and if the index file doesn’t exist (which it’s attempting to locate) it will attempt to redirect through the API. I just needed clarity on whether there was an actual issue of which you just let us know there wasn’t. It was just your “testing” that was failing (which is helpful, but not requried).

@safari2010 On screen where it’s giving the long warning, please say yes.

@zln1996
That’s awesome! Glad to hear you got it working. I figured that directory under run would have been created automatically when starting the process. How interesting. Good job and glad all is intact. Glad we were able to get you in the right direction.

Jason

Hello,

I’d like to close the topic. It was the solution.

Where is the button “solved” ?

Thanks.

Hello guys.

Finally, with wimboot systems work fine in all computer.

This was the code:

#!ipxe cpuid --ext 29 && set arch amd64 || set arch x86 kernel http://${fog-ip}/iso/asus/133/wimboot initrd http://${fog-ip}/iso/asus/133/BOOT/BCD BCD initrd http://${fog-ip}/iso/asus/133/BOOT/BOOT.SDI boot.sdi initrd -n boot.wim http://${fog-ip}/iso/asus/133/SOURCES/BOOT.WIM boot.wim boot

Thank all, a lot.

Sticking this link here for future readers:
https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

@plegrand psexec already has the ability to send commands to remote machines, I’m not sure why you would try to make psexec commands into fog snapins.

This whole thread seems really over-complicated.

Why not just bake-in some run-once functionality into your image? Windows already does this natively via the registry. Doing it for Linux images is trivial because SystemD is amazing.

@ttrammell
It looks like something similar when I had changed the IP and didn’t finish configuring everything. I had left out checking and configuring the Storage group/nodes.
If you have changed your IP(or maybe even Server name) try following these instructions:
https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address
The key part I missed(becasue I didn’t really use storage nodes) was:

Update the IP address for the storage node on the FOG system where you changed the IP address - Web Interface -> Storage Management
Make sure you actually click the node and check the IP setting.

that line in the bandwith.php file points to a location in /sys/class/net/<net_adapter_name>/operstate

I’m not sure if CentOS is diferent but my adapter name is eth0 so look for that in place of adapter name.
Im not sure if you can simply recreate it it if it doesn’t exist. It simply appears to display whether or not your adapter is up or not.

I also found this article but refers more to the fog client install.
https://forums.fogproject.org/topic/5926/change-fog-server-name

Hope that helps,
Jason

< facepalm >

Oh geez … okay, ignore everything. There is no problem other than that the switch servicing that bench had been reprogrammed. The ports used had been set to the wrong vlan; a vlan serviced by a FOG server that didn’t have the intended accounts.

… oy

@jaoyer said in IPXE Issues:

As far as the updating issue going from 1.30RC10 to 1.40 (detailed in my 2nd response), should I create new thread?

Yes.

@Tom-Elliott Changed teh memory_Limit in PHP made all the difference. Thanks man.

@vkenny The second element. (Single data store/server, 5 different nodes pointing essentially at the exact same spot.)