[tor-bugs] #22212 [Core Tor/Tor]: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel padding timeout scheduled 164729ms in the past. Did the monotonic clock just jump?

[Tor Bug Tracker & Wiki]

#22212: [warn] channelpadding_compute_time_until_pad_for_netflow(): Bug: Channel
padding timeout scheduled 164729ms in the past. Did the monotonic clock
just jump?
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:  mikeperry
     Type:  defect        |         Status:  reopened
 Priority:  Medium        |      Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |        Version:  Tor: 0.3.1.1-alpha
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by toralf):

 I added a 2nd Tor exit relay to my machine, listening on ports 9001 and
 9030, ipv4 and ipv4.
 The new is 6EABEBF38CE7E3DF672C4DB01383606FE3EB2215  (the old is
 1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA)
 Started after rebooting the machine at the same time, both notice logs are
 nearly identical, except now for the message seen below of the old,
 matured exit relay. I got few minutes ago :
 {{{
 Aug 26 10:27:48.000 [notice] Received reload signal (hup). Reloading
 config and resetting internal state.
 Aug 26 10:27:48.000 [notice] Read configuration file "/etc/tor/torrc".
 Aug 26 10:27:48.000 [notice] Tor 0.3.1.5-alpha (git-83389502ee631465)
 opening log file.
 Aug 26 10:27:49.000 [notice] Channel padding timeout scheduled 231988ms in
 the past.
 }}}
 The new exit (just few days old) didn't show this behavior.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22212#comment:21>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online