UDT deletes standard tags after Gateway Restart

Ignition
1

Hello, We have v8.1.17, I've been programming since v7.8 on the same server in 2018. Two weeks ago I made some UDTs for a new process I'm running. The UDT was working fine on several machines. Last Monday, I found that a few tags were missing from the UDT which broke the logic. It wasn't a problem, I added them back. Today when I came in, those same three tags were missing after the restart. Its the strangest thing, I've never had a UDT change itself before on this system. These tags are very basic. Any idea why they keep dropping?

I'm losing currentTime, cycleLast and cycleSecondsCurrent. Nothing else goes missing but these three.

Capture
Capture795Ă—160 17.1 KB

2

Have you looked through your wrapper log yet? I'd check around the time you added them back (to see if that threw errors) and shortly after restart (to see if they saved but didn't restore).

3

It looks like the wrapper had cleared from a couple of dead machines spamming logs. I deleted them out so the log will be cleaner the next round.

4

The three that were disappearing, I ended up naming them '_old' and writing in new ones with the same coded and name as the original. This morning, after a weekend power cycle, all the '_old' disappeared but the new ones persisted. Its as if the issue was copy and pasting in the three tags put them in a RAM state and were lost after a power cycle. Got to be some kind of bug in the version I'm running. Its all good now.

5

Hi ,same accident happened to my machine . Any advice how to retrieve deleted tags in the UDTs ? , what I did is some changes in CSS files then I increased the rams in ignition.conf file then restarted the gateway .

6

Interesting….just had a client call yesterday…two tag members disappeared from a UDT…8.1.38. And these tags were copies of two other tag members that persisted. Original two tag members named open_pb and close_pb, copies were open_pb2 and close_pb2. The pb2s disappeared.

7

mine is 8.1.144

8

I confirmed today and was able to repeat the issue. I’ve yet to examine the wrapper logs. For now, we re added the tags again, but not through copies, but new instances.

9

I went to check wrapper logs but unfortunately they were full of database errors…something else they have going on.

But I did find in the system logs alot of errors that are associated with the tag provider that lost the UDT member tags.

The error is [tag provider-xyz] Will perform full pull. Reason: redundant provider on local side has no data.

Then redundancy errors that state “error applying full tag state”

Perhaps the tag provider isn’t synced on the redundancy and when the primary gateway is lost, the redundancy is missing UDT tag members?

10

This feels like the changes are not getting written to the config.idb database. If someone runs into it again, if you can DM me the following, it would help to try and figure out what is going on:

  1. Provide the Tag id for the member that is disappearing:
    1. Right click the UDT Definition Member
    2. Select View Tag Diagnostics
    3. Take a screenshot of the full Tag Id (I can copy the value from that and we haven't fixed this in a way where copy/paste works)
  2. Do the same for one of the members that never disappears
  3. Provide a zipped copy of the <ignition install directory>/data/db/config.idb file
  4. Provide the wrapper.log files
  5. Provide the approximate timestamp the member tags were added back

Garth

1 Like