[tor-bugs] Re: #1121 [Tor - Relay]: reason unexpected while uploading descriptor

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#1121: reason unexpected while uploading descriptor
--------------------------------+-------------------------------------------
 Reporter:  dragonfly           |         Type:  defect     
   Status:  new                 |     Priority:  minor      
Milestone:  Tor: 0.2.2.x-final  |    Component:  Tor - Relay
  Version:  0.2.2.3-alpha       |   Resolution:  None       
 Keywords:                      |       Parent:             
--------------------------------+-------------------------------------------

Old description:

> Hi,
>
> since i upgraded my relay to 0.2.2.5-alpha i am getting these warn
> message below.
>
> Oct 12 13:15:10.985 [notice] Bootstrapped 90%: Establishing a Tor
> circuit.
> Oct 12 13:15:18.207 [notice] Tor has successfully opened a circuit. Looks
> like client functionality is working.
> Oct 12 13:15:18.207 [notice] Bootstrapped 100%: Done.
> Oct 12 13:16:09.666 [warn] http status 404 ("Not Found") reason
> unexpected while uploading descriptor to server '194.109.206.212:80').
> Oct 12 13:16:17.277 [notice] Self-testing indicates your DirPort is
> reachable from the outside. Excellent.
> Oct 12 13:16:18.508 [notice] Performing bandwidth self-test...done.
> Oct 12 13:17:10.924 [warn] http status 404 ("Not Found") reason
> unexpected while uploading descriptor to server '194.109.206.212:80').
> Oct 12 13:23:16.169 [warn] http status 404 ("Not Found") reason
> unexpected while uploading descriptor to server '194.109.206.212:80').
>
> Some kind of new bug?
>
> [Automatically added by flyspray2trac: Operating System: Other Linux]

New description:

 Hi,

 since i upgraded my relay to 0.2.2.5-alpha i am getting these warn message
 below.

 Oct 12 13:15:10.985 [notice] Bootstrapped 90%: Establishing a Tor circuit.
 Oct 12 13:15:18.207 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Oct 12 13:15:18.207 [notice] Bootstrapped 100%: Done.
 Oct 12 13:16:09.666 [warn] http status 404 ("Not Found") reason unexpected
 while uploading descriptor to server '194.109.206.212:80').
 Oct 12 13:16:17.277 [notice] Self-testing indicates your DirPort is
 reachable from the outside. Excellent.
 Oct 12 13:16:18.508 [notice] Performing bandwidth self-test...done.
 Oct 12 13:17:10.924 [warn] http status 404 ("Not Found") reason unexpected
 while uploading descriptor to server '194.109.206.212:80').
 Oct 12 13:23:16.169 [warn] http status 404 ("Not Found") reason unexpected
 while uploading descriptor to server '194.109.206.212:80').

 Some kind of new bug?

 [Automatically added by flyspray2trac: Operating System: Other Linux]

--

Comment(by arma):

 Happy to think about improving the message. The problem here I assume was
 that dizum forwards its directory requests through apache, and Tor was
 down at the time so apache gave the error message.

 I guess we could have the Tor client try to explain better what's up.
 Often the problem is that the client is behind some sort of intercepting
 http proxy. We might special-case complaints that happen as we're trying
 to touch a directory authority. But it will still be unclear whether the
 problem is at the server side or the client side.

 Then again, if we're doing the fetch via begindir, we know the problem is
 at the server side. In that case, what better message can we provide?
 "Problem fetching directory information (404 Not found) from server ..."?

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