Topics created by sudburr

Maybe FOG_PIGZ_COMP can be changed to just FOG_COMP or IMG_COMP
At the end of the day though, it doesn’t really matter.

And there was much rejoicing.

If you expand each option on the Fog Settings page individually, the missing bits are not visible. Only Expand ALL shows the missing bits and only at the top of the list, not where you’d expect them to be.

This wasn’t a problem with key sequence or even double entries as originally thought (though that could still cause similar issues).

However it was found and is now fixed.

@george1421 The changes have been made.

@sudburr This would do the same but give dates and no-longer active branches too. The count is adjustable. This is a snippet from something I’m working on.

git for-each-ref --count=10 --sort=-committerdate refs --format='%(committerdate:short)_%(refname:short)'

Thanks to Tom’s speedy remote work the problem was found and fixed with the release of 1.3.3.

@sudburr Not a guarantee, but you might try scripting the uninstall using the old fog client msi instead of the product ID.

@Quazz yeah, I just use snapins because it’s easier. Click click click and the exact group I’m targeting has the needed snapin assigned.

And, the host must be previously registered with the FOG Server, or if not previously registered it must be approved via the web interface when it shows up in pending.

Also - the host must be vista or newer. On Linux, Mono must be installed.

And - life is a whole lot easier if you don’t have the old FOG Client installed.

The server itself had no hosts; it’s my development server so I regularly blast it; and it was indeed waiting in Pending Hosts.

Thank you for clarifying what to expect .

RC 32 should address the problem you are describing.

Of note, this same issue was occurring on snapins as well.

Both elements should now properly work.

@sudburr Of course, but you can change where these are written to (in console).

Each of the services have a default tty (and they should all be different, though it wouldn’t hurt anything to have them on the same).

The idea, I think, is so make users more aware of the services and that they are running and any issues that might be happening. I don’t know how any information printed out by the services would be “sensitive” unless your file names are in such a way it might give out PII or confidential/sensitive information. In that case, though, you can just change the TTY for the services within FOG Configuration -> FOG Settings -> FOG Linux Service TTY Output (I think).

I mean following the steps I outlined above is how I got it to finally work. Assume a save and a hard refresh on a separate tab to achieve each = . Considering what I found with the storage group association of images yesterday I figured I’d try toggling some settings, and that included the Search vs List option.

It wasn’t until I performed a Search from the Images page that the LIST option setting began to work as intended.

Again, this is on an absolutely from-the-ground-up installation of CentOS followed by RC26. The only thing introduced other than my standard configuration was the importing of exports.

@sudburr what you performed is correct, if you already had a prior config laid out. Sorry I didn’t recognize this sooner but a fix for this has been added to the next working branch.

Essentially the variable was being set properly, but it was being overwritten when the fog settings file was imported.

Aha, that’s why I didn’t find that post in a search. Can’t keyword search attached pictures.

Changing mine to

FOG_URL_AVAILABLE_TIMEOUT = 3000

… fixed it for me. Thank you.

No issues. It just worked.

The Gen1 (Legacy) adapter appears to still be only 100Mb.

Wow … that one almost got lost to the mists of time.

Yes. An update.

I don’t remember precisely when, but I think it was soon after I made this initial post that it started working again.

Regardless, I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.

Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

Confirmed the issue and hopefully have it fully addressed now.

It was a bit of an issue, but ultimately very simple. The files were deleting at least on one node (where possible) but failing to iterate due to return which was meant to be changed to a continue.

After finding that out, the issue was the folder for images would still exist (the data would be removed though).

After some fairly thorough testing (I tested what I could, when and where possible) it appears I’ve finally addressed the problem. Trailing folders get removed as well as the contents of those folders.

I’m solving this, and the other, for now. Feel free to keep us posted though.

@Wayne-Workman What do you mean intermittent?