[Openswan Users] pluto aborted
nw at sbs.de
Wed Feb 9 09:18:20 CET 2005
The crash happens, with a client running openswan-2.3.0-1suse9x from the
openswan site and the server running the 2.2.0 version delivered
originally with Suse9.2.
Here is what I see:
(gdb) attach 21503
Attaching to process 21503
Reading symbols from /usr/lib/ipsec/pluto...(no debugging symbols
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Reading symbols from /usr/lib/libgmp.so.3...(no debugging symbols
Loaded symbols for /usr/lib/libgmp.so.3
Reading symbols from /lib/libresolv.so.2...(no debugging symbols
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
Loaded symbols for /lib/ld-linux.so.2
0xffffe410 in ?? ()
Program received signal SIGABRT, Aborted.
0xffffe410 in ?? ()
#0 0xffffe410 in ?? ()
#1 0xbffeddf8 in ?? ()
#2 0x00000006 in ?? ()
#3 0x000053ff in ?? ()
#4 0x40087d41 in raise () from /lib/tls/libc.so.6
#5 0x40089529 in abort () from /lib/tls/libc.so.6
#6 0x080553ee in passert_fail ()
#7 0x0806ab38 in setup_half_ipsec_sa ()
#8 0x0806b6d1 in install_inbound_ipsec_sa ()
#9 0x08063edb in quick_inI1_outR1_tail ()
#10 0x08064c40 in quick_inI1_outR1 ()
#11 0x08073699 in comm_handle ()
#12 0x0805a200 in call_server ()
#13 0x08058aea in main ()
Hope this helps.
Paul Wouters schrieb:
> On Tue, 8 Feb 2005, Norbert Wegener wrote:
>> Feb 8 15:00:08 lnxtst ipsec__plutorun: /usr/lib/ipsec/_plutorun:
>> line 215: 2124 Aborted /usr/lib/ipsec/pluto
>> --nofork--secretsfile /etc/ipsec.secrets --ipsecdir /etc/ipsec.d
>> --debug-parsing --debug-control
> Can you add dumpdir=/tmp to config setup and show us a gdb backtrace
> of the core?
>> l2tp-winxp with a windowsXP client works without problems, linux
>> clients with the connection l2tp-linuxnat cause the failure.
> I think this might have been fixed. But we also seem to have a problem
> in 2.3.0
> when the windows end has no valid certificate that we no longer handle
> for some reason.
More information about the Users