Opened 4 weeks ago

Last modified 4 days ago

#32850 new defect

Channel padding timeout scheduled xxx ms in the past.

Reported by: computer_freak Owned by:
Priority: Medium Milestone: Tor: 0.4.3.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 041-backport 042-backport
Cc: mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

07:13:16 [NOTICE] Channel padding timeout scheduled 146141ms in the past.

I get them since months already on different relays. Minimum since 0.4.0.5. Maybe earlier.

Probably related to #22212#comment:48

Most of the time its only one message. Sometimes a few messages in a row at the same second like you can see it in #22212#comment:49 too.

Child Tickets

Change History (3)

comment:1 Changed 3 weeks ago by nickm

Cc: mikeperry added
Keywords: 041-backport 042-backport added
Milestone: Tor: 0.4.3.x-final

What operating system is this on?

comment:2 Changed 3 weeks ago by computer_freak

The relay where it happened today

95C8B9418E74F3FF80E5C3D3AF7F03156FFBBFBE

is on Debian 10.2

Some of my relays are still on Debian 9 and one is on Ubuntu but i can not tell right now if its happening on them too.

comment:3 Changed 4 days ago by computer_freak

Today on Debian Buster:

Jan 16 14:16:31.000 [notice] DoS mitigation since startup: 6 circuits killed with too many cells. 791720 circuits rejected, 50 marked addresses. 5929 connections closed. 328 single hop clients refused.
Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 166050ms in the past.
Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 165494ms in the past.
Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 171789ms in the past.
Jan 16 15:51:19.000 [notice] Channel padding timeout scheduled 172075ms in the past.
Jan 16 15:51:20.000 [notice] Channel padding timeout scheduled 173860ms in the past.
Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 175097ms in the past.
Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 173369ms in the past.
Jan 16 15:51:21.000 [notice] Channel padding timeout scheduled 173829ms in the past.
Jan 16 17:23:16.000 [notice] New control connection opened.
Note: See TracTickets for help on using tickets.