[tor-bugs] #14989 [Tor]: While bootstrapping: (Sandbox) Caught a bad syscall attempt (syscall socket), then exits.

[Tor Bug Tracker & Wiki]

#14989: While bootstrapping: (Sandbox) Caught a bad syscall attempt (syscall
socket), then exits.
-------------------------------------------------+-------------------------
 Reporter:  cypherpunks                          |          Owner:
     Type:  defect                               |         Status:  new
 Priority:  normal                               |      Milestone:
Component:  Tor                                  |        Version:  Tor:
 Keywords:  sandbox syscall socket               |  0.2.6.3-alpha
  connection_connect exits                       |  Actual Points:
Parent ID:                                       |         Points:
-------------------------------------------------+-------------------------
 Sandbox 1
 RunAsDaemon 1
 DataDirectory ####
 TransPort #### IsolateClientAddr IsolateClientProtocol
 DNSPort #### IsolateClientAddr
 SocksPort 0
 ControlPort ####
 AutomapHostsOnResolve 1
 VirtualAddrNetwork 172.16.0.0/12

 [notice] Tor v0.2.6.3-alpha (git-69ecf672321755c0) running on Linux with
 Libevent 2.0.21-stable, OpenSSL 1.0.1e-fips and Zlib 1.2.8.
 [notice] Opening DNS listener on ####
 [notice] Opening Transparent pf/netfilter listener on ####
 [notice] Opening Control listener on ####
 [warn] You are running Tor as root. You don't need to, and you probably
 shouldn't.
 [notice] Bootstrapped 0%: Starting
 [notice] We now have enough directory information to build circuits.
 [notice] Bootstrapped 80%: Connecting to the Tor network # reaches 80%
 only using remnants from previously running 0.2.6.2
 [debug] connection_connect(): Connecting to [scrubbed]:9001 # is directly
 followed by:

 (Sandbox) Caught a bad syscall attempt (syscall socket)
 /usr/bin/tor(+0x12f2ba)[0x7fdd4bedb2ba]
 /lib64/libc.so.6(socket+0x7)[0x7fdd4a2c9d07]
 /lib64/libc.so.6(socket+0x7)[0x7fdd4a2c9d07]
 /usr/bin/tor(tor_open_socket_with_extensions+0x52)[0x7fdd4bec6472]
 /usr/bin/tor(+0xc9ea8)[0x7fdd4be75ea8]
 /usr/bin/tor(connection_connect+0x10a)[0x7fdd4be77a1a]
 /usr/bin/tor(connection_or_connect+0x129)[0x7fdd4be89a69]
 /usr/bin/tor(channel_tls_connect+0x88)[0x7fdd4be48898]
 /usr/bin/tor(circuit_handle_first_hop+0x1b8)[0x7fdd4be51b28]
 /usr/bin/tor(circuit_establish_circuit+0x384)[0x7fdd4be52194]
 /usr/bin/tor(circuit_launch_by_extend_info+0xe1)[0x7fdd4be63231]
 /usr/bin/tor(circuit_build_needed_circs+0x30f)[0x7fdd4be6376f]
 /usr/bin/tor(+0x37d30)[0x7fdd4bde3d30]
 /lib64/libevent-2.0.so.5(event_base_loop+0x774)[0x7fdd4b435a44]
 /usr/bin/tor(do_main_loop+0x195)[0x7fdd4bde4965]
 /usr/bin/tor(tor_main+0x16b5)[0x7fdd4bde7735]
 /lib64/libc.so.6(_#_libc_start_main+0xf5)[0x7fdd4a1f5d65] # remove '#'
 /usr/bin/tor(+0x3506d)[0x7fdd4bde106d

 and exits. This does not occur whatsoever with identically configured
 0.2.6.2. Hope this helps.

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