Read Error Eof From Client
QuakeNet's Rules Security S Trusts What do those quit messages mean? Excess flood This quit message shows that you attempted to send too much data to the IRC server, in too short a time period, and the server thought you were attempting to flood it. A good way to prevent this is to enable flood protection in your IRC client. mIRC users may click File -> Options -> IRC -> Flood, and then check Enable flood protection. The default values should be sufficient for most users. Max sendQ exceeded This quit message occurs when you failed to receive the data from the server quick enough, in other words the IRC server tried to send you too much data and closed the connection. This is often caused if you perform a LIST of all IRC channels on QuakeNet, or if you execute a WHO query on a large channel. If you have a poor internet connection you may find yourself getting disconnected with this reason. Ping timeout All IRC servers periodically send what is known as a PING request, to check that the client connection is still alive. The IRC client has to respond to this request within a certain time period, or the connection is deemed to no longer be alive and is closed (with this quit message). If you find yourself getting a lot of Ping timeout errors you may need to try a different (preferably closer) QuakeNet server; see here for a complete listing of public servers. Connection reset by peer This quit message is caused when the IRC client closes the connection to the server uncleanly, and the server doesn't realise the connection has been terminated. This leaves behind what is known as a ghost user, which gives the appearance that the client is still connected, even though it isn't. When the server attempts to send data to the client, it realises the connection no longer exists and it is reset. This causes the termination of the ghost user, with the aforementioned quit messsage. Read error: EOF from client
Forum List Active Topics Search Who's Online Help Topic Options #126678 - 03/08/05 10:39 AM Read Error: EOF from client Cheesehorse Self-satisified door Registered: 03/08/05 Posts: 4 I'm connecting to netgamers from behind a proxy, and have successfully configured mIRC with my proxy settings, hostname. passowrd etc.I can connect to my preffered network and chat with no issues. However, if I am innactive for a period of a 2 or 3 minutes I am disconnected with message '[me] has quit IRC (Read error: EOF from client)'.I've done a seach https://www.quakenet.org/help/general/what-do-those-quit-messages-mean of these forums and found a little info on this message, but it's happening consistently each time I'm innactive - any thoughts on possible solutions or work arounds?Your help is appreciated.C Top #126679 - 03/08/05 11:02 AM Re: Read Error: EOF from client Cheesehorse Self-satisified door Registered: 03/08/05 Posts: 4 As a thought, might it work to set an automated message to send to a channel every http://forums.mirc.com/ubbthreads.php/topics/126678/Read_Error:_EOF_from_client minute or so so I'm not innactive?Something like the script mentioned here:http://forums.mirc.com/s...true#Post133682 Top #126680 - 03/08/05 04:14 PM Re: Read Error: EOF from client IR_n00b Fjord artisan Registered: 01/10/04 Posts: 200 Loc: where i am. you could try:on *:connect:/timer 1 40 /quote ping $tickson *:pong: {var %time = $calc(($ticks - %time)/1000)set %ping.pong.lag. [ $+ [ $server ] $+ . $+ [ $network ] ] %time}menu status,channel {Server lag: [ %ping.pong.lag. [ $+ [ $server ] $+ . $+ [ $network ] ] ] MS:/echo -a Server lag: [ %ping.pong.lag. [ $+ [ $server ] $+ . $+ [ $network ] ] ] MS}---this snippet should keep you connected, and also telll you your approx. lagg to the server ^^, im not sure if the menubar will work tho. copy past this to your remotes, and right click on the stats/channel window and it should tell you. if you click on it, it will echo it to the window. Top #126681 - 03/08/05 08:45 PM Re: Read Error: EOF from client IR_n00b Fjord artisan Registered: 01/10/04 Posts: 200 Loc: where i am. *fix: replace $1 with $2 Top #126682 - 04/08/05 03:45 PM Re: Read Error: EOF from client Cheesehorse
* [Roy] has quit IRC (Read error: EOF from client) * Blue_Dark has quit read error eof IRC (Read error: EOF from client) * Blue_Dark has joined #RSR
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Google Go EOF on reading from connection using Read() up vote 0 down vote favorite I am trying to create a simple TCP server using the Google Go language. I have a client which points to 127.0.0.1:8484. When my server code tries to read the buffer I receive an EOF error on line 37. The client sends an initial tcp packet denoting its client version and other settings (the client is from a game therefore I know that I am doing something wrong). I am trying to read this packet. However, it seems I call the read too late and the client has already sent the packet and is waiting for its response. Any help would be appreciated, as I am truly stumped. package main import ( "fmt" "net" "os" ) func main() { service := ":8484" listener, err := net.Listen("tcp", service) checkError(err) fmt.Println("Login Server Started\nListening on port:", service[1:]) for { conn, err := listener.Accept() if err != nil { continue } go handleClient(conn) } } func handleClient(conn net.Conn) { const BUFFER_LENGTH = 1024 defer conn.Close() fmt.Println("Client connected from", conn.RemoteAddr()) var buf [BUFFER_LENGTH]byte for { n, err := conn.Read(buf[0:]) if err != nil { checkError(err) return } _, err2 := conn.Write(buf[0:n]) if err2 != nil { checkError(err) return } } } func checkEr