Advice reqeusted to migrate MSR from Bare Metal to Container

[toggledbits]

Have you looked at the entity contents for groups>dgc_entrance_open? That's what it's complaining about.

[wmarcolin]

@toggledbits

I had not looked at it as an entity, but when comparing it now with others of similar group function, I see no difference in structure that might help understand the error.

Thanks.

[toggledbits]

You should have a file in the storage/entities/groups directory called dgc_entrance_open. Can you please post its contents?

[wmarcolin]

@toggledbits

{
    "id": "dgc_entrance_open",
    "type": "Group",
    "name": "DGC Entrance Open",
    "source_id": null,
    "_lastupdate": 1651610485346,
    "deadsince": false,
    "can_rename": true,
    "can_delete": true,
    "primary_attribute": "sys_group.empty",
    "_attributes": {
        "sys_group": {
            "members": [],
            "empty": true
        }
    },
    "actions": {},
    "capabilities": {
        "sys_group": {
            "attributes": {
                "members": {
                    "type": "array",
                    "default": []
                },
                "empty": {
                    "type": "bool",
                    "default": true
                }
            },
            "actions": {}
        }
    },
    "notify_member_changed": true,
    "serialize_version": 2
}

Thaks.

[toggledbits]

OK, and let's be clear... does this happen on every restart, and only on this global variable? You have cleared the alert and restarted and verified that the alert returns?

[wmarcolin]

@toggledbits

Every time I perform a restart, the error appears, and always and only in this variable.

I clear the message, restart the variable and everything is fine. If I restart the MSR again, then the whole error scenario comes back.

Thanks.

[wmarcolin]

@toggledbits

ATTENTION: I have just installed the new version 22123, a new installation procedure, and the error does not happen.

I have tested restarting the MSR by Service and Tools > Restart.

We can close this discussion.

Thanks.

[toggledbits]

OK, but just to be safe, please do the following:

1. Stop your Reactor service.
2. Remove the reactor.log file from the logs subdirectory.
3. Restart Reactor.
4. Post the log file.

I want to have a look from the start onward. Thanks!

[wmarcolin]

@toggledbits thank you for all your attention.
I tried to post the log here, but it exceeds the number of characters.
Can you indicate another place to send the file?
Thanks.

[toggledbits]

I'll send you a link via PM.

[toggledbits]

Got it. Looks good. Perfectly clean. There was an incidental issue where the DGC was delaying releasing notifications on a group if the group filtered out all of its entities. You might have noticed different behavior had a door been open at the time Reactor restarted vs what appears to be the more common condition that all were closed (thus empty group displaying the bug). Onward!

[wmarcolin]

@toggledbits