[strongSwan] Multiple Starting IKE charon daemons in log file...

[Dan Cook]

We have a server that under heavy load on reboot shows this in the charon
log.

2014-07-24T10:42:01-0700 00[DMN] signal of type SIGINT received. Shutting
down
2014-07-24T10:47:16-0700 00[DMN] Starting IKE charon daemon (strongSwan
5.1.3, Linux 3.2.0-67-generic, x86_64)
2014-07-24T10:47:31-0700 00[DMN] Starting IKE charon daemon (strongSwan
5.1.3, Linux 3.2.0-67-generic, x86_64)

When this happens all sorts of bad things crop up.  We are listening on the
error up down socket and the peer closes socket and can never reconnect.

<From our logs...>
2014-07-24T10:47:56-07:00 INFO:: IPSec socket closed by peer.
2014-07-24T10:48:02-07:00 INFO:: Entering inner IPSec while loop.
2014-07-24T10:48:11-07:00 INFO:: IPSec socket closed by peer.
2014-07-24T10:48:17-07:00 INFO:: Entering inner IPSec while loop.
2014-07-24T10:48:26-07:00 INFO:: IPSec socket closed by peer.
2014-07-24T10:48:32-07:00 INFO:: Entering inner IPSec while loop.
2014-07-24T10:48:41-07:00 INFO:: IPSec socket closed by peer.

However Charon never comes up afterwards - only the starter is present on
the system.

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strongswan.org/pipermail/users/attachments/20140728/803b5144/attachment.html>