Debian Bug report logs - #358673
racoon: Racoon crashes with SIGSEGV (Segmentation fault)

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Teddy Hogeborn <teddy@fukt.bth.se>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: racoon: Racoon crashes with SIGSEGV (Segmentation fault)

Date: Thu, 23 Mar 2006 21:11:56 +0100

Package: racoon
Version: 1:0.5.2-1sarge1
Severity: important


Since upgrading to sarge I have been experiencing infrequent crashes
by racoon on more than one machine which did not exhibit this
behaviour in woody.  I attached a "strace" to the racoon process on
two of the machines which exhibited the most crashes and got a live
SEGV fault.  I am reluctant to include the full trace in a public bug
tracking system, so I have replaced some data with "####" in the trace
below:

===========================================
[...]
time([1143105094])                      = 1143105094
time([1143105094])                      = 1143105094
time([1143105094])                      = 1143105094
select(12, [3 4 7 9 10 11], NULL, NULL, {3, 0}) = 1 (in [10], left {2, 996000})
getsockname(10, {sa_family=AF_INET, sin_port=htons(500), sin_addr=inet_addr("194.47.143.3")}, [16]) = 0
recvmsg(10, {msg_name(16)={sa_family=AF_INET, sin_port=htons(500), sin_addr=inet_addr("194.47.144.23")}, msg_iov(1)=[{"####"..., 32}], msg_controllen=24, {cmsg_len=24, cmsg_level=SOL_IP, cmsg_type=, ...}, msg_flags=MSG_TRUNC}, MSG_PEEK) = 32
getsockname(10, {sa_family=AF_INET, sin_port=htons(500), sin_addr=inet_addr("194.47.143.3")}, [16]) = 0
recvmsg(10, {msg_name(16)={sa_family=AF_INET, sin_port=htons(500), sin_addr=inet_addr("194.47.144.23")}, msg_iov(1)=[{"####"..., 68}], msg_controllen=24, {cmsg_len=24, cmsg_level=SOL_IP, cmsg_type=, ...}, msg_flags=0}, 0) = 68
time(NULL)                              = 1143105094
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 1671 detached
===========================================

194.47.143.3 above is the host machine itself, 194.47.144.23 is a
Windows machine I have been trying (with only partial success) to talk
IPsec with.

The crashes are infrequent (only 5 or so crashes have happened in
total) but recurring, and on more on one machine, which leads me to
exclude the possibility of hardware failure.

/Teddy

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages racoon depends on:
ii  debconf                  1.4.30.13       Debian configuration management sy
ii  ipsec-tools              1:0.5.2-1sarge1 IPsec tools for Linux
ii  libc6                    2.3.2.ds1-22    GNU C Library: Shared libraries an
ii  libssl0.9.7              0.9.7e-3sarge1  SSL shared libraries
ii  perl                     5.8.4-8sarge3   Larry Wall's Practical Extraction 

-- debconf information:
* racoon/config_mode: racoon-tool

Message #12 received at 358673@bugs.debian.org (full text, mbox, reply):

From: Stefan Bauer <stefan.bauer@cubewerk.de>

To: 358673@bugs.debian.org

Subject: Re: racoon: Racoon crashes with SIGSEGV (Segmentation fault)

Date: Tue, 23 Feb 2010 12:49:06 +0100

Teddy,

as this is a rather old bug and might already got fixed in upstream,
could you please try a more recent version and report back if it
still happens?

thanks

stefan
-- 
Stefan Bauer -----------------------------------------
PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34
-------- plzk.de - Linux - because it works ----------

Message #17 received at 358673-done@bugs.debian.org (full text, mbox, reply):

From: Stefan Bauer <stefan.bauer@cubewerk.de>

To: 358673-done@bugs.debian.org

Subject: cleaning up old reports

Date: Mon, 01 Mar 2010 12:43:20 +0100

As this bug report is almost 5 years old and there is no response
from the initial creator - i close this bug hereby.

Stefan
-- 
Stefan Bauer -----------------------------------------
PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34
-------- plzk.de - Linux - because it works ----------

Send a report that this bug log contains spam.