Opened 4 years ago

Closed 4 years ago

#21187 closed defect (duplicate)

[warn] connection_edge_process_relay_cell (at origin) failed.

Reported by: Betaman2k Owned by:
Priority: Medium Milestone: Tor: 0.2.9.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi

Specs and Infos:

[notice] Tor 0.2.9.8 (git-a0df013ea241b026) opening new log file.
[notice] Interrupt: exiting cleanly.
[notice] Tor 0.2.9.8 (git-a0df013ea241b026) opening log file.
[notice] Tor 0.2.9.8 (git-a0df013ea241b026) running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t and Zlib 1.2.8.
[notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
[notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
[notice] Read configuration file "/etc/tor/torrc".
[notice] Opening Socks listener on 127.0.0.1:9050
[notice] Bootstrapped 0%: Starting
[notice] Bootstrapped 80%: Connecting to the Tor network
[notice] Signaled readiness to systemd
[notice] Opening Control listener on /var/run/tor/control
[notice] Bootstrapped 85%: Finishing handshake with first hop
[notice] Bootstrapped 90%: Establishing a Tor circuit
[notice] Tor has successfully opened a circuit. Looks like client functionality is working.
[notice] Bootstrapped 100%: Done

Spam my logs with the warnings: [warn] connection_edge_process_relay_cell (at origin) failed.

Second problems: Randowm uptime time for my hidden service ( only restart help )

When using the latest "stable" version, tor "wedged" and become unable to connect to a hidden service. For each connection attempt, the log output printed "Rend stream is 120 seconds late. Giving up on address 'xxxxxxxxx.onion'". There was no other info in the log. Closing a restarting tor fixed the problem.

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by asn

Status: newneeds_information

Hello, thanks for the bug report. We probably need some more info to debug this. Is the hidden service definitely up? Can you visit it using a different Tor version?

comment:2 Changed 4 years ago by arma

The log part of this ticket looks like #16706.

And the second part looks like it can be summarized as "my onion service stopped being reachable by my client", which we know is an issue sometimes, and there isn't anything more in this ticket.

comment:3 in reply to:  2 Changed 4 years ago by arma

Replying to arma:

And the second part looks like it can be summarized as "my onion service stopped being reachable by my client", which we know is an issue sometimes, and there isn't anything more in this ticket.

Issue 2's symptoms are consistent with #21056?

comment:4 Changed 4 years ago by nickm

Resolution: duplicate
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.