Hello,
My very stable Tor relay 16102E458460349EE45C0901DAA6C30094A9BBEA is now rebooting every two days since May 31, 2018.
Running Tor 0.3.3.5-rc (git-4fe9670741478750) on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0f, Zlib 1.2.8
You will find a short extract of the Tor log below :
May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Main process exited, code=killed, status=7/BUS May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Unit entered failed state. May 31 23:12:27 mkuktra systemd[1]: tor@default.service: Failed with result 'signal'. May 31 23:12:28 mkuktra systemd[1]: tor@default.service: Service hold-off time over, scheduling restart.
Jun 05 03:17:59 mkuktra tor[23419]: *** Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0 *** Jun 05 03:17:59 mkuktra tor[23419]: ======= Backtrace: ========= Jun 05 03:17:59 mkuktra tor[23419]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fbb01af9bfb] Jun 05 03:17:59 mkuktra tor[23419]: /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fbb01afffc6]
Any idea ??
Pascal
My very stable Tor relay 16102E458460349EE45C0901DAA6C30094A9BBEA is now rebooting every two days since May 31, 2018.
Running Tor 0.3.3.5-rc (git-4fe9670741478750) on Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0f, Zlib 1.2.8
Jun 05 03:17:59 mkuktra tor[23419]: *** Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0 *** Jun 05 03:17:59 mkuktra tor[23419]: ======= Backtrace: ========= Jun 05 03:17:59 mkuktra tor[23419]: /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fbb01af9bfb] Jun 05 03:17:59 mkuktra tor[23419]: /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fbb01afffc6]
Any idea ??
You are running 0.3.3.5-rc, could you upgrade to v0.3.3.6 and and submit your logfile via a trac ticket if the problem persists? thanks!
On Tue, Jun 5, 2018 at 6:37 AM, Pascal Levasseur pascal.levasseur@topette.eu wrote:
Jun 05 03:17:59 mkuktra tor[23419]: *** Error in `/usr/bin/tor': free(): invalid next size (normal): 0x000055ed468598d0 ***
This is some kind of memory corruption bug, and that could be very bad indeed. If it doesn't go away with 0.3.3.6, the next thing I'd try is running the tor daemon under 'valgrind', which will make it significantly slower but will also trap the actual memory corruption instead of its consequences.
since there has been previously a similar but non-reproducible bug I copied your email into a trac ticket so we can find them in the future, if you have further details please add them here: https://trac.torproject.org/projects/tor/ticket/26311
tor-relays@lists.torproject.org
-
nusenu -
Pascal Levasseur -
Zack Weinberg