Re: Virtual Circuit Disconnect Warning

[Deepika Thakur <epics2117@gmail.com>]

Hello,

IOC behaves normally when I do caget. Data from device support  gets printed when I run IOC. Just when I do caget to read OPTO card data it gives zero value as shown below.Also GUI I have prepared in CSS BOY also show disconnected PVs 

[srk@srk iocmyExample]$ caget wafData
wafData 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

When I do caget to read ADC card data I get VIRTUAL CIRCUIT DISCONNECT warning as described in previous post.

There are as such no other symptoms apart from this

On Mon, Aug 31, 2015 at 8:38 AM, Andrew Johnson <anj@aps.anl.gov> wrote:

Hi,

On 08/31/2015 01:08 AM, Deepika Thakur wrote:
> The server is an IOC.
>  When I run IOC , sometimes it gives warning as
>
>
> cas warning: Configured TCP port was unavailable.
> cas warning: Using dynamically assigned TCP port 54834,
> cas warning: but now two or more servers share the same UDP port.
> cas warning: Depending on your IP kernel this server may not be
> cas warning: reachable with UDP unicast (a host's IP in EPICS_CA_ADDR_LIST)

You can ignore that warning as long as your CA clients are all on the
same IP subnet as the server. If you have problems with them connecting
to the IOC, you should read this Wiki page:

https://wiki-ext.aps.anl.gov/epics/index.php/How_to_Make_Channel_Access_Reach_Multiple_Soft_IOCs_on_a_Linux_Host

However the problem you described before is completely unrelated to the
above warning.

Does the IOC continue running and otherwise behave normally when you do
the caget? I suspect there are other symptoms which you have not yet
described.

- Andrew


> On Fri, Aug 28, 2015 at 8:18 AM, Andrew Johnson <anj@aps.anl.gov

> <mailto:anj@aps.anl.gov>> wrote:
>
>     Hi,
>
>     On 08/27/2015 11:31 PM, Deepika Thakur wrote:
>     > Please guide how to resolve this following "VIrtual Circuit Disconnect "
>     > warning :
>     >
>     >
>     > [srk@srk iocmyExample]$ caget ADC_CARD:CHANNEL1-16:ADCData
>     > Read operation timed out: some PV data was not read.
>     > ADC_CARD:CHANNEL1-16:ADCData 72 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>     > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>     > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>     > CA.Client.Exception...............................................
>     >     Warning: "Virtual circuit disconnect"
>     >     Context: "op=0, channel=ADC_CARD:CHANNEL1-16:ADCData,
>     > type=DBR_TIME_CHAR, count=72, ctx="localhost:5064""
>     >     Source File: ../getCopy.cpp line 92
>     >     Current Time: Fri Aug 28 2015 09:52:41.966386036
>     > ..................................................................
>
>     That message usually means that the IOC or CA server died before the
>     client could disconnect from it properly; it is very unusual for caget
>     to show this message, but should be benign. Is the server an IOC, or
>     something based on libcas?
>
>     - Andrew

--
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has
always got there first, and is waiting for it.
    -- Terry Pratchett, Reaper Man