[tor-bugs] #18141 [meek]: Tame "reading from ORPort" error logs in meek-server

[Tor Bug Tracker & Wiki]

#18141: Tame "reading from ORPort" error logs in meek-server
-----------------------------+-----------------
     Reporter:  dcf          |      Owner:  dcf
         Type:  enhancement  |     Status:  new
     Priority:  Medium       |  Milestone:
    Component:  meek         |    Version:
     Severity:  Normal       |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |    Sponsor:
-----------------------------+-----------------
 meek-server operators have asked to disable this error message:
 {{{
 reading from ORPort: read tcp 127.0.0.1:YYYY->127.0.0.1:ZZZZ: read:
 connection reset by peer
 }}}

 It occurs whenever tor closes the TCP connection between meek-server and
 itself. This happens very frequently when you restart the meek-server
 process, because it loses its cache of current session-IDs. When clients
 connect using their formerly valid session-IDs, meek-server treats them as
 new connections and opens new ORPort connections. The clients push TLS
 application data over the new connection, which doesn't match what tor
 expects from a new connection, so it shuts it down. Right after restarting
 you get a ton of these messages for a while (can be more than 10 per
 second).

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