I’ve upgraded a 8.0.12 gateway to 8.0.13, I have some message:
INFO | jvm 1 | 2020/06/10 09:50:04 | W [t.s.internaljson ] [07:50:04]: Invalid configuration type hierarchy for node '02dce1a3-f032-4a9c-bf4e-09ed73168aee.f8cc51fc-8062-4adc-8109-37c248ac3920'. Parent entity '02dce1a3-f032-4a9c-bf4e-09ed73168aee' was not found, or not loaded in the correct order. provider=default
what does it means ?
I’ve seen the same thing on 8.0.12 with a cold redundancy pair, the errors stop when the cold standby node is shut down. No idea what the problem is (yet).
I am getting the same problem in 8.0.16, but they are constantly pouring in every second and flooding out useful messages. So, I am just blocking them by setting the logger level for this internaljson to error:
I am getting the same error. Has anyone found out a solution to this problem yet? I’m using 8.1.3.
I am getting this error as well.. I am using edge 8.1.7
Anyone get anywhere with this? I'm seeing it on 8.1.17
Hey Josh, shoot me email to me to support@icontrols.com.au. Have a feeling our support team may have seen this on a call a few months back.
Hey! Has anyone solved this yet? I am running into the same exact issue on 8.1.35 but I can't find many resources.
I also see this on 8.1.39 seemingly when the Main Gateway tries to take back over from the Backup Gateway after a failover.
Then floods the logs with thousands of errors.
Same here on 8.1.17. When I inspect, it says it's an issue with the backup gateway and references a particular tag provider. Does anyone know what causes this and how to eliminate the root issue?
Same here on 8.1.35. Redundant setup. Filling up logs. Anyone have any info on this?
