Quote from Scawen : Who was trying to join the host? It looks like someone with a bad connection was trying to connect.
Well... Me
But I'm not the only one...
The log generates lots of errors from unique ip addresses;
Quote from deb.log :
Oct 23 17:51:11 TCP ERROR : WOULDBLOCK
Oct 23 17:51:21 Joiner Fatal Error
Oct 23 17:53:12 TCP ERROR : WOULDBLOCK
Oct 23 17:53:22 Joiner Fatal Error
Oct 23 17:59:31 TCP ERROR : WOULDBLOCK
Oct 23 17:59:42 Joiner Fatal Error
Oct 23 17:59:50 TCP ERROR : WOULDBLOCK
Oct 23 18:00:01 Joiner Fatal Error
Oct 23 18:10:49 TCP ERROR : WOULDBLOCK
Oct 23 18:11:00 Joiner Fatal Error
Oct 23 18: 13 :26 TCP ERROR : WOULDBLOCK
Oct 23 18: 13 :36 Joiner Fatal Error
Oct 23 18: 13 :41 TCP ERROR : WOULDBLOCK
Oct 23 18: 13 :50 Joiner Fatal Error
This list could go on forever. Are there really that many bad connections including my own? I doubt it.
The dedicated server runs LFS in a simulated environment though (Linux Wine) maybe thats causing a problem...
But it could also be a Vista / Windows 7 compatibility problem on the client end I guess. (I use Windows 7, without firewall nonsense).
What does the error WOULDBLOCK imply?
Quote : This error happens when the winsock buffer of either the client or server side become full.
Here are two situations in which you might see Winsock error 10035:
* You're trying to send a massive amount of information through the socket, so the output buffer of the system becomes full.
* You're trying to send data through the socket to the remotehost, but the remotehost input buffer is full (because its receiving data slower than you're sending it).
Thats great... But happends this problem on the host side or on the client side
---
* actually this has nothing to do with Z21, had same issues with Z13 ..
I did some forum research and its quite an irritation for some people replacing complete routers, computers and operating systems.
Last edited by nl2dav, Fri, 23 Oct 2009 16:51 .