[Openswan Users] ipsec__plutorun: !pluto failure!: exited with error status 134 (signal 6)

Paul Wouters paul at xelerance.com
Mon Oct 3 13:10:55 EDT 2011

On Mon, 3 Oct 2011, Chen, Xuli (James) wrote:

> I'm experiencing below pluto failure with openswan-2.6.21-5.el5_5.3 when I was trying to stop ipsec during traffic.
> According to searching result from Google, it looks this kind of issue happened before with older openswan release.
> But I could not understand what's the root cause and solution for that. Anyone knows the root cause and solution?

2.6.21 is very old. You should upgrade...

> /usr/libexec/ipsec/pluto --nofork --secretsfile /etc/ipsec.secrets --ipsecdir /etc/ipsec.d --use-netkey
> --crlcheckinterval 600 --nhelpers 0
> Sep 28 09:18:09 tb1ems1 ipsec__plutorun: !pluto failure!:  exited with error status 134 (signal 6)

These logs are only the /var/log/messages entries. There is also a "secure" or "daemon" or "auth.log"
that captures logging from the pluto binary.

If you have an ASSERTION FAILED in your /var/log/auth.log log, then we can probably tell you
when and where it was fixed (if it is not a new issue). If it just crashes without a message,
we would need to see a gdb trace before knowing more.

but you can also go through ftp://ftp.openswan.org/openswan/CHANGES to get an idea about whether
or not we fixed it.


More information about the Users mailing list