Opened 7 years ago

Closed 7 years ago

#7338 closed defect (worksforme)

Tor crashed with segfault libcrypto.so

Reported by: torland Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version: Tor: 0.2.4.3-alpha
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

One of my nodes crashed today with segfault in libcryto.so. Unfortunately I cannot provide much information.

kern.log:

Nov 6 12:52:02 437673 kernel: [6711002.730880] tor[30866]: segfault at 7fc386b85000 ip 00007fc36ba94ad0 sp 00007fffa9d671d0 error 4 in libcrypto.so.1.0.0[7fc36ba29000+19f000]

During the hours before the crash I see many messages like

Nov 06 12:51:46.000 [warn] Your computer is too slow to handle this many circuit creation requests! Please consider using the MaxAdvertisedBandwidth config option or choosing a more restricted exit policy. [58559 similar message(s) suppressed in last 60 seconds]

The number of similar suppressed messages increased over the last hours before the crash.

I updated tor to the last alpha version.

Child Tickets

Change History (5)

comment:1 Changed 7 years ago by torland

Component: - Select a componentTor

comment:2 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:3 Changed 7 years ago by nickm

Status: newneeds_information

Did this happen again after you upgraded? To really track this down and diagnose it, it will probably be necessary to get a stack trace when it happens.

comment:4 Changed 7 years ago by torland

This issue happened once and never happened again. I cant provide a stack trace. I suggest to close this ticket,

comment:5 Changed 7 years ago by nickm

Resolution: worksforme
Status: needs_informationclosed

okay; please reopen if it ever happens again.

Note: See TracTickets for help on using tickets.