| raw e-mail | index | archive | help
I see similar traces on my other box where monerod has never given me probl= ems, but the traces become more far more common on the box that does give me problems once the sonewconn errors start appearing. The sonewconn errors ha= ve never appeared on the other working box. It seems monerod is mostly or entirely unable to continue syncing the block chain with constant stacktraces once it gets to this point unless I complet= ely reboot the system. Completely stopping and starting monerod doesn't help. Looking at sockstat -c the last time I was in this state, I only had a bit = over 200 connections. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>