Tor issueshttps://gitlab.torproject.org/tpo/core/tor/-/issues2020-06-27T14:10:42Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/415seg fault on r98012020-06-27T14:10:42ZRoger Dingledineseg fault on r9801moria1 died last night:
#0 0x0000002a95e91be0 in strlen () from /lib/libc.so.6
#1 0x0000002a95e5fcf5 in vfprintf () from /lib/libc.so.6
legacy/trac#2 0x0000002a95e84c76 in vsnprintf () from /lib/libc.so.6
legacy/trac#3 0x00000000004...moria1 died last night:
#0 0x0000002a95e91be0 in strlen () from /lib/libc.so.6
#1 0x0000002a95e5fcf5 in vfprintf () from /lib/libc.so.6
legacy/trac#2 0x0000002a95e84c76 in vsnprintf () from /lib/libc.so.6
legacy/trac#3 0x0000000000465295 in tor_vsnprintf (
str=0x7fbfffcc6c "Forgetting obsolete (too old) routerinfo for router 'pr 16 21:11:03.0ôÿ¿\177", size=9962,
format=0x7fbffff3e0 "\027\214®-\031Â80¼Æ\002", args=0x1) at compat.c:320
legacy/trac#4 0x00000000004615d3 in format_msg (
buf=0x7fbfffcc30 "Apr 16 21:11:09.114 [info] routerlist_remove_old_routers(): Forgetting obsolete (too old) routerinfo for router 'pr 16 21:11:03.0ôÿ¿\177", buf_len=10022, domain=8192, severity=6,
funcname=0x494ea0 "routerlist_remove_old_routers",
format=0x495bc0 "Forgetting obsolete (too old) routerinfo for router '%s'", ap=0x7fbffff3a0) at log.c:185
legacy/trac#5 0x0000000000460be1 in logv (severity=6, domain=8192,
funcname=0x494ea0 "routerlist_remove_old_routers",
format=0x495bc0 "Forgetting obsolete (too old) routerinfo for router '%s'", ap=0x7fbffff3a0) at log.c:232
legacy/trac#6 0x0000000000460d1f in _log_fn (severity=766413847, domain=2515679776,
fn=0x7fbffff3e0 "\027\214®-\031Â80¼Æ\002",
format=0x1 <Address 0x1 out of bounds>) at log.c:278
legacy/trac#7 0x0000000000454363 in routerlist_remove_old_routers () at routerlist.c:2191
legacy/trac#8 0x0000000000457f3b in update_router_have_minimum_dir_info ()
legacy/trac#9 0x0000000000457e90 in router_have_minimum_dir_info () at routerlist.c:4194
legacy/trac#10 0x0000000000440ccd in run_scheduled_events (now=1176772269) at main.c:931
legacy/trac#11 0x0000000000441219 in second_elapsed_callback (fd=766413847, event=14880,
args=0x7fbffff3e0) at main.c:1063
legacy/trac#12 0x0000002a9599b82d in event_base_priority_init ()
from /usr/lib/libevent-1.1a.so.1
legacy/trac#13 0x0000002a9599ba72 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#14 0x0000002a9599b8e5 in event_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#15 0x0000002a9599b84b in event_dispatch () from /usr/lib/libevent-1.1a.so.1
legacy/trac#16 0x000000000044164b in do_main_loop () at main.c:1266
legacy/trac#17 0x000000000044235a in tor_main (argc=766413847, argv=0x2a95f23a20)
at main.c:2492
legacy/trac#18 0x0000002a95e31441 in __libc_start_main () from /lib/libc.so.6
legacy/trac#19 0x000000000040622a in _start () at ../sysdeps/x86_64/elf/start.S:96
iu
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/413cannot compile svn 99442020-06-27T14:10:42ZTraccannot compile svn 9944When I try to build svn 9944, I receive the following:
gcc -g -O2 -Wall -g -O2 -L/usr/local/lib -Wl,-R/usr/local/lib -o tor buffers.o circuitbuild.o circuitlist.o circuituse.o command.o config.o connection.o connection_edge.o conne...When I try to build svn 9944, I receive the following:
gcc -g -O2 -Wall -g -O2 -L/usr/local/lib -Wl,-R/usr/local/lib -o tor buffers.o circuitbuild.o circuitlist.o circuituse.o command.o config.o connection.o connection_edge.o connection_or.o control.o cpuworker.o directory.o dirserv.o dns.o hibernate.o main.o onion.o policies.o relay.o rendcommon.o rendclient.o rendmid.o rendservice.o rephist.o router.o routerlist.o routerparse.o eventdns.o tor_main.o ../common/libor.a ../common/libor-crypto.a -lz -lpthread -levent -lssl -lcrypto
relay.o(.text+0x2d2e): In function `init_cell_pool':
/home/yancm/torsrc/src/or/relay.c:1488: undefined reference to `mp_pool_new'
relay.o(.text+0x2da4): In function `free_cell_pool':
/home/yancm/torsrc/src/or/relay.c:1496: undefined reference to `mp_pool_destroy'
relay.o(.text+0x2e1e): In function `clean_cell_pool':
/home/yancm/torsrc/src/or/relay.c:1505: undefined reference to `mp_pool_clean'
relay.o(.text+0x2f0e): In function `cell_queue_append_packed_copy':
/home/yancm/torsrc/src/or/relay.c:1519: undefined reference to `mp_pool_get'
relay.o(.text+0x2f4f): In function `cell_queue_clear':
/home/yancm/torsrc/src/or/relay.c:1512: undefined reference to `mp_pool_release'
relay.o(.text+0x3458): In function `connection_or_flush_from_first_active_circuit':
/home/yancm/torsrc/src/or/relay.c:1512: undefined reference to `mp_pool_release'
*** Error code 1
Stop.
make: stopped in /home/yancm/torsrc/src/or
*** Error code 1
Stop.
make: stopped in /home/yancm/torsrc/src
*** Error code 1
Stop.
make: stopped in /home/yancm/torsrc
*** Error code 1
Stop.
make: stopped in /home/yancm/torsrc
[1] Exit 1 make
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: yancmhttps://gitlab.torproject.org/tpo/core/tor/-/issues/412Tor v0.1.2.12-rc segfaults after a while2020-06-27T14:10:42ZTracTor v0.1.2.12-rc segfaults after a whileuname -mrs
FreeBSD 6.2-RELEASE-p3 i386
Tor version 0.1.2.12-rc.
Core was generated by `tor'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libz.so.3...done.
Loaded symbols for /lib/libz.so.3
Reading s...uname -mrs
FreeBSD 6.2-RELEASE-p3 i386
Tor version 0.1.2.12-rc.
Core was generated by `tor'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libz.so.3...done.
Loaded symbols for /lib/libz.so.3
Reading symbols from /lib/libssl.so.5...done.
Loaded symbols for /lib/libssl.so.5
Reading symbols from /lib/libcrypto.so.5...done.
Loaded symbols for /lib/libcrypto.so.5
Reading symbols from /lib/libpthread.so.2...done.
Loaded symbols for /lib/libpthread.so.2
Reading symbols from /lib/libevent-1.2a.so.1...done.
Loaded symbols for /lib/libevent-1.2a.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x2827f537 in pthread_testcancel () from /lib/libpthread.so.2
[New Thread 0x8110200 (runnable)]
[New Thread 0x8110000 (LWP 100098)]
[New Thread 0x80f4000 (runnable)]
[New LWP 100066]
(gdb) where
#0 0x2827f537 in pthread_testcancel () from /lib/libpthread.so.2
#1 0x28277ec8 in pthread_mutexattr_init () from /lib/libpthread.so.2
legacy/trac#2 0x28108450 in ?? ()
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: Orumhttps://gitlab.torproject.org/tpo/core/tor/-/issues/411Tor Dies, SVN 9918 (relay.c:1562, main.c:1271, tor_main.c:22)2020-06-27T14:10:42ZTracTor Dies, SVN 9918 (relay.c:1562, main.c:1271, tor_main.c:22)VER: Checked out revision 9918.
LOG:
Apr 01 06:23:12.256 [err] Bug: relay.c:1562: next_circ_on_conn_p: Assertion conn == orcirc->p_conn failed; aborting.
# gdb /usr/bin/tor /var/lib/tor/core.7405
GNU gdb Red Hat Linux (6.3.0.0-1.132...VER: Checked out revision 9918.
LOG:
Apr 01 06:23:12.256 [err] Bug: relay.c:1562: next_circ_on_conn_p: Assertion conn == orcirc->p_conn failed; aborting.
# gdb /usr/bin/tor /var/lib/tor/core.7405
GNU gdb Red Hat Linux (6.3.0.0-1.132.EL4rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
Core was generated by `/usr/bin/tor -f /etc/tor/torrc --pidfile /var/run/tor/tor.pid --log notice file'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/lib/libz.so.1...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/tls/libpthread.so.0...done.
Loaded symbols for /lib/tls/libpthread.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /usr/lib/libevent-1.3b.so.1...Reading symbols from /usr/lib/debug/usr/lib/libevent-1.3b.so.1.0.3.debug...done.
done.
Loaded symbols for /usr/lib/libevent-1.3b.so.1
Reading symbols from /lib/libssl.so.4...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/libcrypto.so.4...done.
Loaded symbols for /lib/libcrypto.so.4
Reading symbols from /lib/tls/libc.so.6...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /usr/lib/libgssapi_krb5.so.2...done.
Loaded symbols for /usr/lib/libgssapi_krb5.so.2
Reading symbols from /usr/lib/libkrb5.so.3...done.
Loaded symbols for /usr/lib/libkrb5.so.3
Reading symbols from /lib/libcom_err.so.2...done.
Loaded symbols for /lib/libcom_err.so.2
Reading symbols from /usr/lib/libk5crypto.so.3...done.
Loaded symbols for /usr/lib/libk5crypto.so.3
Reading symbols from /lib/libresolv.so.2...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnss_files.so.2...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /lib/libnss_dns.so.2...done.
Loaded symbols for /lib/libnss_dns.so.2
#0 0x0060e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
(gdb) bt
#0 0x0060e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1 0x0064e7a5 in raise () from /lib/tls/libc.so.6
legacy/trac#2 0x00650209 in abort () from /lib/tls/libc.so.6
legacy/trac#3 0x08087870 in make_circuit_inactive_on_conn (circ=0x8b6c940, conn=0x921d1b8) at relay.c:1562
legacy/trac#4 0x08054a23 in circuit_set_circid_orconn_helper (circ=0x8b6c940, id=0, conn=0x0, old_id=57696, old_conn=0x921d1b8, active=1)
at circuitlist.c:107
legacy/trac#5 0x08054c8b in circuit_set_p_circid_orconn (circ=0x8b6c940, id=0, conn=0x0) at circuitlist.c:152
legacy/trac#6 0x08059e6f in command_process_cell (cell=0xbffa09f0, conn=0x921d1b8) at or.h:1555
legacy/trac#7 0x0806cb76 in connection_or_process_inbuf (conn=0x921d1b8) at connection_or.c:780
legacy/trac#8 0x080638ad in connection_process_inbuf (conn=Variable "conn" is not available.
) at or.h:962
legacy/trac#9 0x08065d70 in connection_handle_read (conn=0x921d1b8) at connection.c:1514
legacy/trac#10 0x08083038 in conn_read_callback (fd=30, event=2, _conn=0x921d1b8) at main.c:427
legacy/trac#11 0x0098162d in event_base_loop (base=0x86affd8, flags=Variable "flags" is not available.
) at event.c:315
legacy/trac#12 0x009816e0 in event_loop (flags=0) at event.c:366
legacy/trac#13 0x00981704 in event_dispatch () at event.c:329
legacy/trac#14 0x08084e27 in tor_main (argc=15, argv=0xbffa1174) at main.c:1271
legacy/trac#15 0x080a3c23 in main (argc=15, argv=0xbffa1174) at tor_main.c:22
(gdb)
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: xiandoNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/410Bug: circuituse.c:530 (svn 9918)2020-06-27T14:10:42ZTracBug: circuituse.c:530 (svn 9918)fyi...
tor is crashing with the following log message:
Mar 31 13:44:42.085 [err] circuit_detach_stream(): Bug: edge conn not in circuit's list?
Mar 31 13:44:42.085 [err] Bug: circuituse.c:530: circuit_detach_stream: Assertion 0 failed; ...fyi...
tor is crashing with the following log message:
Mar 31 13:44:42.085 [err] circuit_detach_stream(): Bug: edge conn not in circuit's list?
Mar 31 13:44:42.085 [err] Bug: circuituse.c:530: circuit_detach_stream: Assertion 0 failed; aborting.
gdb bt gives:
clarity 74 -> gdb /usr/local/bin/tor tor.core
GNU gdb 5.3nb1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386--netbsdelf"...
Core was generated by `tor'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/lib/libz.so.0...done.
Loaded symbols for /usr/lib/libz.so.0
Reading symbols from /usr/lib/libpthread.so.0...done.
Loaded symbols for /usr/lib/libpthread.so.0
Reading symbols from /usr/local/lib/libevent-1.3b.so.1...done.
Loaded symbols for /usr/local/lib/libevent-1.3b.so.1
Reading symbols from /usr/lib/libssl.so.3...done.
Loaded symbols for /usr/lib/libssl.so.3
Reading symbols from /usr/lib/libcrypto.so.2...done.
Loaded symbols for /usr/lib/libcrypto.so.2
Reading symbols from /usr/lib/libc.so.12...done.
Loaded symbols for /usr/lib/libc.so.12
Reading symbols from /lib/libcrypt.so.0...done.
Loaded symbols for /lib/libcrypt.so.0
Reading symbols from /usr/libexec/ld.elf_so...done.
Loaded symbols for /usr/libexec/ld.elf_so
#0 0xbd9f80fb in kill () from /usr/lib/libc.so.12
(gdb) bt
#0 0xbd9f80fb in kill () from /usr/lib/libc.so.12
(gdb) bt
#0 0xbd9f80fb in kill () from /usr/lib/libc.so.12
#1 0xbda7917f in abort () from /usr/lib/libc.so.12
legacy/trac#2 0x08057d77 in circuit_detach_stream (circ=0x8edfc00, conn=0x8edfe00)
at circuituse.c:530
legacy/trac#3 0x0807d949 in dns_resolve (exitconn=0x8edfe00) at dns.c:631
legacy/trac#4 0x0806ac1d in connection_exit_begin_resolve (cell=0xbfbfe750,
circ=0x8edfc00) at connection_edge.c:2304
legacy/trac#5 0x08088785 in connection_edge_process_relay_cell (cell=0xbfbfe750,
circ=0x8edfc00, conn=0x0, layer_hint=0x0) at or.h:1555
legacy/trac#6 0x080868b9 in circuit_receive_relay_cell (cell=0xbfbfe750, circ=0x8edfc00,
cell_direction=2) at relay.c:170
legacy/trac#7 0x08059d30 in command_process_relay_cell (cell=0xbfbfe750, conn=0x8e6fb00)
at command.c:331
legacy/trac#8 0x0806ccdd in connection_or_process_cells_from_inbuf (conn=0x8e6fb00)
at connection_or.c:780
legacy/trac#9 0x08063cfe in connection_handle_read (conn=0x8e6fb00) at connection.c:1514
legacy/trac#10 0x0808263c in conn_read_callback (fd=25, event=2, _conn=0x8e6fb00)
at main.c:427
legacy/trac#11 0xbdbbb64c in event_process_active (base=0x80f3300) at event.c:315
legacy/trac#12 0xbdbbb8e2 in event_base_loop (base=0x80f3300, flags=0) at event.c:431
legacy/trac#13 0xbdbbb77b in event_loop (flags=0) at event.c:366
legacy/trac#14 0xbdbbb6ba in event_dispatch () at event.c:329
legacy/trac#15 0x08083ccc in do_main_loop () at main.c:1271
---Type <return> to continue, or q <return> to quit---
legacy/trac#16 0x0808498d in tor_main (argc=7, argv=0xbfbfed1c) at main.c:2497
legacy/trac#17 0x080a2c0b in main (argc=7, argv=0xbfbfed1c) at tor_main.c:22
legacy/trac#18 0x0804c996 in ___start ()
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: yancmhttps://gitlab.torproject.org/tpo/core/tor/-/issues/409Tor doesn't treat 0 as a valid port2020-06-27T14:10:42ZTracTor doesn't treat 0 as a valid portTor does not treat the officially reserved port 0 as a valid port when considering
exit policies. For example, "reject *:0-19" would be summarixed as "reject *:1-19"
and would show up in the directory as such.
Actual version of tor is ...Tor does not treat the officially reserved port 0 as a valid port when considering
exit policies. For example, "reject *:0-19" would be summarixed as "reject *:1-19"
and would show up in the directory as such.
Actual version of tor is 0.1.2.12-rc, but that is not listed in the options.
Reference: http://www.iana.org/assignments/port-numbers
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: Orumhttps://gitlab.torproject.org/tpo/core/tor/-/issues/407Unable to mmap new descriptor file2020-06-27T14:10:43ZTracUnable to mmap new descriptor fileMar 29 23:23:54:062 [Warning] Unable to mmap new descriptor file at 'C:\Documents and Settings\Ils Haxor\Application Data\tor/cached-routers'.
This warning keeps popping up every time I run Tor. No matter what version I have used, both s...Mar 29 23:23:54:062 [Warning] Unable to mmap new descriptor file at 'C:\Documents and Settings\Ils Haxor\Application Data\tor/cached-routers'.
This warning keeps popping up every time I run Tor. No matter what version I have used, both stable and the newest one, this keeps occurring.
I am pretty sure this is my only problem, but I haven't even been able to use Tor yet. Anyone know what to do?
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: Raindoghttps://gitlab.torproject.org/tpo/core/tor/-/issues/405exitlist believes obsolete descriptors too2020-06-27T14:10:43ZRoger Dingledineexitlist believes obsolete descriptors tooWhen you run exitlist with your DirPort enabled, you have many server descriptors
in your cached-routers file. Exitlist looks at every one of them. So if the router
allowed a connection within the past few days, exitlist lists it -- even...When you run exitlist with your DirPort enabled, you have many server descriptors
in your cached-routers file. Exitlist looks at every one of them. So if the router
allowed a connection within the past few days, exitlist lists it -- even if a newer
descriptor says that its exit policy wouldn't allow that.
I guess that means exitlist should learn about "published" timestamps, and learn how
to recognize if two descriptors are from the same server.
[Automatically added by flyspray2trac: Operating System: All]Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/404seg fault on 0.1.2.9-rc dir authority2020-06-27T14:10:43ZRoger Dingledineseg fault on 0.1.2.9-rc dir authorityMar 10 09:52:01.416 [info] dirserv_orconn_tls_done(): Found router liquidvibration3 to be reachable. Yay.
Mar 10 09:52:01.542 [info] routerlist_remove_old_routers(): Forgetting obsolete (too old) routerinfo for router 'mrs5'
Mar 10 09:52...Mar 10 09:52:01.416 [info] dirserv_orconn_tls_done(): Found router liquidvibration3 to be reachable. Yay.
Mar 10 09:52:01.542 [info] routerlist_remove_old_routers(): Forgetting obsolete (too old) routerinfo for router 'mrs5'
Mar 10 09:52:01.562 [info] dirserv_pick_cached_dir_obj(): The server directory is still clean; reusing.
Mar 10 09:52:01.711 [err] routerlist.c:4485: routerlist_assert_ok: Assertion r == r2 failed; aborting.
This was moria1. I'll hopefully get a core if it happens a second time.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/4030.1.2.x warns about non-named servers out of the blue2020-06-27T14:10:43ZRoger Dingledine0.1.2.x warns about non-named servers out of the blueMar 11 18:19:50.085 [warn] You specified a server "BlueStar88b" by name, but thi
s name is not registered, so it could be used by any server, not just the one yo
u meant. To make sure you get the same server in the future, refer to it by...Mar 11 18:19:50.085 [warn] You specified a server "BlueStar88b" by name, but thi
s name is not registered, so it could be used by any server, not just the one yo
u meant. To make sure you get the same server in the future, refer to it by key,
as "$F5B9ABFAB2C44E790AAFC5344B9F00FBDF6DC36E".
Problem is, I didn't ever mention it by name. I only have info level logs, but
they don't help at all. I was probably browsing at the time.
I guess something still refers to something by nickname, internally. I'll try
to collect more info as time goes by.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/402Mac Uninstall2020-06-27T14:10:43ZTracMac UninstallWhen I use the uninstall instructions for Mac OS X 10.4 (Tiger) Universal Binary : Tor & Privoxy & Vidalia bundle: 0.1.1.29, I get the following output. What I am doing wrong? How can I uninstall all components?
Welcome to Darwin!
jaso...When I use the uninstall instructions for Mac OS X 10.4 (Tiger) Universal Binary : Tor & Privoxy & Vidalia bundle: 0.1.1.29, I get the following output. What I am doing wrong? How can I uninstall all components?
Welcome to Darwin!
jason-edwards-computer:~ Jason$ cd /Library/Tor
jason-edwards-computer:/Library/Tor Jason$ sudo -s
Password:
jason-edwards-computer:/Library/Tor root# ./uninstall_tor_bundle.sh
bash: ./uninstall_tor_bundle.sh: No such file or directory
jason-edwards-computer:/Library/Tor root#
Some background...
I installed the bundle without X11 Macports or Fink installed on my computer.
I now have X11 installed. I am not sure if this makes a differnce.
Jay
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: jasonedwards3Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/tpo/core/tor/-/issues/399OP sometimes does not fetch hidden service descriptor2020-06-27T14:10:43ZKarsten LoesingOP sometimes does not fetch hidden service descriptorWhen the onion proxy receives a hidden service request from the client and has no up-to-date hidden service descriptor,
it should make a request to the directory. However, this is only done when Tor does not already have a connection to ...When the onion proxy receives a hidden service request from the client and has no up-to-date hidden service descriptor,
it should make a request to the directory. However, this is only done when Tor does not already have a connection to the
directory, yet. So, from time to time, Tor thinks that there is already a connection to the Dir running and aborts the
hidden service descriptor request. But---and here comes the problem---the request is simply dropped and the descriptor
is NOT requested later. Only a subsequent request from the client application leads to another consideration to fetch
the descriptor from the directory (possibly with the same result: dropped).
Should the request be added to some "request queue" and be performed during a periodic maintenance tasks?
I added my log file (with some additional log statements) that shows the affected methods.
1172409375015 Tor Client Feb 25 14:16:15.015 [info] connection_ap_handshake_process_socks(): method invoked: 67
1172409375015 Tor Client Feb 25 14:16:15.015 [info] connection_ap_handshake_process_socks(): method invoked: 67
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_ap_handshake_process_socks(): method invoked: 67
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_ap_handshake_rewrite_and_attach(): event fired: C01
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_ap_handshake_rewrite_and_attach(): method invoked: 45
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_ap_handshake_rewrite_and_attach(): Got a hidden service request for ID 'scxfcfgpypn33tjt'
1172409375031 Tor Client Feb 25 14:16:15.031 [info] rend_cache_lookup_entry(): method invoked: 03
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_ap_handshake_rewrite_and_attach(): Unknown descriptor scxfcfgpypn33tjt. Fetching.
1172409375031 Tor Client Feb 25 14:16:15.031 [info] rend_client_refetch_renddesc(): event fired: C03
1172409375031 Tor Client Feb 25 14:16:15.031 [info] rend_client_refetch_renddesc(): method invoked: 35
1172409375031 Tor Client Feb 25 14:16:15.031 [info] connection_get_by_type_state_rendquery(): method invoked: 62
1172409375031 Tor Client Feb 25 14:16:15.031 [info] rend_cmp_service_ids(): Comparing two strings scxfcfgpypn33tjt and with result 1
1172409375046 Tor Client Feb 25 14:16:15.031 [info] connection_get_by_type_state_rendquery(): This method says we already have a connection running: scxfcfgpypn33tjt,
1172409375046 Tor Client Feb 25 14:16:15.031 [info] rend_client_refetch_renddesc(): Would fetch a new renddesc here (for "scxfcfgpypn33tjt"), but one is already in progress.
1172409375046 Tor Client Feb 25 14:16:15.046 [info] connection_edge_process_inbuf(): data from edge while in 'waiting for rendezvous desc' state. Leaving it on buffer.
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]https://gitlab.torproject.org/tpo/core/tor/-/issues/392bug in memset call2020-06-27T14:10:45ZTracbug in memset callcommon/compat.c:283: memset(handle, sizeof(tor_mmap_t), 0);
Last two params are reversed.
[Automatically added by flyspray2trac: Operating System: Other]
**Trac**:
**Username**: fookoowacommon/compat.c:283: memset(handle, sizeof(tor_mmap_t), 0);
Last two params are reversed.
[Automatically added by flyspray2trac: Operating System: Other]
**Trac**:
**Username**: fookoowahttps://gitlab.torproject.org/tpo/core/tor/-/issues/391RedHat 5.0beta Enterprise2020-06-27T14:10:45ZAndrew LewmanRedHat 5.0beta EnterpriseThis hack does not quite work out:
%define _build_name_fmt %%{NAME}-%%{VERSION}-%%{RELEASE}.%{target_cpu}.rpm ...This hack does not quite work out:
%define _build_name_fmt %%{NAME}-%%{VERSION}-%%{RELEASE}.%{target_cpu}.rpm
I get:
error: Could not open /usr/src/redhat/RPMS/tor-0.1.1.26-tor.0.rh5_0.i386.rpm: Permission denied
I have /usr/src/redhat/RPMS/i386/ , for example,
where user "rpmbuild" can write to.
tor.spec is the first one to define _build_name_fmt.
Others don't define it and work.
But on the other hand, I don't have many src.rpms which try to
work with more than one distro.
[Automatically added by flyspray2trac: Operating System: Other Linux]Andrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/tpo/core/tor/-/issues/390Assertion !connection_is_on_closeable_list(conn) failed2020-06-27T14:10:45ZTracAssertion !connection_is_on_closeable_list(conn) failedUsing tor version 0.1.1.26-1~~sarge.1 on Debian Sarge:
# uname -a
Linux wormhole.ynfonatic.de 2.6.9-023stab033.1-smp #1 SMP Mon Oct 23 21:47:03 MSD 2006 i686 GNU/Linux
Tor crashes with a core-dump:
# gdb /usr/sbin/tor core.16144
(gdb...Using tor version 0.1.1.26-1~~sarge.1 on Debian Sarge:
# uname -a
Linux wormhole.ynfonatic.de 2.6.9-023stab033.1-smp #1 SMP Mon Oct 23 21:47:03 MSD 2006 i686 GNU/Linux
Tor crashes with a core-dump:
# gdb /usr/sbin/tor core.16144
(gdb) bt
#0 0xb7d7683b in raise () from /lib/tls/libc.so.6
#1 0xb7d77fa2 in abort () from /lib/tls/libc.so.6
legacy/trac#2 0x0806488e in connection_free (conn=0x80b7940) at connection.c:261
legacy/trac#3 0x08082b79 in dns_cancel_pending_resolve (
address=0x8fad7d8 "ðv|\tÀna\t\020") at dns.c:535
legacy/trac#4 0x080861e2 in connection_unlink (conn=0x827ed28, remove=1) at main.c:209
legacy/trac#5 0x0808714f in conn_close_if_marked (i=0) at main.c:523
legacy/trac#6 0x08086e14 in close_closeable_connections () at main.c:388
legacy/trac#7 0xb7e85c79 in event_base_priority_init () from /usr/lib/libevent-1.1a.so.1
legacy/trac#8 0xb7e85f65 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#9 0xb7e85dcb in event_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#10 0xb7e85cb0 in event_dispatch () from /usr/lib/libevent-1.1a.so.1
legacy/trac#11 0x080884db in do_main_loop () at main.c:1183
legacy/trac#12 0x080894a5 in tor_main (argc=0, argv=0x0) at main.c:2158
legacy/trac#13 0x080a5b9b in main (argc=0, argv=0x0) at tor_main.c:22
legacy/trac#14 0xb7d63974 in __libc_start_main () from /lib/tls/libc.so.6
legacy/trac#15 0x0804c571 in _start () at ../sysdeps/i386/elf/start.S:102
Last lines in the logfile:
# tail -n 3 log
Feb 12 23:57:40.103 [warn] spawn_enough_dnsworkers(): 100 DNS workers are spawned; all are busy. Killing one.
Feb 12 23:57:40.103 [warn] spawn_enough_dnsworkers(): 100 DNS workers are spawned; all are busy. Killing one.
Feb 12 23:57:40.105 [err] connection.c:257: connection_free: Assertion !connection_is_on_closeable_list(conn) failed; aborting.
wormhole:/var/log/tor# /usr/sbin/tor --version
Feb 13 18:58:17.225 [notice] Tor v0.1.1.26. This is experimental software. Do not rely on it for strong anonymity.
Tor version 0.1.1.26.
If you need any further evidences, drop me a line.
Cheers, Alex.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: yallahttps://gitlab.torproject.org/tpo/core/tor/-/issues/389Tor not connecting after installing Tor & Privoxy & Vidalia bundle: 0.1.2.7-a...2020-06-27T14:10:45ZTracTor not connecting after installing Tor & Privoxy & Vidalia bundle: 0.1.2.7-alphaWindows 98SE 4.10 (Build 2222 A)
IBM Aptiva - GenuineIntel Pentium(R) 200 MHz xA3 & mxA3
Tor & Privoxy & Vidalia bundle: 0.1.2.7-alpha
Using Tor as *Client only*.
After a clean install of the bundle, downloaded from:
http://tor.eff.org...Windows 98SE 4.10 (Build 2222 A)
IBM Aptiva - GenuineIntel Pentium(R) 200 MHz xA3 & mxA3
Tor & Privoxy & Vidalia bundle: 0.1.2.7-alpha
Using Tor as *Client only*.
After a clean install of the bundle, downloaded from:
http://tor.eff.org/dist/vidalia-bundles/vidalia-bundle-0.1.2.7-alpha-0.0.10.exe
and verified, Vidalia will not start Tor - correct locations of the Tor exe and torrc files verified, but Vidalia
settings "save" is corrupting location info. Privoxy operating correctly. Uninstalled Vidalia. Started Tor, which ran
for a few seconds, then closed - no info available. Edited torrc to send info to debug.log, restarted Tor.
Results below:
Feb 11 17:08:28.070 [notice] Tor 0.1.2.7-alpha opening new log file.
Feb 11 17:08:28.130 [debug] parse_dir_server_line(): Trusted dirserver at 18.244.0.188:9031 (46DB)
Feb 11 17:08:28.130 [debug] parse_dir_server_line(): Trusted dirserver at 18.244.0.114:80 (E45D)
Feb 11 17:08:28.130 [debug] parse_dir_server_line(): Trusted dirserver at 86.59.21.38:80 (1F85)
Feb 11 17:08:28.130 [debug] parse_dir_server_line(): Trusted dirserver at 140.247.60.64:80 (F5FC)
Feb 11 17:08:28.130 [debug] parse_dir_server_line(): Trusted dirserver at 194.109.206.212:80 (EAD6)
Feb 11 17:08:28.180 [info] or_state_load(): Loaded state from "C:\WINDOWS\Application Data\tor/state"
Feb 11 17:08:32.080 [warn] Could not open "C:\WINDOWS\Application Data\tor/cached-routers.new".
Feb 11 17:08:32.080 [info] update_router_have_minimum_dir_info(): We have 0 of 5 network statuses, and we want more
than 2.
Feb 11 17:08:32.080 [notice] I learned some more directory information, but not enough to build a circuit.
Feb 11 17:08:32.080 [info] update_router_descriptor_client_downloads(): Not enough networkstatus documents to launch
requests.
Feb 11 17:08:32.080 [info] update_router_descriptor_client_downloads(): Not enough networkstatus documents to launch
requests.
Feb 11 17:08:32.080 [info] update_networkstatus_client_downloads(): For 5/5 running directory servers, we have 0 live
network-status documents. Downloading 5.
Feb 11 17:08:32.080 [info] router_pick_directory_server(): No reachable router entries for dirservers. Trying them all
again.
Feb 11 17:08:32.080 [info] router_pick_directory_server(): Still no reachable router entries. Reloading and trying
again.
Feb 11 17:08:32.080 [warn] Could not open "C:\WINDOWS\Application Data\tor/cached-routers.new".
Feb 11 17:08:32.080 [info] directory_get_from_dirserver(): No router found for network status; falling back to dirserver
list
Feb 11 17:08:32.080 [debug] directory_initiate_command(): private 0, want_to_tunnel 0.
Feb 11 17:08:32.080 [debug] directory_initiate_command(): initiating network-status fetch
Feb 11 17:08:32.080 [debug] connection_connect(): Connecting to [scrubbed]:80.
Feb 11 17:08:32.250 [debug] connection_connect(): Connection to [scrubbed]:80 in progress (sock 216).
Feb 11 17:08:32.250 [debug] connection_add(): new conn type Directory, socket 216, n_conns 3.
Feb 11 17:08:32.250 [debug] write_to_buf(): added 4 bytes to buf (now 4 total).
Feb 11 17:08:32.250 [debug] write_to_buf(): added 221 bytes to buf (now 225 total).
Feb 11 17:08:32.250 [debug] write_to_buf(): added 33 bytes to buf (now 258 total).
Feb 11 17:08:32.250 [info] update_router_have_minimum_dir_info(): We have 0 of 5 network statuses, and we want more
than 2.
Feb 11 17:08:32.580 [info] or_state_save(): Saved state to "C:\WINDOWS\Application Data\tor/state"
Feb 11 17:08:32.580 [err] nt_service_loadlibrary(): Couldn't find ChangeServiceConfig2A in advapi32.dll! We probably
got the name wrong.
Feb 11 17:08:32.740 [info] or_state_save(): Saved state to "C:\WINDOWS\Application Data\tor/state"
Feb 11 17:08:32.740 [debug] _connection_free(): closing fd 44.
Feb 11 17:08:32.740 [debug] _connection_free(): closing fd 48.
Feb 11 17:08:32.740 [debug] _connection_free(): closing fd 216.
Completely uninstalled everything, re-downloaded bundle, and did clean install, this time de-selecting Vidalia & just
installing Tor and Privoxy. Same results repeated. Searched entire drive for "cached-routers.new" - unable to locate.
Checked properties for "ADVAPI32.dll" - File version 4.80.1675, Win32 ADVAPI32 core component, Copyright (C) Microsoft
Corp. 1991-1998, File size 64Kb, installed 4/23/99 with original installation of Windows 98 OS, apparently *not* revised
during the upgrade to Windows 98SE. I have NEVER had Windows NT - which Tor seems to be wanting -
"[err] nt_service_loadlibrary():"
Here is my torrc file, which the bundle installed in C:\WINDOWS\Application Data\Tor (note the "Last updated 8 October
2006 for Tor 0.1.2.3-alpha.") :
## Configuration file for a typical Tor user
## Last updated 8 October 2006 for Tor 0.1.2.3-alpha.
## (May or may not work for older or newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See the man page, or http://tor.eff.org/tor-manual-cvs.html, for more
## options you can use in this file.
##
## On Unix, Tor will look for this file in someplace like "~/.tor/torrc" or
## "/etc/torrc"
##
## On Windows, Tor will look for the configuration file in someplace like
## "Application Data\tor\torrc" or "Application Data\<username>\tor\torrc"
##
## With the default Mac OS X installer, Tor will look in ~/.tor/torrc or
## /Library/Tor/torrc
## Replace this with "SocksPort 0" if you plan to run Tor only as a
## server, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
#SocksListenAddress 192.168.0.1:9100 # listen on this IP:port also
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests from SocksListenAddress.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to C:\Documents and Settings\Application Data\Tor\notices.log
#Log notice file C:\Documents and Settings\Application Data\Tor\notices.log
## Send every possible message to C:\Documents and Settings\Application Data\Tor\debug.log
Log debug file C:\Program Files\Tor\debug.log
## Use the system log instead of Tor's logfiles
#Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
#RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
#DataDirectory @LOCALSTATEDIR@/lib/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
ControlPort 9051
############### This section is just for location-hidden services ###
## Once you have configured a hidden service, you can look at the
## contents of the file ".../hidden_service/hostname" for the address
## to tell people.
##
## HiddenServicePort x y:z says to redirect requests on port x to the
## address y:z.
#HiddenServiceDir C:\Documents and Settings\Application Data\Tor\hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir C:\Documents and Settings\Application Data\Tor\other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
################ This section is just for servers #####################
## NOTE: If you enable these, you should consider mailing the contents
## of the "fingerprint" file to the tor-ops, so nobody else can pick
## your nickname and use a different key. See
## http://tor.eff.org/docs/tor-doc-server.html for details.
## Required: A unique handle for your server.
#Nickname ididnteditheconfig
## The IP or FQDN for your server. Leave commented out and Tor will guess.
#Address noname.example.com
## Define these to limit your bandwidth usage. Note that BandwidthRate
## must be at least 20 KB.
#BandwidthRate 100 KB # Throttle traffic to 100KB/s (800Kbps)
#BandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## Contact info to be published in the directory, so we can contact you
## if your server is misconfigured or something else goes wrong.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com>
## Required: what port to advertise for Tor connections.
#ORPort 9001
## If you want to listen on a port other than the one advertised
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment the
## line below too. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORListenAddress 0.0.0.0:9090
## Uncomment this to mirror the directory for others. Please do
## if you have enough bandwidth: see the bottom of
## http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised
## in DirPort (e.g. to advertise 80 but bind to 9091), uncomment the line
## below too. You'll need to do ipchains or other port forwarding yourself
## to make this work.
#DirListenAddress 0.0.0.0:9091
## Uncomment this if you run more than one Tor server, and add the
## nickname of each Tor server you control, even if they're on different
## networks. You declare it here so Tor clients can avoid using more than
## one of your servers in a single circuit.
#MyFamily nickname1,nickname2,...
## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## available in the man page or at http://tor.eff.org/documentation.html
##
## Look at http://tor.eff.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # no exits allowed
What do I need to do to correct the "Could not open "C:\WINDOWS\Application Data\tor/cached-routers.new" and "Couldn't
find ChangeServiceConfig2A in advapi32.dll! We probably got the name wrong." problems??? Also, do I need to edit my
torrc file in some other way to operate correctly?
I previously ran an old Tor/TorCP/Privoxy bundle (don't remember the version #'s), which worked fine on my system, but
uninstalled everything and deleted the old bundle file before installing this new bundle, and now cannot find the older
bundle online. Any help would be appreciated.
kc9718
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: kc9718https://gitlab.torproject.org/tpo/core/tor/-/issues/388tor crashes after 6 hours2020-06-27T14:10:45ZTractor crashes after 6 hourstor crashes with this error after about 6 hours
using redhat 3.
Feb 07 19:45:06.358 [warn] connection_watch_events(): Error from libevent setting read event state for 1023 to watched: No such file or directory
Feb 07 19:45:06.373 [wa...tor crashes with this error after about 6 hours
using redhat 3.
Feb 07 19:45:06.358 [warn] connection_watch_events(): Error from libevent setting read event state for 1023 to watched: No such file or directory
Feb 07 19:45:06.373 [warn] connection_watch_events(): Error from libevent setting read event state for 1023 to watched: No such file or directory
Feb 07 19:45:13.787 [warn] connection_unregister(): Error removing read event for 1023
Feb 07 19:45:13.787 [warn] connection_unregister(): Error removing write event for 1023
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: mcncyoAndrew LewmanAndrew Lewmanhttps://gitlab.torproject.org/tpo/core/tor/-/issues/386Assertion circ->state == CIRCUIT_STATE_OR_WAIT failed2020-06-27T14:10:45Zweasel (Peter Palfrader)Assertion circ->state == CIRCUIT_STATE_OR_WAIT failedFeb 04 21:06:56.621 [err] circuitbuild.c:461: circuit_n_conn_done: Assertion circ->state == CIRCUIT_STATE_OR_WAIT failed; aborting.
(gdb) bt
#0 0x7026f1d0 in kill () from /lib/libc.so.6
#1 0x701b430c in pthread_kill () from /lib/libpt...Feb 04 21:06:56.621 [err] circuitbuild.c:461: circuit_n_conn_done: Assertion circ->state == CIRCUIT_STATE_OR_WAIT failed; aborting.
(gdb) bt
#0 0x7026f1d0 in kill () from /lib/libc.so.6
#1 0x701b430c in pthread_kill () from /lib/libpthread.so.0
legacy/trac#2 0x701b465c in raise () from /lib/libpthread.so.0
legacy/trac#3 0x7026eeac in raise () from /lib/libc.so.6
legacy/trac#4 0x70270354 in abort () from /lib/libc.so.6
legacy/trac#5 0x00017a14 in circuit_n_conn_done (or_conn=0x4ddbb8, status=0) at circuitbuild.c:465
legacy/trac#6 0x0001fcdc in circuit_about_to_close_connection (conn=0x4ddbb8) at circuituse.c:522
legacy/trac#7 0x00049218 in connection_unlink (conn=0x0, remove=1) at main.c:208
legacy/trac#8 0x00049fa8 in conn_close_if_marked (i=1) at main.c:523
legacy/trac#9 0x00049cb4 in close_closeable_connections () at main.c:388
legacy/trac#10 0x0004af4c in second_elapsed_callback (fd=-1, args=0xbb000) at main.c:1024
legacy/trac#11 0x70226f84 in event_base_priority_init () from /usr/lib/libevent-1.1a.so.1
legacy/trac#12 0x70227240 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#13 0x0004b380 in do_main_loop () at main.c:1183
legacy/trac#14 0x0004c348 in tor_main (argc=774536, argv=0xeffffa74) at main.c:2158
legacy/trac#15 0x70258e44 in __libc_start_main () from /lib/libc.so.6
legacy/trac#16 0x00013af4 in _start () at ../sysdeps/sparc/sparc32/elf/start.S:56
legacy/trac#17 0x00013af4 in _start () at ../sysdeps/sparc/sparc32/elf/start.S:56
Previous frame identical to this frame (corrupt stack?)
legacy/trac#5 0x00017a14 in circuit_n_conn_done (or_conn=0x4ddbb8, status=0) at circuitbuild.c:465
(gdb) p *or_conn
$1 = {magic = 2084319310, type = 4 '\004', state = 5 '\005', purpose = 0 '\0', wants_to_read = 0,
wants_to_write = 0, hold_open_until_flushed = 1, has_sent_end = 0, control_events_are_extended = 0,
is_obsolete = 1, s = 15, poll_index = 6, read_event = 0x484de0, write_event = 0x56aec8, inbuf = 0xde310,
inbuf_reached_eof = 0, timestamp_lastread = 1170623215, outbuf = 0x372890, outbuf_flushlen = 0,
timestamp_lastwritten = 1170623216, timestamp_created = 1170621095, timestamp_lastempty = 1170623216,
addr = 2551048465, port = 9001, marked_for_close = 688, marked_for_close_file = 0x8b288 "main.c",
address = 0x5ed250 "152.13.233.17", identity_pkey = 0x730058,
identity_digest = "ùg!^|æµ\205ø\f\236\216§ÖÈJ\023Æ)»b", nickname = 0x23def0 "WeAreAHedge",
chosen_exit_name = 0x0, tls = 0x7f25f8, bandwidth = 1024000, receiver_bucket = 1024000,
circ_id_type = CIRC_ID_TYPE_HIGHER, n_circuits = 0, next_with_same_id = 0x8767e0, next_circ_id = 19039,
stream_id = 0, next_stream = 0x0, cpath_layer = 0x0, package_window = 0, deliver_window = 0,
requested_resource = 0x0, socks_request = 0x0, global_identifier = 250042, event_mask = 0,
incoming_cmd_len = 0, incoming_cmd_cur_len = 0, incoming_cmd = 0x0, on_circuit = 0x0,
rend_query = '\0' <repeats 16 times>, incoming_cmd_type = 0}
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/385assert errors on answering begin_dir2020-06-27T14:10:45ZRoger Dingledineassert errors on answering begin_dirI think this was SVN r9422.
moria1 and moria2 both died with:
Jan 30 20:44:41.536 [err] connection.c:2380: assert_connection_ok: Assertion con
nection_is_writing(conn) || conn->wants_to_write failed; aborting.
#0 0x0000002a95e43545 i...I think this was SVN r9422.
moria1 and moria2 both died with:
Jan 30 20:44:41.536 [err] connection.c:2380: assert_connection_ok: Assertion con
nection_is_writing(conn) || conn->wants_to_write failed; aborting.
#0 0x0000002a95e43545 in raise () from /lib/libc.so.6
#1 0x0000002a95e44cce in abort () from /lib/libc.so.6
legacy/trac#2 0x0000000000420834 in assert_connection_ok (conn=0x1819230, now=19842)
at connection.c:2524
legacy/trac#3 0x0000000000440e7b in conn_read_callback (fd=19842, event=19842, _conn=0x6)
at main.c:424
legacy/trac#4 0x0000002a95d0e82d in event_base_priority_init ()
from /usr/lib/libevent-1.1a.so.1
legacy/trac#5 0x0000002a95d0ea72 in event_base_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#6 0x0000002a95d0e8e5 in event_loop () from /usr/lib/libevent-1.1a.so.1
legacy/trac#7 0x0000002a95d0e84b in event_dispatch () from /usr/lib/libevent-1.1a.so.1
legacy/trac#8 0x000000000044259b in do_main_loop () at main.c:1234
legacy/trac#9 0x000000000044323a in tor_main (argc=19842, argv=0x4d82) at main.c:2344
legacy/trac#10 0x0000002a95e31441 in __libc_start_main () from /lib/libc.so.6
legacy/trac#11 0x000000000040622a in _start () at ../sysdeps/x86_64/elf/start.S:96
$7 = {magic = 2575892462, type = 9 '\t', state = 6 '\006', purpose = 9 '\t',
wants_to_read = 0, wants_to_write = 0, hold_open_until_flushed = 0,
inbuf_reached_eof = 0, edge_has_sent_end = 0, or_is_obsolete = 0,
chosen_exit_optional = 0, s = 1503, conn_array_index = 1977,
read_event = 0x6b1feb0, write_event = 0x3230750, inbuf = 0x6a188a0,
outbuf = 0x14e3670, outbuf_flushlen = 141, timestamp_lastread = 1170207881,
timestamp_lastwritten = 1170207879, timestamp_created = 1170207879,
addr = <smudge>, port = 0, marked_for_close = 0,
marked_for_close_file = 0x0, address = 0x6f3880 "Tor network"}
Check out the "address" field -- I think that's our hint. Somewhere we're
making it stop writing but the assert doesn't take this into account.
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/382IPs are shown in logfile2020-06-27T14:10:46ZTracIPs are shown in logfileHi,
first: This bug occurs in 0.1.2.6-alpha.
The bug:
With the log option "notice" the following messages appear in the logfile often:
--snip--
... [warn] Other side (x.x.x.x:443) has a cert without a valid nickname. Closing.
... [warn...Hi,
first: This bug occurs in 0.1.2.6-alpha.
The bug:
With the log option "notice" the following messages appear in the logfile often:
--snip--
... [warn] Other side (x.x.x.x:443) has a cert without a valid nickname. Closing.
... [warn] Identity key not as expected for router at x.x.x.x:9001: wanted ....
---snap-
where x.x.x.x is a clearly visible IP which was masked by me in this note.
Regards,
Joerg
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: MaschiNick MathewsonNick Mathewson