Upgrade to ignition 8.0.13 : Invalid configuration type hierarchy for node message?

[mazeyrat]

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 ?

[adam.todorski]

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).

[nicholas]

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:

[james_electriceng]

I am getting the same error. Has anyone found out a solution to this problem yet? I’m using 8.1.3.

[yin.cheng]

I am getting this error as well.. I am using edge 8.1.7

[joshdunstan]

Anyone get anywhere with this? I'm seeing it on 8.1.17

[glenfry1]

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.

[Daniel_Kareem_Tabet]

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.

[denji26]

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.

[Drew_Hitchcock]

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?

[framebuilder]

Same here on 8.1.35. Redundant setup. Filling up logs. Anyone have any info on this?

[pascal.fragnoud]

I'll bump this thread as I'm having my logs filled by this. Literally the 500 hundred pages are only this.
I can't see any consequences so far, except for the log flood.

[AnirudhVelamore]

Anyone know how to identify the “node” or the “parent entity”?

I’ve taken a look at tags and UDT definitions from a high level and didn’t find anything obviously wrong.

[Porter_Ellis]

This error flooded the logs so much that the gateway crashed. @pturmel, any thoughts on this one? Seems like the issue has been around for some time.

[pturmel]

I've never seen this one myself. I vaguely recall something like this in a release note.

[Steve_Laubach]

As some said in this thread, it seems to be linked to redundant failover. 2 other threads I think are worth checking out.

Redundancy's Synchronization Error

Hello everyone! I am trying to set the redundancy of a remote tag provider. I have the following architecture with four different machines: Main gateway, Remote Tag Provider, gateway redundant, tag provider redundant. I have set in the backup gateway, Standby Activity Level as cold. During synchronization, log throws the following messages: [t.s.internaljson ] [07:16:10]: Invalid configuration type hierarchy for node 'guid number'. Parent entity 'guid number' was not found, o…

An IA rep responded in this thread

[Perspective] HTTP Error 503 Service Unavailable

Hello. Since we've updated to Ignition 8.1.43 we've been encountering an annoying issue. Every morning, when we start up our system, Chrome loads up with a Error 503 Service Unavailable message. The browser automatically opens after around 5 minutes pointing to the login page of our project through a Windows Scheduled Task. We've never encountered this behaviour beforehand; moreover rebooting the system apparently resolves the issue. The gateway logs show a bunch of warning like this one at t…

Some of the messages indicate that it started after an upgrade on the system. If you can safely do it, I would break redundancy, upgrade both systems to the same version and then re-establish redundancy and see if it's fixed. You can also contact support and have them look at the backend db. Of course, make a gateway backup before trying this.