Bug 1046220 - [abrt] strongswan: segv_handler(): charon killed by SIGABRT
Summary: [abrt] strongswan: segv_handler(): charon killed by SIGABRT
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: strongswan
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:5702f131025fee83feac3b41687...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-24 06:45 UTC by Michael Hampton
Modified: 2014-03-14 19:00 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-14 18:45:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.43 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: cgroup (161 bytes, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: core_backtrace (43.69 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: dso_list (8.24 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: environ (376 bytes, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: limits (1.29 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: maps (42.62 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: open_fds (819 bytes, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: proc_pid_status (903 bytes, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
File: var_log_messages (19.55 KB, text/plain)
2013-12-24 06:45 UTC, Michael Hampton 		no flags Details
View All

Description Michael Hampton 2013-12-24 06:45:27 UTC 
Description of problem:
Crash occurred at service startup

Version-Release number of selected component:
strongswan-5.1.0-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/strongswan/charon
crash_function: segv_handler
executable:     /usr/libexec/strongswan/charon
kernel:         3.12.5-302.fc20.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 segv_handler at charon.c:194
 #4 BN_mod_exp_mont at /lib64/libcrypto.so.10
 #5 DH_check_pub_key at /lib64/libcrypto.so.10
 #6 compute_key at /lib64/libcrypto.so.10
 #7 set_other_public_value at openssl_diffie_hellman.c:98
 #8 process_payloads at sa/ikev2/tasks/ike_init.c:211
 #9 process_i at sa/ikev2/tasks/ike_init.c:516
 #10 process_response at sa/ikev2/task_manager_v2.c:540
 #11 process_message at sa/ikev2/task_manager_v2.c:1212
 #13 execute at processing/jobs/process_message_job.c:74
Comment 1 Michael Hampton 2013-12-24 06:45:34 UTC 
Created attachment 841088 [details]
File: backtrace
Comment 2 Michael Hampton 2013-12-24 06:45:35 UTC 
Created attachment 841089 [details]
File: cgroup
Comment 3 Michael Hampton 2013-12-24 06:45:37 UTC 
Created attachment 841090 [details]
File: core_backtrace
Comment 4 Michael Hampton 2013-12-24 06:45:39 UTC 
Created attachment 841091 [details]
File: dso_list
Comment 5 Michael Hampton 2013-12-24 06:45:40 UTC 
Created attachment 841092 [details]
File: environ
Comment 6 Michael Hampton 2013-12-24 06:45:42 UTC 
Created attachment 841093 [details]
File: limits
Comment 7 Michael Hampton 2013-12-24 06:45:44 UTC 
Created attachment 841094 [details]
File: maps
Comment 8 Michael Hampton 2013-12-24 06:45:46 UTC 
Created attachment 841095 [details]
File: open_fds
Comment 9 Michael Hampton 2013-12-24 06:45:47 UTC 
Created attachment 841096 [details]
File: proc_pid_status
Comment 10 Michael Hampton 2013-12-24 06:45:49 UTC 
Created attachment 841097 [details]
File: var_log_messages
Comment 11 Pavel Šimerda (pavlix) 2014-03-05 11:10:56 UTC 
Avesh, is this related to the fix you were doing in rawhide?
Comment 12 Pavel Šimerda (pavlix) 2014-03-14 17:52:20 UTC 
The retrace server says there's been just one event, is there a reliable way to reproduce the problem or it happened just once?
Comment 13 Michael Hampton 2014-03-14 18:45:18 UTC 
I've not seen this crash since updating to 5.1.1. If there are no other reports, it can probably be closed.
Comment 14 Pavel Šimerda (pavlix) 2014-03-14 19:00:58 UTC 
Thanks!
Note You need to log in before you can comment on or make changes to this bug.