Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T13:57:37Zhttps://gitlab.torproject.org/legacy/trac/-/issues/4030.1.2.x warns about non-named servers out of the blue2020-06-13T13:57:37ZRoger 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/legacy/trac/-/issues/404seg fault on 0.1.2.9-rc dir authority2020-06-13T13:57:38ZRoger 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/legacy/trac/-/issues/409Tor doesn't treat 0 as a valid port2020-06-13T13:57:41ZTracTor 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/legacy/trac/-/issues/412Tor v0.1.2.12-rc segfaults after a while2020-06-13T13:57:46ZTracTor 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
#2 0x28108450 in ?? ()
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: Orumhttps://gitlab.torproject.org/legacy/trac/-/issues/407Unable to mmap new descriptor file2020-06-13T13:57:41ZTracUnable 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**: Raindog