[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #26311 [Core Tor/Tor]: Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0

#26311: Error in `/usr/bin/tor': free(): invalid next size (normal):
0x000055ed468598d0
--------------------------+---------------------------------
 Reporter:  cypherpunks   |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.3.5-rc
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+---------------------------------

Comment (by starlight):

 In comment:13 that's a simple math captcha put up by TRAC, should be easy
 to solve.  If it's not your language you could use Google Translate.  If
 the log is very large (5MB+) it will help to compress it with xz.

 I looked at the log from earlier and it blew at 17 minutes after the hour.
 Possibly related to obtaining a new consensus diff.  Recommend

 1) take down the relay and delete all cached-* files the entire diff-cache
 sub-directory in case one of the files is corrupt; eyeball `state` for
 anything that does not look kosher and perhaps delete garbage that may
 appear (make a copy first); the start the relay again to see if it fails

 2) if it continues to fail, please run a debug trace so the exact location
 and call-arc to it can be unraveled; torrc lines for medium detailed
 logging less many highest-volume categories:

 {{{
 # retain normal logging to syslog
 Log="notice syslog"
 # high-volume debug to a file
 LogMessageDomains=1
 LogTimeGranularity=1
 Log="[*]notice [*]info [channel,dir,dirserv,guard,heartbeat,consdiff]debug
 file debuglog
 }}}

 if category with the fail seems to be missing, please
 try to figure out which one it is and add it from the below

 {{{
 general, crypto, net, config, fs, protocol, mm, http, app, control, circ,
 rend, bug, dir, dirserv, edge, acct, hist, handshake, heartbeat, channel,
 sched, guard, consdiff, dos
 }}}

 If you have a technical background it would help if the trace had line
 numbers.  Can get a bit involved obtaining them.  Possily Debian has
 "debug" packages companion to the various library packages (similar to
 RH/Centos) and installing them will magically cause line numbers to appear
 in the call trace.  Possibly tor has a debug package as well--I always
 build from source and I don't know offhand where to look.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26311#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs