Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T15:42:25Zhttps://gitlab.torproject.org/legacy/trac/-/issues/30839Update EndOfLifeTor.md with our latest end of life process2020-06-13T15:42:25ZteorUpdate EndOfLifeTor.md with our latest end of life processThe draft is currently in:
https://github.com/torproject/tor/pull/1062/files
Once #28453 merges, I will update the document with:
* Update git scripts
* Update Tor Travis Cron Jobs instructions
* Jenkins test builds
* Jenkins deb builds...The draft is currently in:
https://github.com/torproject/tor/pull/1062/files
Once #28453 merges, I will update the document with:
* Update git scripts
* Update Tor Travis Cron Jobs instructions
* Jenkins test builds
* Jenkins deb builds, including nightlies and experimental-(latest release), which needs to have a successful build before:
* Debian website instructions, including JavaScript and no script lists
* Chutney Travis CI
* Stem Travis CI
* sbws Travis CI (the sbws CI does not use multiple tor versions yet, so add a ticket number)Tor: 0.4.4.x-finalteorteorhttps://gitlab.torproject.org/legacy/trac/-/issues/29645test.exe hangs on Appveyor CI2020-06-13T15:49:23Zteortest.exe hangs on Appveyor CITor's test.exe sometimes hangs on our Appveyor Windows CI.
I've seen this happen twice over the past few weeks.
Here is one example:
https://ci.appveyor.com/project/torproject/tor/builds/22791909/job/u0jd5tpr07mt2nv3
We've reduced the ...Tor's test.exe sometimes hangs on our Appveyor Windows CI.
I've seen this happen twice over the past few weeks.
Here is one example:
https://ci.appveyor.com/project/torproject/tor/builds/22791909/job/u0jd5tpr07mt2nv3
We've reduced the job time limit to 30 minutes to mitigate this issue.
But I am not sure how to debug it further.Tor: 0.4.4.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/29136PT_LOG and PT_STATUS event fields unspecifed2020-06-13T15:37:03ZDamian JohnsonPT_LOG and PT_STATUS event fields unspecifedRecently Tor added PT_LOG and PT_STATUS events to the spec...
https://gitweb.torproject.org/torspec.git/commit/?id=3028cf1
https://gitweb.torproject.org/torspec.git/commit/?id=b38257e
Unfortunately the 'pt-spec.txt section 3.3.5' secti...Recently Tor added PT_LOG and PT_STATUS events to the spec...
https://gitweb.torproject.org/torspec.git/commit/?id=3028cf1
https://gitweb.torproject.org/torspec.git/commit/?id=b38257e
Unfortunately the 'pt-spec.txt section 3.3.5' section they mention does not exist, and in looking around I can't find anything that describes what these event fields are defined as ('PT=' 'TYPE=', 'CONNECT=', etc).
I started to write a stem parser for these but can't continue until this is done (I can't parse events without knowing what fields they include).
David is aware of this and plans to has kindly offered to add the missing info...
```
22:24 <+atagar> dgoulet: Your control-spec addition to descript PT_LOG and PT_STATUS
cite a pt-spec section 3.3.4 which does not exist.
22:24 <+atagar> s/descript/describe
22:29 <+atagar> dgoulet: Huh. I'm not spotting anything that lists the keyword
arguments ('PT=' and 'SEVERITY=') so guess the sections simply
missing from the spec. I need that for stem support so please
give me a nudge when the event spec's done. :)
22:59 <+dgoulet> atagar: oh hmmm I'll fix that sorry
23:17 <+atagar> Thanks! Much appreciated. :)
```Tor: 0.4.4.x-finalDamian JohnsonDamian Johnsonhttps://gitlab.torproject.org/legacy/trac/-/issues/24857Tor uses 100% CPU when accessing the cache directory on Windows2020-06-13T15:51:45ZTracTor uses 100% CPU when accessing the cache directory on WindowsHi,
I have tor 0.3.1.9 running as non-exit relay.
From time to time it starts consuming 100% of CPU. Even though network traffic is minimal.
Is it normal? If not, how can I help you to investigate it?
My system is Win 7 x64 SP1, cpu i...Hi,
I have tor 0.3.1.9 running as non-exit relay.
From time to time it starts consuming 100% of CPU. Even though network traffic is minimal.
Is it normal? If not, how can I help you to investigate it?
My system is Win 7 x64 SP1, cpu is Core i5-3570.
**Trac**:
**Username**: Eugene646Tor: 0.4.4.x-finalAlexander Færøyahf@torproject.orgAlexander Færøyahf@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/16016extrainfo_insert(): Bug: No entry found in extrainfo map.2020-06-13T14:46:05ZRoger Dingledineextrainfo_insert(): Bug: No entry found in extrainfo map.I get these on moria1 pretty often. It's been ongoing for a long time I think -- since whenever we attempted to fix that last bug with ri / ei synchronization.
Here's a potentially useful info-level log:
```
May 13 18:50:37.600 [info] c...I get these on moria1 pretty often. It's been ongoing for a long time I think -- since whenever we attempted to fix that last bug with ri / ei synchronization.
Here's a potentially useful info-level log:
```
May 13 18:50:37.600 [info] connection_dir_client_reached_eof(): Received extra server info (size 5307) from server '131.188.40.189:80'
May 13 18:50:37.600 [info] router_load_extrainfo_from_string(): 3 elements to add
May 13 18:50:37.600 [warn] extrainfo_insert(): Bug: No entry found in extrainfo map. [1 similar message(s) suppressed in last 1800 seconds] (on Tor 0.2.7.1-alpha-dev 95a9920461dd3322)
May 13 18:50:37.623 [info] connection_dir_client_reached_eof(): Received 0/9 extra-info documents requested from 131.188.40.189:80
```
I don't know if this last line is related or not.
Actually, I get one of the Bug: messages every hour on moria1, a little bit after the 50 minute mark. Sounds like I'm hearing votes from other authorities, and they make me think of an extrainfo I don't have, so I try to get it, and then bug.Tor: 0.4.4.x-finalNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/legacy/trac/-/issues/5304Obfsproxy should respect OutboundBindAddress in torrc2020-06-13T14:17:58ZTracObfsproxy should respect OutboundBindAddress in torrcRather it just binds to * (any IP).
Tested with latest git obfsproxy and Tor 0.2.3.12-alpha.
**Trac**:
**Username**: korobkovRather it just binds to * (any IP).
Tested with latest git obfsproxy and Tor 0.2.3.12-alpha.
**Trac**:
**Username**: korobkovTor: 0.4.4.x-final