Opened 10 years ago

Closed 2 years ago

#1121 closed defect (fixed)

reason unexpected while uploading descriptor

Reported by: dragonfly Owned by:
Priority: Medium Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Tor Version: 0.2.2.3-alpha
Severity: Normal Keywords: easy tor-relay
Cc: dragonfly, karsten, nickm Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description (last modified by arma)

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]

Child Tickets

Change History (14)

comment:1 Changed 10 years ago by dragonfly

Just FYI, getting more of the 404.

Oct 12 20:53:13.412 [warn] Received http status code 404 ("Not Found") from server '194.109.206.212:80' while fetching "/tor/status/all.z". I'll try again soon.
Oct 13 09:54:04.911 [warn] http status 404 ("Not Found") reason unexpected while uploading descriptor to server '194.109.206.212:80').

comment:2 Changed 9 years ago by nickm

Milestone: Tor: 0.2.2.x-final

This should be a better error message, especially on the uploading case. I have no idea why dizum might have been saying this, though. Do we have records as to whether dizum was having intermittent problems at the time?

My guess is that dizum was behind some kind of http proxy, and down at the time. Otherwise there's no reason it should have been saying 404 here.

For now, given that dizum is working, the best we can do is probably try to improve the warning message.

comment:3 Changed 9 years ago by arma

Description: modified (diff)

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 ..."?

comment:4 Changed 9 years ago by nickm

Keywords: easy added

Marking as "easy", since this is mainly a matter of figuring out what went wrong on a directory operation in a more useful way, and giving a friendlier error message.

comment:5 Changed 9 years ago by arma

Triage: no need for this to block 0.2.2.x

comment:6 Changed 9 years ago by arma

Perhaps we can know to blame the directory server if we're using a begindir connection? Heck, in some cases we could even make this an info-level log if it's begindir and the directory interaction isn't critical-path.

If we're not using a begindir connection, it could be a problem with the local connection intercepting http requests, so it probably wants some sort of log still. I don't know what it should say that would explain it in 10 words to an ordinary user though. Too many possible things that could have gone wrong.

comment:7 Changed 9 years ago by arma

This probably *wasn't* a begindir connection though, right, because dizum wouldn't send it through its apache if it's already inside Tor. It would just make a linked conn.

comment:8 Changed 8 years ago by arma

Owner: set to arma
Priority: minormajor
Status: newassigned

comment:9 Changed 8 years ago by arma

Owner: arma deleted

I no longer know why I assigned this one to myself. I don't have any particular feelings on what log messages would explain things better. There are still a wide variety of things that could have gone wrong, and it's hard for Tor to tell which one happened.

comment:10 Changed 8 years ago by nickm

Milestone: Tor: 0.2.2.x-finalTor: unspecified
Priority: majornormal

Tossing this into "Tor: unspecified". It would be great if somebody worked on making this message better, but atm there seems to be no plan and not much urgency.

comment:11 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:12 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:13 Changed 3 years ago by nickm

Cc: dragonfly,karsten,nickmdragonfly, karsten, nickm
Points: small
Severity: Normal

comment:14 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.1.x-final
Resolution: Nonefixed
Status: assignedclosed

Tried to clean up this message a bit with b80a35e683d636

Note: See TracTickets for help on using tickets.