RE: Tunnel collapses with "Bad file descriptor"|
Fri, 16 Apr 2004 15:26:27 -0700|
Unfortunately this will not work in my case, since the tunnel is constantly
used by other processes, not just by users that are able to call the script.
For example servlets connecting to databases, etc., that are not able to
first call the script in case the tunnel is down.
But thanks anyway.
From: James Knott [mailto:james.knott,AT,rogers,DOT,com
Sent: Friday, April 16, 2004 3:01 PM
Subject: Re: Tunnel collapses with "Bad file descriptor"
> I have a cipe (v.1.4.5) tunnel running between a Redhat9 and a Fedora
> core 1 machine. The tunnel gets established successfully and works
> fine until at some point - sometimes after a few hours, sometimes
> after a few days - it collapses with this error message:
> Apr 14 19:22:50 lvd1 ciped-cb: kxchg: read(r): Bad file descriptor
> Apr 14 19:22:50 lvd1 ciped-cb: Interface stats 22552096 201358 4
> 0 0 1 0 0 0
> 0 0 0 0 0 0 0
> Apr 14 19:22:50 lvd1 ciped-cb: KX stats: rreq=0, req=335,
> ind=336, indb=0, ack=328, ackb=0, unknown=0 Apr 14 19:22:50 lvd1
> cipcb1: daemon exiting
> Any idea where this might come from?
> The machines are sitting locally within a LAN - it's just a test setup
> for now...
I have noticed the same thing here. I wrote a short script, so that I
could use ssh from my notebook, to restart CIPE, when I'm away from home
and find I can't connect my VPN.