[strongSwan] strongswan 5.8.3 core dump

Marco Berizzi pupilla at hotmail.com
Wed Mar 25 19:07:59 CET 2020


Hello Tobias,

Here is the charon.log: I hope it will be useful for you.

[CFG] <apsil-10.221.128.183|25> found matching child config "apsil-10.221.128.183" with prio 6
[CFG] <apsil-10.221.128.183|25> selecting traffic selectors for other:
[CFG] <apsil-10.221.128.183|25>  config: 10.221.128.183/32, received: 10.221.0.0/16 => match: 10.221.128.183/32
[CFG] <apsil-10.221.128.183|25> selecting traffic selectors for us:
[CFG] <apsil-10.221.128.183|25>  config: 10.240.123.0/26, received: 10.240.123.0/26 => match: 10.240.123.0/26
[CFG] <apsil-10.221.128.183|25> selecting proposal:
[CFG] <apsil-10.221.128.183|25>   no acceptable DIFFIE_HELLMAN_GROUP found
[CFG] <apsil-10.221.128.183|25> selecting proposal:
[CFG] <apsil-10.221.128.183|25>   no acceptable ENCRYPTION_ALGORITHM found
[CFG] <apsil-10.221.128.183|25> received proposals: ESP:3DES_CBC/HMAC_SHA1_96/NO_EXT_SEQ
[CFG] <apsil-10.221.128.183|25> configured proposals: ESP:3DES_CBC/HMAC_SHA1_96/MODP_1024/NO_EXT_SEQ, ESP:AES_CBC_128/AES_CBC_192/AES_CBC_256/HMAC_SHA2_256_128/HMAC_SHA2_384_192/HMAC_SHA2_512_256/HMAC_SHA1_96/AES_XCBC_96/NO_EXT_SEQ
[DMN] <apsil-10.221.128.183|25> thread 15 received 11
[LIB] <apsil-10.221.128.183|25>  dumping 11 stack frame addresses:
[LIB] <apsil-10.221.128.183|25>   /lib64/libpthread.so.0 @ 0x7f100083d000 [0x7f100084e3b0]
[LIB] <apsil-10.221.128.183|25>     -> ??:?
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000d86603]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/encoding/payloads/sa_payload.c:411
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000dc6ab7]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/sa/ikev1/tasks/quick_mode.c:748
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000dc8d1c]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/sa/ikev1/tasks/quick_mode.c:1153
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000dbc70d]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/sa/ikev1/task_manager_v1.c:1081
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000d94a77]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/sa/ike_sa.c:1587
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libcharon.so.0 @ 0x7f1000d63000 [0x7f1000d8c111]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libcharon/processing/jobs/process_message_job.c:74
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libstrongswan.so.0 @ 0x7f1000ff5000 [0x7f100102cb83]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libstrongswan/processing/processor.c:235
[LIB] <apsil-10.221.128.183|25>   /usr/local/lib/ipsec/libstrongswan.so.0 @ 0x7f1000ff5000 [0x7f100103e4b7]
[LIB] <apsil-10.221.128.183|25>     -> /tmp/STRONGSWAN/strongswan-5.8.3/src/libstrongswan/threading/thread.c:332 (discriminator 3)
[LIB] <apsil-10.221.128.183|25>   /lib64/libpthread.so.0 @ 0x7f100083d000 [0x7f1000844684]
[LIB] <apsil-10.221.128.183|25>     -> ??:?
[LIB] <apsil-10.221.128.183|25>   /lib64/libc.so.6 @ 0x7f1000270000 (clone+0x6d) [0x7f1000376eed]
[LIB] <apsil-10.221.128.183|25>     -> ??:?
[DMN] <apsil-10.221.128.183|25> killing ourself, received critical signal


From: Tobias Brunner <tobias at strongswan.org>

Sent: Wednesday, March 25, 2020 3:07 PM

To: Marco Berizzi <pupilla at hotmail.com>; users at lists.strongswan.org <users at lists.strongswan.org>

Subject: Re: [strongSwan] strongswan 5.8.3 core dump

 


Hi Marco,



> What should I do to debug it?



First, not stripping symbols/debug information from binaries probably

would help.  Then you might already see what the problem is.  Otherwise

try attaching a debugger or use one to analyze the core dump (if one is

created).



Regards,

Tobias



More information about the Users mailing list