After several days of running continuously, the rapidSCADA session is denied

[grhsc]

Dear developer, I have encountered a strange problem

It might not be a problem with rapidSCADA, I’d like to hear your analysis.

The rapidSCADA project is connected with 4 different opc ua servers (same manufacturer, through the Internet) these 4 OPC UA servers provide data to other applications besides rapidscada

After 4-5 days, the 4 OPC UA servers will show that the CurrenSession exceeds the maximum one after another, and close the connection of rapidscada (but the connection of other applications will still be retained). It can be seen intuitively on the View that these data have stopped updating.

This problem is very troublesome, from V5.84 to V6, it has been like this, currently only to restart opc ua But it still keep only lasts a few days.

Whether this phenomenon can be avoided by setting, has anyone reported similar problems before?

[Mikhail]

Hello,
The issue happened the 1st time.
Do the OPC servers show active connections? How many connections in total?
What does Rapid SCADA 6 do if an OPC connection is closed by OPC server?

[grhsc]

Do the OPC servers show active connections? How many connections in total?

– At this time, I can no longer use the client software to know its CurrenSession.
That is to say, the server rejects all new sessions, but it is strange that the original rapidSCADA will also be rejected. But other existing sessions are still maintained.
Looking at the 1 minute archived data before it was rejected, the number of sessions was less than 5 (10 is the server maximum sessions ) I did not see the CurrenSession > 5 in the archived data, I can only guess that it was at 1 Minutes are rapidly greater than 10 and no records are archived because 1 minute intervals.

What does Rapid SCADA 6 do if an OPC connection is closed by OPC server?
– When the rapidSCADA session is terminated, the data cannot be updated, this is the wrong log

2023-01-13 18:17:37 Delay before connecting 4.6 sec
2023-01-13 18:17:42 Connect to opc.tcp://192.168.204.100:49320
2023-01-13 18:17:42 Error connecting OPC server:
System.AggregateException: One or more errors occurred. (BadSecureChannelClosed)
—> Opc.Ua.ServiceResultException: BadSecureChannelClosed
at Opc.Ua.Bindings.ChannelAsyncOperation`1.End(Int32 timeout, Boolean throwOnError)
at Opc.Ua.Bindings.UaSCUaBinaryClientChannel.EndSendRequest(IAsyncResult result)
at Opc.Ua.DiscoveryClient.GetEndpoints(RequestHeader requestHeader, String endpointUrl, StringCollection localeIds, StringCollection profileUris, EndpointDescriptionCollection& endpoints)
at Opc.Ua.DiscoveryClient.GetEndpoints(StringCollection profileUris)
at Scada.Comm.Drivers.DrvOpcUa.OpcClientHelperBase.SelectEndpoint()
at Scada.Comm.Drivers.DrvOpcUa.OpcClientHelperBase.ConnectAsync()
— End of inner exception stack trace —
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Scada.Comm.Drivers.DrvOpcUa.Logic.OpcClientHelper.Connect()

[grhsc]

This is a low-speed (10 Sec) updated ua server, Could modifying some RapidSCADA comm parameters help reduce the chances of it being rejected?

[Mikhail]

When the rapidSCADA session is terminated, the data cannot be updated

It tries to reconnect, but cannot.

Could modifying some RapidSCADA comm parameters help reduce the chances of it being rejected?

I suppose, disconnect is initiated by the OPC server. You should ask the OPC server developers why it closes connections.

[Author]

Posts