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

Question: Subscription / Monitoring - Connection Drop #2092

Open
track02 opened this issue Oct 3, 2018 · 4 comments

Comments

@track02
Copy link

commented Oct 3, 2018

I'm currently running a FreeOpcUa server on a Raspberry Pi and connecting to it with a Qt Android Application (QtOpcUa + Open62541 Backend)

I seem to have some trouble monitoring nodes for value changes as the connection will just drop out after around 10 minutes of starting the monitoring.

I'm having a hard time debugging this and was just wondering if this is something you've came across before or would have any better ideas on how to diagnose.

I enabled logging on my server and can see an entry closing the connection to the client and cleaning up. Looking at the output the application provides only shows the following from open62541:

qt.opcua.plugins.open62541: Unable to send publish request

I've tried Wireshark but can't seem to spot anything as the packets stop when the connection drops, this may just be my inexperience using it so please point me in the right direction if possible.

I have also tried changing the log level when building open62541 but don't see anything new (again this may be an error on my behalf).

Any thoughts or ideas would be greatly appreciated.

Many thanks.

Edit: Tested this a little more today, and it seems after ~10 minutes of being connected any interaction with the server will cause the connection to drop not just subscriptions (E.g. Subscribe to a node, read a node, etc)

@ChHaa

This comment has been minimized.

Copy link

commented Oct 5, 2018

Did you change the def. values for session lifetime ?

@track02

This comment has been minimized.

Copy link
Author

commented Oct 5, 2018

Thank you for the suggestion; I was able to find a default lifetime variable on the server but changing it didn't seem to affect anything and it was already very high.

I'm wondering if it's just a mismatched setting somewhere, trying QtOpcUa/Open62541 with other servers doesn't have the same issue and trying different clients with the server is also fine.

I'll have another look into the default values and settings over the weekend.

@jpfr

This comment has been minimized.

Copy link
Member

commented Oct 22, 2018

Hello @track02 ,

do you have log messages that were generated when the disconnect happened?

@track02

This comment has been minimized.

Copy link
Author

commented Oct 22, 2018

Hi,

Unfortunately don't have them to hand but can try and recreate the drop-out tomorrow if you'd like.
From memory the client would log a warning from Open62541 like this:

Open62541: Unable to Send Publish Request

And the server would just log a client disconnection and cleanup of the session.

I've tried using a Node.js server instead and have no issues but I have noticed logs about security tokens changing with a timeout of 600000ms (10 min) so I wonder if there's something similar going on with the Python FreeOpcUa server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.