For now I’m solving this. I realize the issue at hand is likely still there, but this (at this point) is not a problem of FOG or the FOG Client in a “bug” form. This seems much more likely to be a problem simply with disk space. Of course feel free to post info as we find more info out.

@JJ-Fullmer no it would not. The idea is to get a good working list of issues that will then be addressed for RC 2

@Wayne-Workman I suspect all is already fixed in the working area. You can create the log, and if you can see when/where/how the change happened, it certainly will help. I’m 98% sure it’s a specific set of actions necessary though, which is why I can’t seem to replicate it.

I’m certain it has nothing to do with the location plugin, just in case you were going to try with and without the plugin installed.

I’ve solved this thread so I don’t go nuts thinking I have keep finding and fixing this issue. Filenames with spaces (as well as other special characters) will be replaced with _ and this will be available to the next RC release.

@Tom-Elliott Today we tested with Version 1.3.0-RC-1 (SVN Revision: 5935) and the “Chainload failed” message still appears with exit type “EXIT”.

But since the exit type “REFIND_EFI”works, we’re OK with that.

Beauty. Thank you.

@Tom-Elliott My apologies, this can be marked as solved. I was restarting fogservice to test for the popups for shutdown, and restart tasking; however restarting the fogservice doesn’t really reset the client like I thought. It requires that the client checks in on it’s normal time ( sleep service time) for the popups to appear.

Update. It will all be fixed.

I’m solving for now as I’m fairly sure this is fixed. Of course feel free to test and update this thread as any other information comes forward. I’ve tried to test, but too many other things going on at the moment.

If you update again, I’ve taken (I think) a cleaner approach to showing the membership list information. It should still work, but also no longer timeout. It should even be “faster” than it was before.

I’ve also heavily modified the deploy functionality from groups as well for a similar effect, but it is a little harsher on speed as it has to load the object in an iterative fashion, versus try to obtain all objects all at once.

@Tom-Elliott Thanks, that would be really helpful to a lot of people I feel. It’s of course possible to setup a putty session or something, but having keymaps in debug mode sounds awesome.

@x23piracy Deleting images from select box will not remove the files. This is somewhat intentional. The image itself being deleted was a bug and is now fixed. Thank you.

@Tom-Elliott I think we can mark this as a one off problem. Maybe I missed a step when I migrated the old images. Thanks for looking into it.

@dolf Simple doesn’t get the job done when you’re trying to measure bufferbloat, or other multi-variable problems 😉

Check out Flent: https://flent.org/

I’ve solved this for now as the other thread is also reporting as solved since switching to ksort from asort.

@Tom-Elliott Sorry for the delay… patch week and all that fun.

I ran with disabling dynamic memory for other VMs until today. I updated my dev server to build 8597 and kept the 4.6.2 that the installer downloaded today (2016/07/14) and the issue appears resolved.

Confirmed fixed, the client is now showing in the logs the scheduled power task.

I’m pretty sure it does fall on the installer already.

I’ll double check just to be sure:

1 configureSnapins() { 2 dots "Setting up FOG Snapins" 3 mkdir -p $snapindir >>$workingdir/error_logs/fog_error_${version}.log 2>&1 4 if [[ -d $snapindir ]]; then 5 chmod -R 775 $snapindir 6 chown -R fog:$apacheuser $snapindir 7 fi 8 errorStat $? 9 }

That’s the script portion in the installer’s functions.sh file.

I see what’s wrong now. Thanks for leading me to it. Yes, Servers were getting the information set, but plain nodes were not. Should be fixed in latest. Thanks for reporting. Also fixed a few minor issues while I was there.

This is solved as the version is now operational again, though Sourceforge is still DITW (Dead in the water) at this point.

@Tom-Elliott yes it’s working again, ty.

alt text

Regards X23