[Openswan dev] no available worker thread an issue in Feb 2nd drop

[Paul Wouters]

On Mon, 13 Feb 2012, Steve Lanser wrote:

> Looks like I'm getting segfaults over this in the 2nd case:
>
> Feb 13 15:19:18 tb7 pluto[17495]: "10.3.0.121-to-10.3.0.113" #12: STATE_PARENT_R2: received v2I2, PARENT SA established transport mode {ESP=>0x7dc0a36f <0xe4c06d7f xfrm=3DES_192-HMAC_SHA1 NATOA=none NATD=none DPD=none}
> Feb 13 15:19:28 tb7 pluto[17495]: "10.3.0.121-to-10.3.0.113" #13: transition from state STATE_IKEv2_START to state STATE_PARENT_R1
> Feb 13 15:19:28 tb7 pluto[17495]: "10.3.0.121-to-10.3.0.113" #13: STATE_PARENT_R1: received v2I1, sent v2R1 {auth=IKEv2 cipher=oakley_3des_cbc_192 integ=sha1_96 prf=oakley_sha group=modp1024}
> Feb 13 15:19:28 tb7 pluto[17495]: "10.3.0.121-to-10.3.0.113" #16: can not start crypto helper: failed to find any available worker
> Feb 13 15:19:28 tb7 pluto[17495]: "10.3.0.121-to-10.3.0.113" #16: system too busy

That's odd. This is not some embedded low power cpu device?

> Feb 13 15:19:28 tb7 kernel: pluto[17495]: segfault at 0000000000000030 rip 0000000000432b08 rsp 00007fffed9c4fb0 error 6

set dumpdir= and get a "bt full" using gdb on the core to give us more
information please. Use a new bug since the bug you referenced that
we closed was for openswan 2.4.x.

Paul