Re: Client receiving Net::write error: could not reestablish connection.
Paul Keusemann <[email protected]> Wed, 29 Jul 2015 07:44:07 -0500
| Newsgroups | gmane.comp.distributed-net.proxyper |
|---|---|
| Message-ID | <[email protected]> |
On 07/14/15 10:19, Steven Nikkel wrote: > The error messages aren't very informative, but I'm guessing the > upstream has run out of work and thus is closing the connection that > is requesting work. Unfortunately it looks like it's an unclean > negotiation. > > ref > http://blogs.distributed.net/2015/07/10/04/28/bovine/ > Well, I'm not sure what was going on but as of yesterday afternoon, it is working again. I know the keymaster started working again on the 22, so I'm not sure that was the cause of this but I'm not sure I care enough at this point to try to chase it down. Paul > --- > Steven Nikkel > steven_nikkel-WeBCG/[email protected] > > On 2015-07-14 10:13 am, Paul Keusemann wrote: >> Hello, >> >> I am running the Personal Proxy (build 347) on a FreeBSD >> (10.1-RELEASE-p14) machine with clients on Solaris and Windows. The >> Solaris client started getting the following error messages a while >> back and I've finally got around to investigating: >> >> [Jul 14 14:24:09 UTC] Connected to woodstock.<domain>:2064... >> [Jul 14 14:24:09 UTC] The perproxy says: "woodstock Distributed.Net >> Personal >> Proxy!" >> [Jul 14 14:24:09 UTC] Retrieved project state data from server. >> (cached) >> [Jul 14 14:24:09 UTC] Net::write error: could not reestablish >> connection. >> [Jul 14 14:24:10 UTC] FetchOGR-NG:: Unable to send request (-1.168). >> [Jul 14 14:24:14 UTC] Net::write error: could not reestablish >> connection. >> [Jul 14 14:24:14 UTC] FetchRC5-72:: Unable to send request (-1.168). >> [Jul 14 14:24:15 UTC] Net::write error: could not reestablish >> connection. >> [Jul 14 14:24:15 UTC] FlushRC5-72::Unable to send packet (-1.168). >> [Jul 14 14:24:17 UTC] Network update is currently not available. >> >> Like I said, it's been a while since this started but if I remember >> correctly, there were no updates that precipitated this problem. >> >> Any ideas what might be going on here? >> >> Paul >> >> -- >> Paul Keusemann [email protected] >> 4266 Joppa Court (952) 894-7805 >> Savage, MN 55378 >> >> >> _______________________________________________ >> proxyper mailing list >> proxyper-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] >> http://lists.distributed.net/mailman/listinfo/proxyper > _______________________________________________ > proxyper mailing list > proxyper-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] > http://lists.distributed.net/mailman/listinfo/proxyper > -- Paul Keusemann [email protected] 4266 Joppa Court (952) 894-7805 Savage, MN 55378 _______________________________________________ proxyper mailing list proxyper-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected] http://lists.distributed.net/mailman/listinfo/proxyper