Failing because we have 4063 connections already. Please read doc

niftyhamster · 09-28-2016, 04:21 PM

Hi there,

I get a lot of error messages "Failing because we have 4063 connections already. Please read doc". I am running Debian 7 64 fully patched. I already googled this error message and could not solve it. Playing around with ulimit does nothing.

Anyone any good idea how to get rid of this error? Thanks for reading

niftyhamster

PS: Please speak newbie to me

Keith Hedger · 09-28-2016, 06:08 PM

you need to be more specific about what is causing tnis error is it in a browser, command line, what commands are u actually using?

niftyhamster · 09-28-2016, 06:15 PM

niftyhedgehog notices.log RN] Failing because we have 4063 connections already. Please read doc
root@43ba79:~# cat /proc/sys/fs/file-max
100000
root@43ba79:~# ls
niftyhedgehog notices.log RN] Failing because we have 4063 connections already. Please read doc
root@43ba79:~# nano /etc/security/limits.conf
root@43ba79:~# ulimit -n -H
65535
root@43ba79:~# ls
niftyhedgehog notices.log RN] Failing because we have 4063 connections already. Please read doc
root@43ba79:~# cat /proc/sys/fs/file-max
100000
root@43ba79:~#

Sorry, it shows up on the CLI. So its a message from Debian itself and not from an installed prg.

Cheers,

Markus

ondoho · 09-29-2016, 01:40 AM

^ do you mean it shows up whenever you open a terminal, and whenever you enter 'ls'?

incidentally, why are you root? does the error also occur when you're a normal user?

and...

Quote:

Originally Posted by niftyhamster

I am running Debian 7 64 fully patched.

...what do you mean "fully patched"?
what distro are you actually using?

sundialsvcs · 09-29-2016, 08:04 AM

You can't have done much Googling, because if you had searched for exact-phrases you would find that this message is coming from tor.

There is always a limit as to the maximum number of connections that any server (process) can accept, and therefore sustain, at any one time. More connection-requests might come, such that a select() loop would see them, but the process can only open so-many sockets at one time.

If you are now entertaining over four thousand sockets, you already have a serious problem, and that is the root-cause problem, not any sort of limit-tweaking command that you might use to increase the limits that prevail.

niftyhamster · 09-29-2016, 08:33 AM

Quote:

Originally Posted by sundialsvcs

You can't have done much Googling, because if you had searched for exact-phrases you would find that this message is coming from tor.

As I said: I googled it and the fix with ulimit does not help on this server. Read it again. Understand it.

There is always a limit as to the maximum number of connections that any server (process) can accept, and therefore sustain, at any one time. More connection-requests might come, such that a select() loop would see them, but the process can only open so-many sockets at one time.

UHHHH, yeah?

If you are now entertaining over four thousand sockets, you already have a serious problem, and that is the root-cause problem, not any sort of limit-tweaking command that you might use to increase the limits that prevail.

Right, thank you for not helping but bulls****ing me.

Keith Hedger · 09-29-2016, 06:09 PM

sundialsvcs is correct a simple google search for that error ( i copied and pasted it as you posted it ) givez a load of links all pointing to the problem being with tor.

ondoho · 09-30-2016, 12:54 AM

Quote:

Originally Posted by sundialsvcs

There is always a limit as to the maximum number of connections that any server (process) can accept, and therefore sustain, at any one time.

aaah, it's a server!
another piece of crucial information withheld.

niftyhamster, the reactions you received are entirely justified.
you however, slowly drifting into abusive language and still not providing the minimum effort required to enable others to help you, aren't justified.

please read the first link in my signature.