Unable to create thread for connection
Answered
Hi,
The SFTP won't accept any new connections, in the log we see underneath.
A restart of the service resolves the issue.
Is this anything we can prevent?
[2020-03-10 11:37:28]:CONNECT [496498] - Incoming connection request on SSH interface 6 at x.x.x.x
[2020-03-10 11:37:28]:CONNECT [496498] - SSH SFTP connection request accepted from x.x.y.y
[2020-03-10 11:37:28]: ERROR [496498] - Unable to create thread for connection 1496498 from x.x.y.y
[2020-03-10 11:37:29]:CONNECT [496499] - Incoming connection request on SSH interface 6 at x.x.x.x
[2020-03-10 11:37:29]:CONNECT [496499] - SSH SFTP connection request accepted from x.x.y.y
[2020-03-10 11:37:29]: ERROR [496499] - Unable to create thread for connection 1496499 from x.x.y.y
[2020-03-10 11:37:29]:CONNECT [496500] - Incoming connection request on SSH interface 6 at x.x.x.x
[2020-03-10 11:37:29]:CONNECT [496500] - SSH SFTP connection request accepted from x.x.y.y
[2020-03-10 11:37:29]: ERROR [496500] - Unable to create thread for connection 1496500 from x.x.y.y
Kr,
Matt
-
Hello, Matt.
How many simultaneous connections do you have going on at one time?
It appears that something could be wrong at the OS level or the system is way overloaded and have too many threads allocated system-wide
The quick fix is to restart the Cerberus service in the Windows Service Manager.(As you have done already) I would also ensure that you are running the latest version of Cerberus as well.
0 -
Matt,
I am troubleshooting a similar issue, I am curious if you have found a solution.
Paul
0 -
Dana Anderson
We don't have that many simultaneous connections, I too believe its more likely to be related tot the OS.
We are indeed looking into upgrading to the latest version as our current version is end of life
Paul Murphy
We haven't found a definite root cause yet, we are planning to do the upgrade and hope to not see the error again. If not we'll continue troubleshooting and likely dive deeper on detecting this before it happens.
0 -
I upgraded from 10.0.4 I believe, to 11.0.10.0, issue still persists.
I would check to see how many max connections you allow per user and you allow per listener. i have 2 servers running Cerberus. Both were having this issue. I noticed that one had a max connection limit of 5 on the listener/interface and the user was allowed 100. I changed the listener to be 100 and have yet to have an issue on that particular server. I would make sure the listener/interface can allow at least the same number of max connections than the users.
I am testing this theory out with the other server at this time.
Just to note, I am using Windows Server 2012 R2.
0 -
Hey Paul,
Having a max connection limit of 5 would most definitely cause you some issues. By default, the connection limit is set to 500. Obviously, you can set it to what works best for your environment, but bumping it up to 100 may eliminate some of those errors.
0 -
Paul Murphy
We had the issue again today together with a memory alert.
I'm starting to think this is related to high memory consumption/memory spikes.
0 -
Hello Matt,
What exact version of Cerberus FTP Server are you currently running?
0 -
Hi Grant,
8.0.0.9, to be upgraded to the latest in the coming months.
The memory issues are related to the system, Cerberus was not using excessive amounts of memory.
Kr,
Matthias
0 -
Hi Matthias,
Thanks for the information. I'm glad to at least hear that it doesn't appear to be Cerberus causing these issues.
I know you mentioned looking to upgrade to the latest version from you current version, but if that upgrade is delayed for an extended period of time please note that you can at least upgrade to 8.0.13, regardless of your current support status. You're always able to upgrade to the latest minor release. There were 26 minor releases between 8.0.0.9 and 8.0.13 so you would at least get a significant number of bug, security vulnerability, and new feature additions.
Even within 8.0 there were a lot of fixes and new features between those releases.
0
Please sign in to leave a comment.
Comments
9 comments