[Openswan Users] Openswan Error

[Daniel Sung]

Hello,

Please advice if anyone has comments about below.

B.Rgds

Daniel Sung
Information Technology - Shipco Transport

Tel : +852 2574 3188 (General Lines)
Tel : +852 2574 7274 (Direct Line)
Fax : +852 2573 3936
e-mail : dsung at shipco.com

For access to STI-Online which offers on-line schedules, bookings,
documentation, shipment tracking and other e-commerce tools, please visit
our website, www.shipco.com



-------- Original Message  --------
Subject: Openswan Error
From: Daniel Sung <dsung at shipco.com>
To: users at openswan.org
Date: Fri Nov 17 2006 16:46:45 GMT+0800 (China Standard Time)
> Hi,
>
> I have my openswan 2.2.8 on Debian 3.1, few days ago the 'syslog' keep 
> generate the error message like below and the openswan is up and down 
> all the time, is it my configration problem or a bug in this version? 
> We have few firewall like this and all generate the same error.  
> Kindly please advice if any idea.
>
> QUOTE
> Nov 16 06:43:44 firewall ipsec__plutorun: !pluto failure!:  exited 
> with error status 139 (signal 11)
> Nov 16 06:43:44 firewall ipsec__plutorun: restarting IPsec after pause...
> Nov 16 06:43:54 firewall ipsec_setup: ...Openswan IPsec stopped
> Nov 16 06:43:54 firewall ipsec_setup: Stopping Openswan IPsec...
> Nov 16 06:43:54 firewall ipsec_setup: Removing orphaned 
> /var/run/pluto.pid:
> Nov 16 06:43:55 firewall ipsec_setup: KLIPS ipsec0 on eth0 
> 80.16.194.54/255.255.255.0 broadcast 80.1
> 6.194.255
> Nov 16 06:43:55 firewall ipsec_setup: ...Openswan IPsec started
> Nov 16 06:43:55 firewall ipsec_setup: Restarting Openswan IPsec 
> U2.2.0/K2.4.27-3-686...
> Nov 16 06:44:01 firewall ipsec__plutorun: 104 "cph-hkg" #1: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:01 firewall ipsec__plutorun: ...could not start conn 
> "cph-hkg"
> Nov 16 06:44:02 firewall ipsec__plutorun: 104 "cph-tll" #2: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:02 firewall ipsec__plutorun: ...could not start conn 
> "cph-tll"
> Nov 16 06:44:03 firewall ipsec__plutorun: 104 "cphit-cph" #3: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:03 firewall ipsec__plutorun: ...could not start conn 
> "cphit-cph"
> Nov 16 06:44:04 firewall ipsec__plutorun: 104 "got-cph" #4: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:04 firewall ipsec__plutorun: ...could not start conn 
> "got-cph"
> Nov 16 06:44:05 firewall ipsec__plutorun: 104 "hob-cph" #6: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:05 firewall ipsec__plutorun: ...could not start conn 
> "hob-cph"
> Nov 16 06:44:06 firewall ipsec__plutorun: 104 "lon-cph" #9: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:06 firewall ipsec__plutorun: ...could not start conn 
> "lon-cph"
> Nov 16 06:44:07 firewall ipsec__plutorun: 104 "cph-hel" #10: 
> STATE_MAIN_I1: initiate
> Nov 16 06:44:07 firewall ipsec__plutorun: ...could not start conn 
> "cph-hel"
> Nov 16 06:44:53 firewall ipsec__plutorun: /usr/lib/ipsec/_plutorun: 
> line 1: 13625 Segmentation fault
>     /usr/lib/ipsec/pluto --nofork --secretsfile /etc/ipsec.secrets 
> --ipsecdir /etc/ipsec.d --debug-
> all --uniqueids
> Nov 16 06:44:53 firewall ipsec__plutorun: !pluto failure!:  exited 
> with error status 139 (signal 11)
> Nov 16 06:44:53 firewall ipsec__plutorun: restarting IPsec after pause...
> Nov 16 06:45:03 firewall ipsec_setup: ...Openswan IPsec stopped
> Nov 16 06:45:03 firewall ipsec_setup: Stopping Openswan IPsec...
> Nov 16 06:45:03 firewall ipsec_setup: Removing orphaned 
> /var/run/pluto.pid:
> UNQUOTE
>
> P.S. : Couple days ago, we changed to use SSH protocol to connect 
> other servers over the tunnel.  Is that a reason cause the error?
>