This content has been marked as final. Show 4 replies
I would perhaps restart the service and see what happens. also maybe running a scan for orphaned objects may find something.
just use the api command "cleanupmachinegroup" to do that.
Thanks SafeBoot, worked like a charm. That command was documented for use on version 4.x and we're on 5.1.3, I'm a little concerned that it was needed.
should be documented in the v5 guide as well.
it's equally vaild - I guess something just crashed while doing the group update, maybe a network outage etc.