@Junkhacker Alright I disabled IMAGEREPLICATORGLOBALENABLED and that process went away. Thanks.

@Junkhacker Alright I disabled IMAGEREPLICATORGLOBALENABLED and that process went away. Thanks.

@Junkhacker /opt/fog/snapins

Sorry for the confusion earlier with us all participating here, I should’ve introduced myself.

@andjjru OK I discovered the IGNORE option and it appears to have run on 5025 hosts. No noticeable improvement in CPU load still, so probably need figure out that error.

mysql> UPDATE IGNORE hosts SET hostPubKey="", hostSecToken="", hostSecTime="0000-00-00 00:00:00";
Query OK, 5025 rows affected, 21415 warnings (0.43 sec)
Rows matched: 21415  Changed: 5025  Warnings: 21415

@Wayne-Workman I tried running that command from the wiki and received an error.

ERROR 1292 (22007): Incorrect datetime value: '0000-00-00 00:00:00' for column 'hostSecTime' at row 1

Alright, I’ll just go scrub them from the database then. Thanks, Tom.

I put in the full MAC in there and saved but I’m still seeing the MAC under pending and on a host I picked out from the list. Is there anything else I need to do? Do I just need to be patient?

Well, look at that. “[FONT=Ubuntu][COLOR=#555555]FOG_QUICKREG_PENDING_MAC_FILTER” is the setting I take it?[/COLOR][/FONT]

We had an issue recently where a software VPN MAC address was picked up by the FOG client on a laptop and accidentally added by someone (me) as an additional MAC. Since the VPN is installed the same and has the same MAC address on all the laptops it’s on, this caused quite a few laptops to rename themselves once taken offsite before we realized what was happening and deleted the offending host from FOG. We now know better and to be more careful in the future, but is there any chance of a safeguard to this sort of thing in the future?

edit: Or does anyone have any ideas on how to blacklist one MAC address from being added to the database?

Thanks, that’ll work well enough for now.

With the newest version of GroupManagementPage.class.php, clicking on a group from search results takes several minutes to load, as do most changes to the group once it finally loads. During these times, apache is pegging a CPU core or two.

Tom, seems that the fancy new features on the new group page are really slowing things down for me. Could you make a new version of the “orig” file with the AD settings fixed the same way?