Hello Yong,
Thanks a lot for your reply with the information.
We are using the 3.14.12.4 for the CA gateways.
For the information, we were running virtualized CA gateways and yesterday we have built an additional CA gateway on another physical machine without virtualization for comparison of virtualized
and physical CA gateways.
As the result, we observed that the message is often being occurred on a virtualized CA gateway but no such message on the physical machine based CA gateway.
In our case for the moment it seems the message is related with performance of system such as network traffic processing.
Thanks again.
Regards,
Sangwon
Hi Sangwon,
Take a look at this:
https://bugs.launchpad.net/epics-base/+bug/541238
At the end, Andrew said “Probably fixed in later versions of Base ….”, “R3.14.10 released”.
Which version of Base is your CA gateway built against?
Best,
Yong
Hello,
We are running several CA gateways for providing access to PVs for clients including OPIs.
I observed the warning message “Virtual circuit unresponsive”
on log files of the CA gateways.
For instance,
Aug 28 15:29:19 Warning: Virtual circuit unresponsive 172.17.101.21:5064
Aug 28 15:53:40 Warning: Virtual circuit unresponsive 172.17.101.80:5064
…
In addition, when the message is logged on a log file, connections to PVs of the IOC server related with the message (ex. 172.17.101.21) are disconnected.
At the time, connection to the same PVs which directly connects to the IOC server instead of CA gateway is still continued and client (camonitor) can receive changes from the IOC without disturbance.
For the information, we are running two versions of CA gateways, v2.0.4.0 and v2.1.0.
Could anyone please share any guidance or comments in the case?
Thanks in advance for your guidance or any comments.
Regards,
Sangwon