Message: "Received chunk with wrong sequence, spec says to close connection #1323
Replies: 4 comments
-
Having the same issue with an Advantech module |
Beta Was this translation helpful? Give feedback.
-
Found a solution.
|
Beta Was this translation helpful? Give feedback.
-
somehow there are messages missing see sequencenumbers.... looks like networkissue on the first look! |
Beta Was this translation helpful? Give feedback.
-
The systems are in the same subnet; the connection works from the PC with other software AND I have a previous version of my solution which already uses Actual reason: the OPC UA server gets hung up from time-to-time - somewhat stupid/basic device. |
Beta Was this translation helpful? Give feedback.
-
I am using a freeopcua python script (v 0.98.10) to read data from an OPCUA server. The script runs fine for hours and days, but then often stops with a message similar to this one:
opcua.ua.uaerrors._base.UaError: Received chunk: MessageChunk(Header(type:b'MSG', chunk_type:b'F', body_size:100, channel:3876308278), SequenceHeader(SequenceNumber:255538, RequestId:255489 ), SymmetricAlgorithmHeader(TokenId:104 ), 50 bytes) with wrong sequence expecting: 255536, received: 255538, spec says to close connection Protocol Error
What could the reason for this error? Is it connected to network problems (latency)? My colleagues tell me that the server is not showing problems.
How would I catch the corresponding exception in Python? My usual approach is to wait 60 seconds (in case the server got rebooted) and reinitialize the connection, but with this error, my script just hangs (a KeyboardInterrupt is however caught, so I can do 'Ctrl-C' whenever I notice that the script is hanging, and it will reestablish the connection).
Any ideas will be appreciated, I can also provide more information if needed.
Upfate: It happened again - here is the error message and traceback:
Beta Was this translation helpful? Give feedback.
All reactions