Topics created by LPetelik

@george1421 We just ran the engine update. Thanks for those links. We’ll watch it for a bit to see how it looks. The GUI is a bit slow at the moment, hoping that clears up.

On a side note, while working with this issue, we ran .installfog and during the install it picked a new STORAGENODE MYSQLPASS password that had a closing bracket in it. It broke the node’s connections to the master even with the password updated in all the spots it should be. Once we created a new SQL password (on a whim to test, without special characters) and updated it in .fogsettings, reran the .installfog file, the nodes started talking to the master again.

I think we are in much better shape. We need to fix our node password issue and start imaging again to know for sure.

@tom-elliott When I updated the master to the working branch, the three nodes immediately reconnected. I then updated the nodes too. (Two nodes are offline, will get them updated when they get back online). I also realized that some of the memory in the server wasn’t showing up. I think that is a large part of the problem. Ordering some more now…

@wayne-workman Thanks. I changed it to 15 minutes. I’ll see how that does.

@wayne-workman Thank you. So far we seem to be working through them but we aren’t quite back to normal yet.

This is solved from a FOG point of view.

The problem was that a user replicated several large images overnight and Hyper-V expanded the VM, choking the main servers.

Thank you for all of your help @Sebastian-Roth!

@LPetelik Great idea, I think this would be very useful.

@xx23piracy Good catch!

I reviewed them and yes, they are laptops. I tracked one down and yes, it is adding MAC addresses that it previously didn’t have a record for. It just worried me because the hosts already existed and have been there for a while then it all the sudden started adding all these extra addresses.

So…resolved it looks like. Thanks!

It may be possible that your browser extensions are blocking the script. so check it or disable all the browser extension once.

There are many ways to accomplish this, but the simplest was to just edit the variables that define the booturl when the location plugin is enabled.

This has been added and pushed.

The update fixed the issue. Thanks for the quick response.