One node crashed this morning. I was rebuilding it. The node was still enabled in fog - and because it wasn’t responding it caused the above error and a chainloading issue on hosts. The node that was not working was not the node that technicians were trying to deploy from.

Great! Thank you!

Already fixed in RC-3

Already fixed in RC-3

@Wayne-Workman Tom posted a hot fix (i.e. you fix-it) for RC-2 here: https://forums.fogproject.org/topic/8172/if-email-when-complete-is-enabled-the-database-is-unable-to-clear-the-task/2

Already been corrected for. Fix will be in the RC-3 release.

For those that use the email functionality, please edit the file:

/var/www/fog/lib/reg-task/taskqueue.class.php

Go to line number 58 and replace the ‘sanpinjob’ with ‘snapinjob’.

Save the file and all should be well.

@george1421 and if I recall the access control is already built for 2.0.

While I agree plain removing it seems a bit harsh, it can still be side loaded. Remember, I maintain a backup of the version being installed. So the backup of the original web structure is still available, with the only exception being when one goes to install rc-3. The rc-3 backup will remove the accesscontrol. If you go to the rc-2 backup (from when you installed rc-2) you can still get a copy of the access control plugin. While not perfect and does require a little extra work, it is still relatively easy.

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.