Solaris: Connection / Protocol errors?

Nettworkz · Post by **Nettworkz** » Thu Dec 02, 2004 1:23 am

Hi All,

I've got an Unreal3.2.2 server that I'm having an odd issue with. I've searched around and googled it 10 different ways and can't find anything similar, let alone a solution.

------------------------------------------------------------------------------------
*** (s) Cannot accept connections randolph.us.zerofuzion.net[140.186.179.1.6667]

rotocol error
*** (s) Cannot accept connections randolph.us.zerofuzion.net[140.186.179.1.6667]

rotocol error
*** (s) setsockopt(SO_REUSEADDR) [217.117.132.108]:Broken pipe
*** (s) setsockopt(SO_USELOOPBACK) [217.117.132.108]:Broken pipe
*** (s) setsockopt(SO_RCVBUF) [217.117.132.108]:Broken pipe
*** (s) setsockopt(SO_SNDBUF) [217.117.132.108]:Broken pipe
*** (s) getsockopt(IP_OPTIONS) [217.117.132.108]:Broken pipe
*** (s) setsockopt(IP_OPTIONS) [217.117.132.108]:Broken pipe
*** (s) setsockopt(SO_RCVBUF) [217.117.132.108]:Connection reset by peer
*** (s) setsockopt(SO_SNDBUF) [217.117.132.108]:Broken pipe
*** (s) getsockopt(IP_OPTIONS) [217.117.132.108]:Broken pipe
*** (s) setsockopt(IP_OPTIONS) [217.117.132.108]:Broken pipe
*** (s) Cannot accept connections randolph.us.zerofuzion.net[140.186.179.1.6667]

rotocol error
*** (s) Cannot accept connections randolph.us.zerofuzion.net[140.186.179.1.6667]

rotocol error
------------------------------------------------------------------------------

This is repeated randomly throughout the day, the "setsockopt" is not that frequent, but the protocol errors, I get several hundred a day for some reason.

Anyone have any insite/thoughts on what this is and how to fix it?

Thanks.

codemastr · Post by **codemastr** » Thu Dec 02, 2004 2:55 am

It sounds as though something is severely wrong with your system and/or connection.

Post by **Syzop** » Thu Dec 02, 2004 4:45 am

First, what OS is this?

I've never seen the protocol error stuff before but here it says that it could happen on accept() if the connection went away during accepting.
The same is true for the [get|set]sockopt() stuff.
Both things could be just harmless errors (especially if it are only a few IPs creating many msgs), or do you also have connected clients dieing with these weird errors for no reason?

Nettworkz · Post by **Nettworkz** » Fri Dec 03, 2004 12:08 am

Syzop wrote:First, what OS is this?

This is under the Solaris OS

I've never seen the protocol error stuff before but here it says that it could happen on accept() if the connection went away during accepting.
The same is true for the [get|set]sockopt() stuff.
Both things could be just harmless errors (especially if it are only a few IPs creating many msgs), or do you also have connected clients dieing with these weird errors for no reason?

Once clients are connected, all seems fine and there are no disconnects associated with this error. I'm only seeing it when clients are first attempting to connect to the IRCD.

Other than these annoying error messages, the ircd has been quite the champ in the number of users it has been hosting without any other problems.

Post by **Syzop** » Fri Dec 03, 2004 12:18 am

This is under the Solaris OS
--snip.. not noticing any problems..--

Ah ic.. that explains :P.
You can safely ignore these errors.

Also, these messages are not broadcast to opers unless they have the junk snomask set, so they shouldn't bother you TOO much? ;P

Anyway, I'll have a look at ignoring these specific cases.
Like for example the accept() errors are sent to all opers in CVS (not in any release), so I'll have to ignore those harmless (solaris) errors anyway.
Sidenote, we already ignore a few Linux/FreeBSD specific errors, it's just that almost every OS comes up with some other harmless errors (but don't worry, we are getting there) :P.

Nettworkz · Post by **Nettworkz** » Sat Dec 04, 2004 6:52 am

Well Alllllllrighty then.. I'll just ignore them

Thanks for the info, had me scratching my head.