Irc Broken Pipe Error
Contents |
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 read error: connection reset by peer irc thought you were attempting to flood it. A good way to prevent this is to irc connection reset by peer enable flood protection in your IRC client. mIRC users may click File -> Options -> IRC -> Flood, and then check Enable flood irc ping timeout 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
Max Sendq Exceeded
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 irc client 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 is often caused if the IRC client software crashes or exits suddenly, when it doesn't have the chance to close the connection gracefully. Write error, closing link This quit message means that the IRC server, for some reason or another, failed to send data to the client. Due to this
connection abort 5 [10054] Connection reset by peer 6 [10060] Connection timed out 7 [10061] Connection refused 8 [10065] No route to host Error 9 Unable to resolve server 10 Ping Timeout 11 Broken pipe Common connection related errors. For an extended explanation on mirc these errors, please visit IRC Errors [10049] Can't assign requested address This means the address you are trying to connect to does not resolve to an accessible IP. To combat this issue, try connecting directly to another server. The server list can be found here. [10050] Network is down or [10051] Network unreachable These errors occur on if the destination network is down. [10052] Network dropped connection on reset The server that is hosting the IRCd, or the https://www.quakenet.org/help/general/what-do-those-quit-messages-mean network it's on has, crashed, rebooted or been reset. Just reconnect in a few minutes. [10053] Software cause connection abort There is an issue with your client attempting to connect/respond to the IRC server. One cause for this may be the use of SSL. Connect to the network on a non-SSL port to attempt to combat this issue. [10054] Connection reset by peer Connection reset by peer is a tough one because it can be caused by so many https://wiki.swiftirc.net/wiki/Connection_issues things. In all cases, the server determines that the socket is no longer good and closes it from its side. [10060] Connection timed out A connect or send request failed because the connected party did not properly respond after a period of time. (The timeout period is dependent on the communication protocol.) [10061] Connection refused Users mainly receive this error because of a firewall issue. If you connect to the wrong port or a port that your firewall is blocking, you will receive this issue. Attempting to connect on port 8080 (to the servers that listen on it) will most likely fix this issue. The servers page can be found here. [10065] No route to host Error This normally means you are not properly connected to the Internet. Your Windows cannot find out how or where to find the IRC server. It has nothing todo with mIRC or IRC! Check your connection (reconnect if everything seems fine) and try again. Unable to resolve server This error occurs when the DNS records (that convert hostnames to IP addresses for actual use) are altered or non-existant (no authoritative DNS server could be located). Ping Timeout Servers automatically ping users at preset intervals to ensure the client is still connected to the server. It means the server has pinged a user's client and hasn't received a reply, which automatically disconnects the user. This results in a ping timeou
and revised October 5, 2002 Table Of Contents 1.0 Introduction 1.1 What are IRC quit messages 1.2 Where are they displayed 1.3 http://www.user-com.undernet.org/documents/quitmsg.php How to gather information from quit messages 1.4 Customizing quit messages 2.0 Read/Write error quit messages 2.1 Read error definition 2.2 Write error definition 2.3 Connection reset by peer 3.0 https://forum.anope.org/index.php?topic=2313.0 Ping timeout 3.1 Definition of ping 3.2 When they occur 3.3 Avoiding ping timeouts 4.0 Less common quit messages 4.1 Other quit messages 4.2 Nick Collisions 4.3 Recognizing a connection reset netsplit 4.4 Broken Pipe 4.5 Max SendQ Exceeded 4.6 Excess Flood 4.7 Oper-resulted quit messages 5.0 References and acknowledgements 5.1 Other resources 5.2 Acknowledgements 1.0 Introduction 1.1 What are IRC quit messages Quit messages are used on IRC to describe why the user is disconnecting from IRC (or quitting as it's called),via a custom quit message, or the reason why connection reset by the server closed the connection. Custom quit messages can be created by the user to show or tell other users why they are leaving . They cannot exceed 160 characters, and they are limited to a single line. Server quit messages can be used to describe the reason that caused a disconnection from the server. 1.2 Where are they displayed The display of a quit message is pretty straightforward. When the user disconnects, a message is displayed in the channel window. A quit message is not shown in a query/chat window when the user quits, so if you don't receive an answer in a private chat, check your status window for a "no such nick" message, or do a /whois to check. In the channel, the usual quit message is "Nick has quit IRC (message)". In the message area, a description is placed. This can either be a custom quit message, or an error quit message as described above. 1.3 How to gather information from quit messages Besides gathering information about why a user has disc
Only)> Read error from server: Broken pipe « previous next » Pages: [1] Go Down Print Author Topic: Read error from server: Broken pipe (Read 6892 times) 0 Members and 2 Guests are viewing this topic. rapax Anope User Offline Posts: 3 Read error from server: Broken pipe « on: September 06, 2008, 03:16:05 AM » I've been getting hit everyday by some kids and the services are crashing every time. Is there a way to prevent this type of attack?[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG nickserv :help"[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG helpserv :help"[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG operserv :help"[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG chanserv :help"[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG hostserv :help"[Sep 05 16:04:44 2008] Ignored message from zRtyKfTcRsS: ":zRtyKfTcRsS PRIVMSG botserv :help"[Sep 05 16:04:45 2008] Read error from server: Broken pipeThe attack is massive, this is the last portion, before the services crash.Please advise... Logged deiks Anope User Offline Gender: Posts: 139 Shizle my nizle Re: Read error from server: Broken pipe « Reply #1 on: September 06, 2008, 09:37:00 AM » Use spamfilter nick match, or use proxy scanners.There's no way to prevent it, if they're connected to server.If they're connected then it's like regular user.I'm using BOPM and AKILL. Logged Jan Milants Team Offline Gender: Posts: 1372 Re: Read error from server: Broken pipe « Reply #2 on: September 06, 2008, 10:39:27 AM » consider lowering the sendq and receiveq of your client blocks... Logged If you like me donate coins to 1FBmZVT4J8WAUMHKqpWhgNVj3XXnRN1cCk Jobe Contributor Offline Gender: Posts: 1023 Re: Read error from server: Broken pipe « Reply #3 on: September 06, 2008, 11:55:21 AM » Are you running UnrealIRCd? if so can you