Opened 11 years ago

Last modified 7 years ago

#912 closed defect (Not a bug)

Tor says "data cell dropped, unknown stream", no furter usage of Tor possible

Reported by: knappo Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: 0.2.1.10-alpha
Severity: Keywords:
Cc: knappo, nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It is the third time this happens to me on this computer.

Tor was running all smooth on the computer, but today I am not able to connect to any website through Tor.
It looks pretty normal and Firefox already shows the favicon when out of nowhere Firefox acts
like someone pressed the reload button. The connection to the site is halted and then Firefox tries to reconnect.
This happens before the page content is rendered in the browser so I don't know how much data was already processed
till the reconnection happens.
At the same time this "reconnect" happens, the Tor log says:
[Info] connection_edge_process_relay_cell(): data cell dropped, unknown stream.
(about 30 times in a row on [Info] verbosity.

I've attached 2 logs. One at [Info] and one at [Debug]. In both cases, Tor was started through Vidalia.
After the onion went green (Tor was connected) I waited some seconds and tried to open blog.fefe.de in
Firefox (Fefes Blog was chosen because it consists of one large html page without pictures - beside the favicon).

Last time this problem occurred I had to do a clean reinstall of the Vidalia Bundle to make it disappear.
The problem occurred with different versions of the 2.1.x branch.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Attachments (4)

tor-log-info.zip (5.9 KB) - added by knappo 11 years ago.
Tor log on [Info] verbosity
tor-log-debug.zip (71.0 KB) - added by knappo 11 years ago.
Tor log on [Debug] verbosity
tor-log-info-wo-pipelining.zip (8.7 KB) - added by knappo 11 years ago.
Tor log on [Info] verbosity, this time without http-pipelining. The website request starts 00:44:32
tor-log-debug-wo-pipelining.zip (98.8 KB) - added by knappo 11 years ago.
[Debug] verbosity, no http-pipelining, website request starts ~00:58:39

Download all attachments as: .zip

Change History (11)

Changed 11 years ago by knappo

Attachment: tor-log-info.zip added

Tor log on [Info] verbosity

Changed 11 years ago by knappo

Attachment: tor-log-debug.zip added

Tor log on [Debug] verbosity

comment:1 Changed 11 years ago by knappo

I thought this could be somehow connected to pipe lining, but disabling it does not make a difference.
Watching the Vidalia interface for connections (Network map) it shows, that the connections to the website
are getting closed before the site is loaded. Afterwards a new connection is made but then also closed.

The problem is not limited to a specific circuit but persistent.

comment:2 Changed 11 years ago by knappo

I've let it run for some time now.
It seems, that relay operation is not affected by this,
because the node has now incoming and outgoing traffic.

comment:3 Changed 11 years ago by arma

The pile of "data cell dropped, unknown stream" happens normally when you
make a connection, ask for a big web page or whatever, and then your
local application side hangs up. Tor then forgets about the request,
and then the big web page arrives (in a series of data cells followed by
an end cell). Your Tor drops each one because it's not expecting it.

Looking over your info-level log, it looks like you're opening a *lot*
of streams:
Jan 16 14:29:55.491 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:29:55.491 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:29:55.648 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:29:55.648 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:30:01.351 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 4 seconds.
Jan 16 14:30:01.351 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 4 seconds.
Jan 16 14:30:01.632 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 4 seconds.
Jan 16 14:30:01.632 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 4 seconds.
Jan 16 14:30:07.101 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:30:07.101 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:30:07.367 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:30:07.680 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 3 seconds.
Jan 16 14:30:15.836 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 5 seconds.
Jan 16 14:30:15.836 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 5 seconds.
Jan 16 14:30:15.836 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 5 seconds.
Jan 16 14:30:15.836 [Info] connection_edge_process_relay_cell_not_open(): 'connected' received after 5 seconds.

Notice how they come up batches of 4 connect requests each time. I'm not sure
what that tells us. Perhaps that your firefox is loading four pages each time?

Is this with privoxy? Polipo? Firefox straight to Tor?

Are you using Torbutton 1.2.0?

comment:4 Changed 11 years ago by knappo

First: This happens with Portable Firefox 2.0.0.20, Torbutton 1.2.0,

Vidalia 0.1.10 and Tor 0.2.1.10 and Privoxy 3.0.6

I've done another log, this time I've disabled any network tweaks in Firefox, this means especially, that no pipelining was active.

Changed 11 years ago by knappo

Tor log on [Info] verbosity, this time without http-pipelining. The website request starts 00:44:32

Changed 11 years ago by knappo

[Debug] verbosity, no http-pipelining, website request starts ~00:58:39

comment:5 Changed 11 years ago by knappo

It now seems to be, that this is a problem with my Firefox, as using a new installation has solved the problem.
I will try to investigate further and report if there is anything useful for Tor.

Sorry for wasting your time blaming Tor in the first place.

comment:6 Changed 11 years ago by nickm

flyspray2trac: bug closed.

comment:7 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.