Failed to start OPC-UA Connection for Source

0

Hi,

Objective : I am working to collect the data from Kepware OPC server [ EC2-Windows] to IOT sitewise through Gateway & OPC UA source [ EC2-Linux]

As per the documentation, I deployed Gateway(v2) with OPCUA data source and status shows as In-Sync. But I didn't see the Latest data in data streams or assets-measurements area.

Observation:

  1. I deleted all gateways, core device and deployed newly then also same issue.
  2. Error: component SiteWiseEdgeCollectorOpcua is logging this error when it starts: aws.iot.SiteWiseEdgeCollectorOpcua: stdout. [WARN ] 2024-01-17 09:10:33.290 [Thread-3] OpcUaManagedConnection - {"message":"Failed to start OPC-UA Connection for Source (EC2Kepware-Public): Failed to discover endpoint for OPC-UA server opc.tcp://<hostip>:49320. [ I tested with both Public & private IP ]

Question:

  1. whether following trust certificate step need to complete on OPC server end? If yes, I need your help because I cannot find any files in my EC2 instance folders to export https://docs.aws.amazon.com/iot-sitewise/latest/userguide/enable-source-trust.html
  2. Which IP (Public / private) to be use in Opc-UA server configuration in Sitewise Data source
  3. Any other steps or guidance for successful completion.

Let me know in case I need to provide more information. Thank you very much in advance for your support!

Pawan
gefragt vor 4 Monaten161 Aufrufe
1 Antwort
1
Akzeptierte Antwort

Hi Pawan. It seems to me that the error message you're reporting is not so likely if the status is "In sync". Maybe that error didn't occur at the same time as "In sync".

Is your Kepware OPC server in the same VPC and subnet as the SiteWise gateway? Perhaps you can tell us a little about your network architecture.

  1. I think Kepware OPC requires it, but you need to determine that. As for where to find the cert on the gateway, please retrace your steps. Have you found the sitewise-COLLECTOR-config.json file? If not, perhaps try sudo find / -name sitewise-COLLECTOR-config.json.
  2. It will depend on your network architecture.

By the way, you said in one of your other questions that you're following this blog: https://aws.amazon.com/blogs/iot/collecting-organizing-monitoring-and-analyzing-industrial-data-at-scale-using-aws-iot-sitewise-part-1/. Please be aware that that blog is more than 4 years old and was written for Greengrass V1.

The SiteWise workshop might also be a valuable reference: https://catalog.us-east-1.prod.workshops.aws/workshops/2de8cd26-ae40-4b09-ad19-7b1eff358f5f/en-US/30-aws-iot-sitewise-setup/create-sitewise-gateway

profile pictureAWS
EXPERTE
Greg_B
beantwortet vor 4 Monaten
profile picture
EXPERTE
überprüft vor 2 Monaten
  • Thank you Greg. I found the issue on Network end and rectified..

  • Thank you Greg. I found the issue on Network end and rectified..

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen