more quick actions
minimize quick actions
Topic starter
Hello,
Received contact from customer regarding subscription timeout.
In the attached Trace.txt, the log that happened in 2022/08/02, 23:53:46.
What I want to ask is, under what circumstances (or possibly some improper operation), this kind of log will appear.
The structure can refer to the attachment STATION.txt
Posted : 23/08/2022 2:42 pm
Hi Liyang,
Let's take in example the variable OperationRoot.Position.Obi.Obi28.Knkks.CoChi1_NoboriIriguchi.TmReg
What station is producing it?
Nico
Posted : 23/08/2022 8:39 pm
Topic starter
Hello，Nico.
The following stations operate as master servers. and provide all variables·
STATIONNG,DATASERVER0,卓サーバ#0,0,1,100,0,0,0,0,0,-2,1,0,0,
NODEIP,DATASERVER00,DATASERVER0,卓サーバ#0,0,1,10.26.53.70,1,,1981,1,2,30,10,60,30,100
In addition, customers use the VarexpSave.dat file to automatically save variables (this file is often used Redundancy?)
Is this problem related to the VarexpSave.dat file?
Posted : 24/08/2022 12:21 pm
I think the problem you have is the regular disconnection of the DATASERVER0
Search in the trace.log the string WSAECONNRESET
Nico
Posted : 24/08/2022 3:03 pm