Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection Timeout #10

Open
srjhunjhunwalacorp opened this issue Jun 5, 2024 · 4 comments
Open

Connection Timeout #10

srjhunjhunwalacorp opened this issue Jun 5, 2024 · 4 comments
Assignees
Labels
question Further information is requested

Comments

@srjhunjhunwalacorp
Copy link

Hello Team,

While using the commander I am getting timeouts, when checked connectivity to OPC UA server seems fine, it sometimes connects fine sometime its shows this random behaviour also with historical and write commands, can you please suggest -

Screenshot 2024-06-05 at 3 22 25 PM
Screenshot 2024-06-05 at 3 20 25 PM

@srjhunjhunwalacorp
Copy link
Author

I am receiving following logs while starting the container -

[09:58:02 INF] Log file is: /app/uacloudcommander.logfile.txt
Could not load cert file, creating a new one. This means the new cert needs to be trusted by all OPC UA servers we connect to!
Could not load key file, creating a new one. This means the new cert generated from the key needs to be trusted by all OPC UA servers we connect to!
[09:58:03 INF] Connected to MQTT broker.
[09:58:03 INF] UA Cloud Commander is running.

@barnstee barnstee self-assigned this Jun 12, 2024
@barnstee barnstee added the question Further information is requested label Jun 12, 2024
@barnstee
Copy link
Member

@srjhunjhunwalacorp , the cert file error is because you are not mapping the PKI directory of the UA Cloud Commander to the Docker host filesystem during Container startup (-v flag in docker). Therefore UA Cloud Commander can't load an existing cert and creates a new one. It seems like you are not using security in your OPC UA server, so this should not be your issue (although not using security is of course an issue!)

It looks like you are using IoT Hub with UA Cloud Commander. Sometimes IoT Hub simply throttles you and you will get timeouts. I would recommend using an Event Hub instead.

@srjhunjhunwalacorp
Copy link
Author

Yes I am using IoT hub but at the same time I can see that the request is received on the UA cloud commander but it is not initiating a connection towards the OPC UA server as I cant see the connection request on the server side. Earlier it was working fine in the same way but after the new release it started giving timeout issue.

Also I checked the throttling metrics but could not find it happening on the IoT hub.

image

@barnstee
Copy link
Member

Make sure the clock is set correctly in your Docker host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants