Read Error From Server Broken Pipe
Help installing ANOPE « previous next » Pages: [1] Go Down Print Author Topic: Help installing ANOPE (Read 8139 times) 0 Members and 2 Guests are viewing this topic. msken Guest Help installing ANOPE « on: January 17, 2007, 02:34:06 AM » Hi,I'm a complete newb to iRCD networks and such. I am setting up an IRC server for a Massive Multiplayer Online Game I am developing at www.motorworldonline.net I have done a ton of reading and threw trail and error I have finally compiled and set up Unreal iRCD 3.2 on my server. I am following this tutorial here: http://news.softpedia.com/news/Building-Your-Own-IRC-Server-With-Services-40772.shtmlBut I just can't seem to get my anope services configured and running with Unreal 3.2? Is there anyone trust worthy out there whom I could let use my shell/FTP access to help me get up and running? Logged BigBen Anope User Offline Posts: 79 (No subject) « Reply #1 on: January 17, 2007, 03:39:27 AM » IF you downloaded Anope services, and have found the example.conf ( change it to services.conf ) and open in it, and change the stuff that it tells you to do, for example:listen services.bigtigerirc.net:6669;link 127.0.0.1{username *;hostname 127.0.0.1;bind-ip *;port 6669;password-connect "---"; be sure the passwords are the same!password-receive "---";class servers;options { -----------Services:RemoteServer 127.0.0.1 6669 "----"# ServerName
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 http://forum.anope.org/index.php?topic=1228.0 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. https://www.quakenet.org/help/general/what-do-those-quit-messages-mean 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 This quit message is displayed when the client terminated the connection to the IRC server prematurely, and the server expected more data. This
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 http://stackoverflow.com/questions/4584904/what-causes-the-broken-pipe-error 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 What causes the Broken Pipe Error? up vote 42 down vote favorite 12 I know that broken pipe error is thrown when the socket on the peer side is closed. But, in my test I have noted that an immediate 'send' call on this read error side when the peer side is closed doesn't always lead to a broken pipe error. E.g.: After closing the socket on peer side (I have tried clean closing by calling close and also abnormal closing by killing the peer), if I try to send 40 bytes, then I don't get a broken pipe, but, if I try to send 40000 bytes then it immediately gives broken pipe error. What exactly causes broken pipe and can it's behavior be predicted? c broken-pipe share|improve this question edited read error from Jun 9 at 7:53 Robert Siemer 7,33743455 asked Jan 3 '11 at 13:39 Jay 10.6k1551106 add a comment| 3 Answers 3 active oldest votes up vote 33 down vote accepted It can take time for the network close to be observed - the total time is nominally about 2 minutes (yes, minutes!) after a close before the packets destined for the port are all assumed to be dead. The error condition is detected at some point. With a small write, you are inside the MTU of the system, so the message is queued for sending. With a big write, you are bigger than the MTU and the system spots the problem quicker. If you ignore the SIGPIPE signal, then the functions will return EPIPE error on a broken pipe - at some point when the broken-ness of the connection is detected. share|improve this answer answered Jan 3 '11 at 16:55 Jonathan Leffler 441k62513824 3 @varevarao: I don't think that queueing transmissions and sending at specific intervals is a workaround. Queuing transmissions until there's more than the MTU to send might be a workaround if your application can live with the delays. –Jonathan Leffler Dec 13 '12 at 16:10 add a comment| up vote 6 down vote The current state of a socket is determined by 'keep-alive' activity. In your case, this is possible that when you are issuing the send call, the keep-alive activity tells that the socket is active and so the send call will write the required data (40 b