[Openswan Users] stuck at STATE_QUICK_I1
Pierre de France
pierre.defrance at lattitudeweb.com
Tue Sep 13 18:24:34 CEST 2005
THANKS !!!
I was totally stuck with that issue !
There were two files (among others) in my /usr/local/lib/ipsec/ :
_updown and _updown.old.
I simply replaced _updown by _updown.old and everything went just fine !
Thanks very much for your help !
Pierre.
> -----Message d'origine-----
> De : Andy [mailto:fs at globalnetit.com]
> Envoyé : mardi 13 septembre 2005 17:07
> À : Pierre de France
> Cc : users at openswan.org
> Objet : Re: [Openswan Users] stuck at STATE_QUICK_I1
>
> On Tue, 2005-09-13 at 15:51 +0200, Pierre de France wrote:
>
> > 117 "synagir1" #2: STATE_QUICK_I1: initiate
> > 003 "synagir1" #2: up-host command exited with status 139
> > 032 "synagir1" #2: STATE_QUICK_I1: internal error
> >
>
> This indicates a problem in the updown script, I think.
> That's /usr/local/lib/ipsec/_updown or wherever your distribution puts
> it.
>
> 139 is a segfault, IIRC. Maybe some inconsistent versions of some
> libraries and utilities. I had a similar problem once when I updated
> something with an RPM which didn't do enough dependency checking.
>
> You could try making a copy of the default script and pointing to the
> copy with a left/rightupdown= entry. Add something like this to the
top
> of the copy (right after the '#! /bin/sh' line) so you can see a trace
> of what it's up to:
>
> exec >/tmp/updown.$$ 2>&1
> set -x
>
>
More information about the Users
mailing list