CAN'T OPEN A LISTENING SOCKET -- can't send userfile

fuggees · Post by **fuggees** » Sat May 20, 2006 10:50 pm

One of my users gets this after 30+ bots have connected to his hub and him in DCC Chat with the hub bot.

I have searched like crazy on this error and have not come up with anything. I do have other users with 30+ bots connected to a hub and they have not had issues.

Has anyone seen/had this issue? If so, what was the fix or did you get the issue fixed?

De Kus · Post by **De Kus** » Sun May 21, 2006 7:34 am

sounds like a open file restriction. check max-files/inodes. But maybe you also ran out of avaible ports.

fuggees · Post by **fuggees** » Sun May 21, 2006 9:19 am

check max-files/inodes have already been checked and they are high enough for that not to happen.

As far as running out of ports goes, consider, ports 1025-65535 on each ip are available. So I don't think I ran out of ports.

De Kus · Post by **De Kus** » Sun May 21, 2006 1:50 pm

well, if an application uses port 1050, and eggdrop tries to use port 1024-65535 it might get stuck after port 1049, since it tries to open 1050, which is unavaible.
It's called "reserved-portrange" not "theoretical avaible port range".

fuggees · Post by **fuggees** » Sun May 21, 2006 5:37 pm

Ok I get ya. My bad.