Opened 3 years ago

Closed 3 years ago

#19800 closed defect (user disappeared)

After install, launching tor from shell results in segfault

Reported by: dmirtillo Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7.6
Severity: Normal Keywords: segfault
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I installed tor on CentOS Linux release 7.2.1511 (Core) with the packages from epel-release.

I then proceeded to configure the /etc/tor/torrc file, but i was not aware there was a service active so i tried launching tor from shell - seeing the RunAsDaemon directive.

This is not the expected behaviour, i should have been told there was a service already running.

[root@server ~]# tor
Aug 02 10:51:24.202 [notice] Tor v0.2.7.6 running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1e-fips and Zlib 1.2.7.
Aug 02 10:51:24.202 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Aug 02 10:51:24.202 [notice] Read configuration file "/etc/tor/torrc".
Aug 02 10:51:24.204 [notice] You configured a non-loopback address '10.0.0.20:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Aug 02 10:51:24.204 [notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
Aug 02 10:51:24.204 [notice] Based on detected system memory, MaxMemInQueues is set to 2843 MB. You can override this by setting MaxMemInQueues by hand.
Aug 02 10:51:24.204 [notice] You configured a non-loopback address '10.0.0.20:9100' for SocksPort. This allows everybody on your local network to use your machine as a proxy. Make sure this is what you wanted.
Aug 02 10:51:24.204 [notice] Opening Socks listener on 127.0.0.1:9050

============================================================ T= 1470127884
Tor 0.2.7.6 died: Caught signal 11
tor(+0x12bb28)[0x7f6405597b28]
tor(retry_all_listeners+0x689)[0x7f640554a009]
tor(retry_all_listeners+0x689)[0x7f640554a009]
tor(set_options+0x1889)[0x7f640553f9a9]
tor(options_init_from_string+0x2d9)[0x7f64055404c9]
tor(options_init_from_torrc+0x1d7)[0x7f64055407f7]
tor(tor_init+0x2d4)[0x7f64054aab84]
tor(tor_main+0x55)[0x7f64054acc75]
tor(main+0x19)[0x7f64054a7809]
/lib64/libc.so.6(libc_start_main+0xf5)[0x7f6403aa6b15]
tor(+0x3b85d)[0x7f64054a785d]
Aborted

Child Tickets

Change History (4)

comment:1 Changed 3 years ago by nickm

Component: Core TorCore Tor/Tor

comment:2 Changed 3 years ago by nickm

This isn't still happening, is it? Did it turn out to be reproducible?

comment:3 Changed 3 years ago by nickm

Milestone: Tor: unspecified
Status: newneeds_information

comment:4 Changed 3 years ago by nickm

Resolution: user disappeared
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.