@deimos Latest stable version is 1.4.4, try this please. There’s lots of fixes in every release.

@redbob With the access control plugin. Enable the plugin system inside FOG Configuration -> FOG Settings, then install the access control plugin. There’s some threads here in the forums on how to use it.

@jgallo So, rebooting after you clear the cache nullifies the effects that clearing the cache does, because rebooting does the same thing. I’m trying to isolate if clearing the cache fixes the problems for you.

@jbranka4 said in Updated FOG now all Windows 7 machines attempt to pxe boot and just keep cycling through pxe:

We just did the latest update

We really need to know the exact version you’re on.

@jjcjr said in How to easily import/Export images between systems:

then it could easily be imported, scripted or automated.

This is what the API is for.

@jgallo Having cache in the RAM isn’t a bad thing - Linux does a really amazing job at managing memory, it’s just something about fog that causes the cache to not be effective (what’s cached is not what’s actually used often). cache size grows as the Linux kernel does stuff. The less stuff it does, the slower the cache grows. Eventually though - and by design - the RAM gets filled with cache in order to make future requests faster. Again, in the case of fog, what’s cached is not what is getting used over and over.

@sebastian-roth Just tested RC 9. The host doesn’t show up in the pending MACs report, but does show up in the ‘list all’ in Host Management, but is unapproved at that point. Clicking a little link towards the top of it’s general page will approve it.

So, from what I’m seeing, the pending MACs list has something wrong with it, but the auto-registration is working.

@jgallo Try clearing the cache the same way on one of the nodes, see if it fixes that node.

Hey there Canonical, you’re not doing yourself any favors when you change settings the admin has manually set. I hoped someone on your team would have read this thread and made changes accordingly to prevent the continuance of mayhem, but alas it seems nobody has… Don’t you have Google alerts setup when the words “Canonical” are used on-line?

@tian said in backing up data error:

@george1421 this should be the correct solution
We’re also on Ubuntu 16.04 and the fog installer is failing at exactly the same point. After running the commands to alter the root user in mysql the installer runs fine.
I think this problem re-occurs even when just updating the system by apt-get sometimes - so I am running the mysql alter commands every time after apt-get to be on the safe side.

I think you’re a victim: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy