Thanks again Tom!

Well I ended up doing a fresh install of FOG (wiped existing FOG files and set it up again) and during setup I provided the password for MySQL this time. I have a GUI, so I’m going to continue testing and see if I hit any other issues.

I will do my best to figure this out! Thanks for the start.

Cheers.

@Tom-Elliott said:

0.0.0.0 just means to use any interface.

I believe just :69 means to use anything, so even if network is not up when it starts, it won’t crash simply because network does come up.

WiKi updated to reflect this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP#Ubuntu:

/tmp/pigz1 is a temporary location where data is streamed for compression/decompression. that part of your system seems to be running fine. what it sounds like, however, is that your drive is not being re-sized to fill the disk after imaging completes.
what version of fog are you using?
i’m assuming this is a resizable image, is that correct?

thanks Tom, that has us up and running!

I’m solving this thread. It was caused simply because I overlooked a while loop. What was a while loop should’ve simply been an if statement. Basically it was looping as long as poll was invalid, which if the connection is dropped (such as the case during an upload task to change from one checkin to another element) would cause it to loop repeatedly forever because the array no longer existed.

This should now be solved and I’m sorry. Version 4264.

4258 should fix this.

I teamviewered in. Found that the redirect to static/index.html was not something FOG Was causing.

The NAS was NFS Mounted to the FOG Server. But as they had found out, the NFS From FOG Couldn’t redistribute the share as NFS. Because of this, Storage Node was pointed directly at the NAS and volume of the NAS to allow imaging to occur. However, when going to FOGConfigurationPage it was attempting to go to the NAS’s management portal, and because it was invalid, it was being redirected per the NAS’s settings.

Changed the Node to the FOG Server proper information and FOG Configuration Page loaded with no issues.

Invalid security token is your problem here please go to host management find this relevant post and select reset encryption data they should correct your problem

Awesome. I will be back onsite tomorrow.

You folks are awesome.

@cg2916 Why not just use “resizeable” image types? This image type was developed specifically for the problem you have. And if resizeable works, there’s absolutely no reason to not use it.

@Wayne-Workman Rebooting didn’t help. I ended up running the installer again and that fixed it. I had some issues with the tasks not ending properly after it was completed and the service would get stuck. I just cleared the multicast tasks in mysql and restarted the multicast service and that seemed to work. Haven’t had any more issues since that happened earlier. Thanks again for all of your help.

That did the trick. Thank you. 🙂 Was so use to seeing installation finished that it was finished. But did realize it seemed to grab the kernels and client wayyy faster than normal. I’ll make sure to keep that in mind next time.

Well i tried to update to trunk with wget but did not think it worked. is it possible that it did install and thats what happened?

Thank you! It worked like a charmed.

@liquidprinter Since this thread is a year old, we need all of your specific details. Fog Version, Linux Distribution and Version, and the model of the target host you’re trying to network boot, if you’re network booting in BIOS mode or UEFI mode, and what boot file you’re using, and what you’re using to hand out the file (DHCP, ProxyDHCP).

Also, you might want to take a look at the WiKi, there are troubleshooting articles in there. Here’s one on TFTP: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

I confirmed and was working on a fix. While I was at it, I cleaned up the management page. This is now pushed. 4248 should correct these issues.

Thanks for reporting.

OK. That’s what I was afraid of. No big deal and life goes on. Strange that it didn’t take the settings though. Thanks

@Wayne-Workman

Wayne, I apologize I was in a huge hurry and was kind of freaking out, but once I calmed down, I realized I should’ve looked before posting. Sorry bout that, again.