On Mon, 11 Jul 2016, Li, Mike wrote:
I experienced a situation where Libreswan (libreswan-3.15-5.3.el6.x86_64) and with
libreswan-3.17-1.el6.x86_64 which went into a "stuck" or failed? state on
2.6.32-573.18.1.el6.x86_64 RHEL6
root 60394 1 0 Jul02 ? 00:00:00 /bin/sh
/usr/libexec/ipsec/_plutorun --config /etc/ipsec.conf --nofork
root 60401 60394 96 Jul02 ? 1-08:47:08 /usr/libexec/ipsec/pluto
--config /etc/ipsec.conf --nofork
root 103393 102552 0 03:48 ? 00:00:00 /bin/sh /etc/init.d/ipsec
status
root 103405 103393 0 03:48 ? 00:00:00 /usr/libexec/ipsec/whack
--status
root 104658 100948 0 13:44 pts/0 00:00:00 sudo /usr/sbin/ipsec auto
status
root 104661 104658 0 13:44 pts/0 00:00:00 /bin/sh
/usr/libexec/ipsec/auto status
root 104662 104661 0 13:44 pts/0 00:00:00 /usr/libexec/ipsec/whack
--status
root 131679 1 0 Jul08 ? 00:00:00 /bin/sh
/usr/libexec/ipsec/_plutorun --config /etc/ipsec.conf --nofork
root 131686 131679 68 Jul08 ? 2-07:23:51 /usr/libexec/ipsec/pluto
--config /etc/ipsec.conf --nofork
I could not stop it using
time sudo /etc/init.d/ipsec stop
Shutting down pluto IKE daemon
^C
real 5m52.619s
user 0m0.014s
sys 0m0.014s
(stuck for more than 5 minutes)
And I could not get result for /etc/init.d/ipsec status because the command
also got stuck.
Could I issue a kill command with any option to capture some debug information?
You could use strace -v -f `pidof pluto` so we have an idea of where it
seems stuck.
Paul
_______________________________________________
Swan mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan
