[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: TLS errors



-----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-----