> The question is: what does the CA server do
> after it outputs these error messages?
It discards the rest of the UDP datagram and waits for another UDP datagram to arrive. It's interesting that the count is 5064. It's even possible that the UDP header is being processed as CA protocol presumably due to some issues in the IP kernel.
> Could it be it does something to the socket that
> makes vxWorks throw up hands and strike?
nothing that I know of
> Also, note the 10 second delay between the CAS
> message and the vxWorks message.
>
> Is this a known bug in VxWorks? In the CAS?
My best guess is vxWorks. Make certain that all of the LAN interface driver patches are installed. I have definitely seen issues in the past with the vxWorks IP kernel getting wedged, attempting a reset, and then being unable to recover.
I have seen the damaged UDP messages in the past when the 10/100 auto negotiation fails. That used to happen here sometimes when the switch was powered up after the IOC.
Jeff
_______________________________________________________
Jeffrey O. Hill Email [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
Message content: TSPA
> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Benjamin Franksen
> Sent: Wednesday, June 23, 2010 7:20 AM
> To: [email protected]
> Subject: strange ioc hangup
>
> >From the console log:
>
> CAS: request from 192.168.21.6:46187 => "CAS: Missaligned protocol
> rejected"
> [Sun Jun 20 05:23:20 2010]CAS: Request from 192.168.21.6:46187 =>
> cmmd=49320
> cid=0x91f87157 type=48940 count=5064 postsize=5587
> [Sun Jun 20 05:23:20 2010]CAS: Request from 192.168.21.6:46187 =>
> available=0xcb45c46e N=1 paddr=0x0
> [Sun Jun 20 05:23:20 2010]CAS: invalid (damaged?) UDP request from
> 192.168.21.6:46187 ?
> [Sun Jun 20 05:23:30 2010]interrupt:
> [Sun Jun 20 05:23:30 2010]ei0: reset
>
> This is base 3.14.8.2 and VxWorks 5.4.2. Looks like one or more corrupt
> UDP
> packages arrived at the IOC. The problem is that after the last message
> ("ei0: reset") the IOC is dead to the network (neither transmits nor
> receives anything). No way to recover, other than rebooting.
>
> The question is: what does the CA server do after it outputs these error
> messages? Could it be it does something to the socket that makes vxWorks
> throw up hands and strike? Also, note the 10 second delay between the CAS
> message and the vxWorks message.
>
> Is this a known bug in VxWorks? In the CAS?
>
> Cheers
> Ben
- References:
- strange ioc hangup Benjamin Franksen
- Navigate by Date:
- Prev:
Re: strange ioc hangup Andrew Johnson
- Next:
Re: strange ioc hangup rolf keitel
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: strange ioc hangup Benjamin Franksen
- Next:
Re: strange ioc hangup rolf keitel
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|