[warn] channelpadding_ and [warn] assign_
Hi everybody On 3.1.3a there are quiet some log entries like 10 per day and relay, more cicuits - more entries: [warn] channelpadding_compute_time_until_pad_for_netflow: Bug: Channel padding timeout scheduled 212ms in the past. Did the monotonic clock just jump? (on Tor 0.3.1.3-alpha dc47d936d47ffc25) and [warn] assign_to_cpuworker failed. Ignoring. Seems without impact to performance. I just wonder. Switching to 3.1.4a might fix it ? 3.0.8 doesn't show it. [] Tor 0.3.1.3-alpha (git-dc47d936d47ffc25) running on FreeBSD with Libevent 2.1.8-stable, OpenSSL LibreSSL 2.4.3, Zlib 1.2.8, Liblzma 5.2.2, and Libzstd 1.2.0. -- Cheers, Felix
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/03/2017 09:58 PM, Felix wrote:
- -- Toralf PGP C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iI0EAREIADUWIQQaN2+ZSp0CbxPiTc/E6s3eAHbpTgUCWVqiwxccdG9yYWxmLmZv ZXJzdGVyQGdteC5kZQAKCRDE6s3eAHbpTqavAP9TMX3RPRH2thkxfHu6JE8HAreo ih3AIHefHcLhwfNP4AD9HromYZMykGvusiqfH7forOGap2cVyK342FDshgZ42JQ= =ZdBT -----END PGP SIGNATURE-----
On Mon, Jul 03, 2017 at 09:58:02PM +0200, Felix wrote:
https://bugs.torproject.org/22212
and
[warn] assign_to_cpuworker failed. Ignoring.
https://bugs.torproject.org/22356
Seems without impact to performance. I just wonder. Switching to 3.1.4a might fix it ?
The 0.3.1.4-alpha changelog lists both of these tickets. So, let us know if they continue once you've updated! --Roger
participants (3)
-
Felix -
Roger Dingledine -
Toralf Förster