RE: partial (damaged?) UDP msg

["Williams Jr., Ernest L." <ernesto@slac.stanford.edu>]

Hi,

Please provide more information:
Such as what version of EPICS are you running for your CA server and clients?


Cheers,
Ernest
________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Zhang Yuliang [zhangyl@ihep.ac.cn]
Sent: Saturday, April 15, 2017 4:27 AM
To: tech-talk
Subject: CAS: partial (damaged?) UDP msg

Hi all,

I found that one soft ioc output the following information:

epics> CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: request from 10.1.204.140:54439 => CAS: Missaligned protocol rejected
CAS: Request from 10.1.204.140:54439 => cmmd=0 cid=0x4143435f type=0 count=3100 postsize=3100
CAS: Request from 10.1.204.140:54439 =>   available=0x4c524254  N=3 paddr=(nil)
CAS: invalid (damaged?) UDP request from 10.1.204.140:54439 ?
CAS: request from 10.1.204.140:54439 => CAS: Missaligned protocol rejected
CAS: Request from 10.1.204.140:54439 => cmmd=0 cid=0x4143435f type=0 count=3100 postsize=3100
CAS: Request from 10.1.204.140:54439 =>   available=0x4c524254  N=3 paddr=(nil)
CAS: invalid (damaged?) UDP request from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?
CAS: partial (damaged?) UDP msg of 8 bytes from 10.1.204.140:54439 ?

At that time, all of our Labview and C# type CA servers hung up(the standard iocs were all ok), no response to the ca search from clients. After we reboot the ca servers, it return to OK.
It is the first time we saw this and I think the ca server hung up event has relation to the invalid request.

Regards,
Zhang Yuliang