Opened 4 years ago

Closed 3 years ago

Last modified 3 years ago

#13973 closed defect (duplicate)

Old bug back or something is tampering HS?

Reported by: oneday Owned by:
Priority: Medium Milestone: Tor: 0.2.7.x-final
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Keywords: tor-hs, 027-triaged-1-in, research
Cc: asn Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor: SponsorR

Description

I'm getting a few dozens of same WARN on a SRV running an up to date debian & Tor to publish a Hidden Service: 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux.

WARN sample (/var/log/tor/log.2):

Dec 15 04:53:19.000 [warn] rend_service_introduce(): Bug: Internal error: Got an INTRODUCE2 cell on an intro circ (for service "……….") with no corresponding rend_intro_point_t.

The Hidden Service seems working fine, any suggestion about how to investigate about it?

Child Tickets

Change History (13)

comment:1 Changed 4 years ago by dgoulet

Cc: asn added
Keywords: tor-hs added; INTRODUCE2 rend_service_introduce rend_intro_point_t removed
Priority: criticalnormal

That's a duplicate of #8864 but on a more recent version (0.2.5). Priority set back to "normal". There might be a bug in the code that does not clean up something but the HS service is still working fine.

Can you change the log level to "debug" and attach that here to the ticket? Basically, once you see the [warn] rend_service_introduce(): Bug: Internal..., capture the log file and you can put back to normal debug your HS service. (make sure to scrub your HS service name if you don't want it there).

comment:2 Changed 4 years ago by oneday

ASN, done.
Waiting for some more logs.

Weird bug:

  • yesterday happened hundreds of time but related to 5 specific moments of the day
  • today happened a few dozens of time but in the same 2 minutes.

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

Replying to oneday:
In addition to debug logging, I suggest LogTimeGranularity 1 and LogMessageDomains 1.

Last edited 4 years ago by qwerty1 (previous) (diff)

comment:4 Changed 4 years ago by oneday

24h monitoring, nothing new till now.

comment:5 Changed 4 years ago by oneday

No news.
It's weird to see no more any entry of this after two long session, with no causality but with a regular and continuous iteration.

comment:6 Changed 4 years ago by hellais

I noticed a lot of tor log entries with this error message when running tor 0.2.5.8-rc.

Here is the log grepping for those lines: http://paste.debian.net/142106/

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-final

comment:8 Changed 4 years ago by nickm

Status: newassigned

comment:9 Changed 3 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:10 Changed 3 years ago by isabela

Keywords: SponsorR research added
Points: medium
Version: Tor: 0.2.5.10Tor: 0.2.7

comment:11 Changed 3 years ago by oneday

I got again hundreds of:

May 29 09:02:21.450 [warn] {BUG} rend_service_introduce(): Bug: Internal error: Got an INTRODUCE2 cell on an intro circ (for service "----------------") with no corresponding rend_intro_point_t.

Distributed during daytime, no more than 30 per hour.
Currently I'm using a:
Linux version 3.2.0-4-amd64 (debian-kernel@…) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.54-2
Fully updated, and tor:
Tor version 0.2.5.12 (git-3731dd5c3071dcba)

comment:12 Changed 3 years ago by s7r

Resolution: duplicate
Status: assignedclosed

comment:13 Changed 3 years ago by dgoulet

Keywords: SponsorR removed
Sponsor: SponsorR
Note: See TracTickets for help on using tickets.