TLS errors

[Csaba Kiraly]

Hi,
As far as I can tell (I'm not a developer) the error message you see  is 
normal behavior, just logged in a way that scares people ;)
Of course it can also be something else, but you can find a possible 
explanation in my previous mail in the "no traffic?" thread:
http://archives.seul.org/or/talk/Nov-2007/msg00038.html

The cause is a housekeeping operation at the other side, which tears 
down your connection, but for some reason the TLS session is not closed 
nicely.
Messages in the two logs should be similar to the following (say "auth1" 
is your machine, "auth2" is the other node):

auth2   Nov 06 13:18:50.660 [info] run_connection_housekeeping(): 
Marking duplicate conn to 193.168.2.1:34066 obsolete (fd 16, 140 secs old).
auth2   Nov 06 13:18:50.660 [info] run_connection_housekeeping(): 
Expiring non-used OR connection to fd 16 (193.168.2.1:34066) [Obsolete].
auth1   Nov 06 13:18:50.661 [info] connection_read_to_buf(): tls error. 
breaking (nickname auth2, address 193.168.2.2).

This does not justify bandwidth problems, so you might have to look for 
some other reason as well ....
Csaba

Alexander W. Janssen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hans Schnehl wrote:
>   
>> Hi,
>>     
>
> Hi!
>
>   
>> Jan 02 12:46:06.204 [debug] TLS error: <syscall error while reading>
>> (errno=54: Connection reset by peer) Jan 02 12:46:06.204 [info]
>> connection_read_to_buf(): tls error [connection reset]. breaking
>> (nickname NoNickNode, address 111.112.113.114).
>>     
>
> It looks like one of the nodes you have a connection too just kicked you
> out for some reason ("connection reset by peer"). This is pretty normal.
> Could be the remote node shutting down the software, rebooting and such.
>
>   
>> Jan 02 12:46:14.711 [debug] crypto error while performing RSA
>> decryption: oaep decoding error (in rsa
>> routines:RSA_padding_check_PKCS1_OAEP)
>>     
>
> Not sure about those, but it could be consecutive errors resulting from
> the encrypted connection (TLS) being shut down.
>
>   
>> Tor is running, but appears to be using only fractions of the
>> bandwidth it is supposed to. Can someone please give a short
>> explanation?
>>     
>
> No idea about that though. But it usually takes some time until everyone
> learned about your node - from my experience it takes up to 24 hours
> until the bandwidth is fully utilized.
>
> I'm just guessing from my generic experience :)
>
>   
>> Hans
>>     
>
> Alex.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
>
> iQCVAwUBR3uQZBYlVVSQ3uFxAQK9BwP+Ir5XUmyxYPttIdC6u3K/B/0Zyf8zE5p1
> 7Xm7xm43gNlGRG5ypimO/rhsaA2Lb9AegTbWKjGcxQo2ysn9RwrXMOAq4BNf3U1J
> kXY/xPEydo9UdMtT6+E4UZii1NbKYvDGAyU6IsiB8cYX9LyO+r0c+qrg5CIaZTta
> i99biZT6/G0=
> =JAjN
> -----END PGP SIGNATURE-----
>