Skip to main content
Question

OPC UA Extractor Pipeline Notifications


Chris Selph
Seasoned
Forum|alt.badge.img

We have an OPCUA extractor pulling data from an Ignition OPC Server which had been working well at a customer site for weeks. This is a try before you buy scenario so the issue of data loss notification is important and that we respond back to the customer as to reasons why this occurred.

It seems something changed on the Ignition OPC server preventing the extractor from accessing the tag data.

We can see that data stopped and when using the Cognite chart.

However we did not receive an email notification of a pipeline failure over several days.

Upon restarting the OPC Extractor service, we did receive the pipeline failure email as seen below. 

We know the data access problem is in the OPC Server so not trying to get help from Cognite with that but It seems that the pipeline SHOULD have sent a failure notification WITHOUT having to restart the service. That is the important fact to bring to Cognite’s attention.

Failure email message:

Error: Root node does not exist: ns=2;s=[IAWAT_Tags_Enterprise]/XXX/IAWAT-2119/SnackPack at Cognite.OpcUa.Browse.Browser.GetRootNodes(IEnumerable`1 ids, CancellationToken token) at Cognite.OpcUa.Browse.Browser.BrowseNodeHierarchy(IEnumerable`1 roots, Action`3 callback, CancellationToken token, String purpose, Nullable`1 nodeClassMask) at Cognite.OpcUa.NodeSources.UANodeSource.LoadNodes(IEnumerable`1 nodesToBrowse, UInt32 nodeClassMask, HierarchicalReferenceMode hierarchicalReferences, String purpose, CancellationToken token) at Cognite.OpcUa.NodeSources.NodeHierarchyBuilder.LoadNodeHierarchy(Boolean isFullBrowse, CancellationToken token) at Cognite.OpcUa.UAExtractor.RunMapping(IEnumerable`1 nodesToBrowse, Boolean initial, Boolean isFull) at Cognite.OpcUa.UAExtractor.RunExtractorInternal(Int32 startTimeout) at Cognite.OpcUa.UAExtractor.Start() at Cognite.Extractor.Utils.BaseExtractor`1.Start(CancellationToken token)

I did not see this message about the root node in any of the extractor log files UNTIL the service restart. 

2 replies

Mithila Jayalath
Seasoned Practitioner
Forum|alt.badge.img

@Chris Selph thank you for reporting this. I’ll inform the engineering team.


Chris Selph
Seasoned
Forum|alt.badge.img
  • Author
  • Seasoned
  • 27 replies
  • January 8, 2025

more info:

note the run history does not reflect a problem until after the extractor was restarted on JAN 7.

The run history now reflects the error so it seems there are comms checks in the extractor startup routine that are not executed ongoing unless it sees a problem on startup.

 

Also, prior to extractor restart the Status was reported as “Seen”.

 


Reply


Cookie Policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings