Brett Laney (Customer) asked a question.
I'm curious to know if anyone else is having issues after upgrading to 10.0.3? I'm already working with support, but we keep hitting our Maximum number of connections on the listener (which shouldn't be happening).
@Brett Laney (Customer) Hi Brett, Yes there are few cases reported with the same error message and Progress WS_FTP Engineering and Technical Support teams are working incessantly to resolve the issue soon.
Hi Samik, Hi Brett,
I hope you're both doing well.
Has this issue been resolved on your end? We appear to be experiencing similar behavior on our WS_FTP Server 10.0.3 environment. Our logs are showing repeated "Maximum number of connections exceeded" warnings, and users periodically become unable to connect until we restart the Progress SSH Server service.
Any insight would be greatly appreciated.
Thanks,
Aurel
@Aurel Dimaculangan (Customer) We are still investigating the issue. If there is a ticket submitted then WS_FTP Tech Support would share the findings and analysis on the same.
@Aurel Dimaculangan (Customer) Reducing the network timeout on SSH listener to 60 secs and followed by restart of SSH Service may help in this case as a workaround. You can try the same. This is basically reducing the idle timeout to 60 secs whole the default vaie us 600 secs.
If issue persists post workaround, please report to Technical support.
Thanks Samik!!!! I opened a ticket with support last night. We are in constant communication today. You suggestion is one of the tings they suggested as well. they also sent me a new DLL so we are trying that now before we move forward.
Not sure this is of value. My company had something similar, exceeding connections; that caused all kinds of havoc and severity tickets. The issue was that one of your middleware platforms, MuleSoft, held onto connections after use. We had to adjust the connector to disconnect after each use. That solved our issue. I also created a PowerShell script to check port 22 remote connections and send emails 3 or 4 times a day for proactive monitoring. To check the port 22 connections
If you would like the PowerShell script to monitor, I can attach it here. I hope this helps
Hi!
We experience the same problem.
5 days ago we updated from version 10.0.2 to 10.0.3 and the problem started:
After some hours no SFTP connection is possible. Log: "Maximum number of connections exceeded for the listener."
Session manager shows no SFTP-sessions, and also the OS (netstat) shows no SSH connection on Port 22.
A restart of the "Progress SSH Server" service is the only solution.
2 days ago we updated to the recently published version 10.0.4,
but the problem sill exists.
@Karl Köstler (Customer) We are working to fix this issue soon. You can submit a ticket via the Portal so that we can share the same as soon as we recieve it from Engineering.
Thanks for the replies, everyone.
We are still working with Progress Support on this issue. They have asked us to hold off on upgrading to 10.0.4 for now, as they are working on a fix.
We also identified a possible correlation with our health monitoring traffic and are continuing to investigate with Support.
Thanks,
Aurel
We are also still having the issue even with 10.0.4. Just to update issue
Thanks for the replies, everyone.
We are still working with Progress Support on this issue. They have asked us to hold off on upgrading to 10.0.4 for now, as they are working on a fix.
We also identified a possible correlation with our health monitoring traffic and are continuing to investigate with Support.
Thanks,
Aurel