You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ftpserver-users@mina.apache.org by Dan <da...@tipjarawards.com> on 2009/04/03 16:05:44 UTC
Maximum login connections: 421
I am getting:
WARNING: SENT: 421 Maximum login limit has been reached.
I have set the connection configuration as follows:
ConnectionConfigFactory connectionConfigFactory = new
ConnectionConfigFactory();
connectionConfigFactory.setMaxLogins(32);
The thing is there aren't even close to 32 people logged in right now, are
there known bugs with having hanging connections etc. that could cause this?
Any hints to help debug this in the future?
Thanks,
Dan
RE: Maximum login connections: 421
Posted by "Loureiro, Gil" <gi...@logica.com>.
Hi,
I've a similar problem, in conditions that I don't know the server returns that message, even in a configuration without connection limit.
On my case I think this appends when exceptions occurs on my ftplet...
Cumprimentos,
Loureiro, Gil
Document Engineering Manager
Document Services
_________________________________________
Edinfor - a LogicaCMG company
Rua Particular da EDP (à rua cidade Goa nº11), 2685 Sacavém
Portugal
M: +351 93 741 8888
E: gil.loureiro@edinfor.logicacmg.com
www.edinfor.logicacmg.com
-----Original Message-----
From: Dan [mailto:dan@tipjarawards.com]
Sent: sexta-feira, 3 de Abril de 2009 15:06
To: ftpserver-users@mina.apache.org
Subject: Maximum login connections: 421
I am getting:
WARNING: SENT: 421 Maximum login limit has been reached.
I have set the connection configuration as follows:
ConnectionConfigFactory connectionConfigFactory = new
ConnectionConfigFactory();
connectionConfigFactory.setMaxLogins(32);
The thing is there aren't even close to 32 people logged in right now, are
there known bugs with having hanging connections etc. that could cause this?
Any hints to help debug this in the future?
Thanks,
Dan
Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei die Umwelt zu schuetzen / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico.
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
RE: Stability and reliability issues
Posted by Dan <da...@tipjarawards.com>.
Ummmmm no :)
Next time I'll get them
Thanks Niklas,
Dan
-----Original Message-----
From: Niklas Gustavsson [mailto:niklas@protocol7.com]
Sent: April-10-09 2:16 PM
To: ftpserver-users@mina.apache.org
Subject: Re: Stability and reliability issues
Were you able to get a netstat -a or lsof output from the hung server?
/niklas
On Fri, Apr 10, 2009 at 6:05 PM, Dan <da...@tipjarawards.com> wrote:
> Versions we are using: RC1 and Mina M4 inside of tomcat 5.5.x on linux
> 32-bit.
>
> Another crash after two days or working, had to restart server. So in
> a way this is good news, worse would be crashes every month, I'm sure
> we can track this bug down. We are running the server on its own
> machine so it is running in a very isolated environment.
>
> After the crash the server stays running to some extent but nobody can
> connect (endless CREATED log messages but no logins), here is the
> Filezilla
> output:
>
> ----------------------------------------
> Status: Connecting to 174.129.220.134:21...
> Status: Connection established, waiting for welcome message...
> Error: Connection timed out
> Error: Could not connect to server
> ----------------------------------------
>
> Can't give a DEBUG log output since simply too much output from other
> components that are running. Here is the last snippet of INFO level
> logging before crash:
>
> ------------------------------------------------
> Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: SENT: 250 Directory changed to /XXX/files/SyncData^M
>
> Apr 10, 2009 3:32:12 PM
> org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: MODE S
> Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: SENT: 200 Command MODE okay.^M
>
> Apr 10, 2009 3:32:13 PM
> org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: STRU F
> Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: SENT: 200 Command STRU okay.^M
>
> Apr 10, 2009 3:32:13 PM
> org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: TYPE I
> Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: SENT: 200 Command TYPE okay.^M
>
> Apr 10, 2009 3:32:13 PM
> org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: PASV
> Apr 10, 2009 3:33:15 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:33:35 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:33:55 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:34:15 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:34:35 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:34:55 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:35:15 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:35:37 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:35:57 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> Apr 10, 2009 3:36:17 PM org.apache.mina.filter.logging.LoggingFilter
> log
> WARNING: CREATED
> --------------------------------------------------------
>
> -----Original Message-----
> From: David Latorre [mailto:dvlato@gmail.com]
> Sent: April-07-09 3:44 AM
> To: ftpserver-users@mina.apache.org
> Subject: Re: Stability and reliability issues
>
> My answers are below:
>
> 2009/4/6 Dan <da...@tipjarawards.com>:
>> We are using RC1 with Mina M4 and we start the server embedded in a
>> tomcat 5.5.x webapp. Java is version 5.0 running on Linux. There was
>> another user with the same "Max login" problem as I previously posted
>> that problem to this group.
>>
>> Even when the ftp server dies the tomcat server is running fine
>> throughout, still taking connections etc. Once we reboot the ftp
>> server starts working again.
>>
>
> Can you provide more info on your environment? For example: are you
> updated to the latest 5.0 version? Are you using SSL or plain
> connections )? Active or Passive? both of them?
>
> Since you're integrating FtpServer into Tomcat I do not know which
> logging facility you're using: is it log4j? In that case, DEBUG level
> is set in log4j.properties; the ready-to-use ftpserver bundled has a
> log4j.properties, but i'd rather use a file appender.
>
>
>> At this point my guess is there is somewhere in the login workflow
>> where something isn't being closed properly. We have several users
>> running batch scripts, if they aren't closing a connection etc. that
>> should not be able to crash the ftp server. Maybe connections are not
>> being closed or collected with an idle timeout in some cases?
>
> Once you set the LOG level to debug can you send it along with the
> configuration you are using (you aren't using the xml config
unfortunately).
> Are you using custom Ftplets?
>
>>
>> For now we are just going to restart the server and wait and see.
>>
>> Thanks,
>>
>> Dan
>>
>> -----Original Message-----
>> From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
>> Sent: April-06-09 2:00 PM
>> To: ftpserver-users@mina.apache.org
>> Subject: RE: Stability and reliability issues
>>
>>
>> Well I'm using this server in a couple different production
>> environments without any issues and I know there are others on this
>> list who are as well, so I'd say your experience is not typical.
>>
>> What version of the ftp server and Java are you using? What operating
>> system?
>>
>> The debug level is set in log4j.properties.
>>
>>
>>
>>
>> -----Original Message-----
>> From: Dan [mailto:dan@tipjarawards.com]
>> Sent: Monday, April 06, 2009 1:51 PM
>> To: ftpserver-users@mina.apache.org
>> Subject: Stability and reliability issues
>>
>> We are having some serious stability/scalability issues with the ftp
> server.
>>
>> First there were hanging logins (nobody able to login but supposedly
>> max login users was reacehd according to log message). With idle
>> timeouts this should never happen as after a few minutes all the
>> "dead" logins should have been collected.
>>
>> Second problem we are now getting 'Could not connect to server' and
>> 'Connection timed out' errors with the server running after only two
days.
>> It gets as far as the "CREATED" log message then hangs as a user
>> tries to connect and login. So we will be rebooting the server again
>> as it appears the server is again dead.
>>
>> I hope the focus of development is first and foremost
>> stability/reliability since adding in new features to a server that
>> keeps crashing in a production environment is very troubling.
>>
>> I am happy to provide more debug info or log info to help, it's just
>> not clear how to accomplish this. Where can I easily set the debug level?
>>
>> Any ideas? Let me know.
>>
>> Thanks,
>>
>> Dan
>>
>>
>>
>>
>>
>>
>> -----------------------------------------
>> Use of email is inherently insecure. Confidential information,
>> including account information, and personally identifiable
>> information, should not be transmitted via email, or email attachment.
>> In no event shall Citizens or any of its affiliates accept any
>> responsibility for the loss, use or misuse of any information
>> including confidential information, which is sent to Citizens or its
>> affiliates via email, or email attachment. Citizens does not
>> guarantee the accuracy of any email or email attachment, that an
>> email will be
> received by Citizens or that Citizens will respond to any email.
>>
>> This email message is confidential and/or privileged. It is to be
>> used by the intended recipient only. Use of the information
>> contained in this email by anyone other than the intended recipient
>> is strictly prohibited. If you have received this message in error,
>> please notify the sender immediately and promptly destroy any record of
this email.
>>
>>
>
>
Re: Stability and reliability issues
Posted by Niklas Gustavsson <ni...@protocol7.com>.
Were you able to get a netstat -a or lsof output from the hung server?
/niklas
On Fri, Apr 10, 2009 at 6:05 PM, Dan <da...@tipjarawards.com> wrote:
> Versions we are using: RC1 and Mina M4 inside of tomcat 5.5.x on linux
> 32-bit.
>
> Another crash after two days or working, had to restart server. So in a way
> this is good news, worse would be crashes every month, I'm sure we can track
> this bug down. We are running the server on its own machine so it is running
> in a very isolated environment.
>
> After the crash the server stays running to some extent but nobody can
> connect (endless CREATED log messages but no logins), here is the Filezilla
> output:
>
> ----------------------------------------
> Status: Connecting to 174.129.220.134:21...
> Status: Connection established, waiting for welcome message...
> Error: Connection timed out
> Error: Could not connect to server
> ----------------------------------------
>
> Can't give a DEBUG log output since simply too much output from other
> components that are running. Here is the last snippet of INFO level logging
> before crash:
>
> ------------------------------------------------
> Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: SENT: 250 Directory changed to /XXX/files/SyncData^M
>
> Apr 10, 2009 3:32:12 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: MODE S
> Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: SENT: 200 Command MODE okay.^M
>
> Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: STRU F
> Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: SENT: 200 Command STRU okay.^M
>
> Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: TYPE I
> Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: SENT: 200 Command TYPE okay.^M
>
> Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
> messageReceived
> INFO: RECEIVED: PASV
> Apr 10, 2009 3:33:15 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:33:35 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:33:55 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:34:15 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:34:35 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:34:55 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:35:15 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:35:37 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:35:57 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> Apr 10, 2009 3:36:17 PM org.apache.mina.filter.logging.LoggingFilter log
> WARNING: CREATED
> --------------------------------------------------------
>
> -----Original Message-----
> From: David Latorre [mailto:dvlato@gmail.com]
> Sent: April-07-09 3:44 AM
> To: ftpserver-users@mina.apache.org
> Subject: Re: Stability and reliability issues
>
> My answers are below:
>
> 2009/4/6 Dan <da...@tipjarawards.com>:
>> We are using RC1 with Mina M4 and we start the server embedded in a
>> tomcat 5.5.x webapp. Java is version 5.0 running on Linux. There was
>> another user with the same "Max login" problem as I previously posted
>> that problem to this group.
>>
>> Even when the ftp server dies the tomcat server is running fine
>> throughout, still taking connections etc. Once we reboot the ftp
>> server starts working again.
>>
>
> Can you provide more info on your environment? For example: are you updated
> to the latest 5.0 version? Are you using SSL or plain connections )? Active
> or Passive? both of them?
>
> Since you're integrating FtpServer into Tomcat I do not know which logging
> facility you're using: is it log4j? In that case, DEBUG level is set in
> log4j.properties; the ready-to-use ftpserver bundled has a log4j.properties,
> but i'd rather use a file appender.
>
>
>> At this point my guess is there is somewhere in the login workflow
>> where something isn't being closed properly. We have several users
>> running batch scripts, if they aren't closing a connection etc. that
>> should not be able to crash the ftp server. Maybe connections are not
>> being closed or collected with an idle timeout in some cases?
>
> Once you set the LOG level to debug can you send it along with the
> configuration you are using (you aren't using the xml config unfortunately).
> Are you using custom Ftplets?
>
>>
>> For now we are just going to restart the server and wait and see.
>>
>> Thanks,
>>
>> Dan
>>
>> -----Original Message-----
>> From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
>> Sent: April-06-09 2:00 PM
>> To: ftpserver-users@mina.apache.org
>> Subject: RE: Stability and reliability issues
>>
>>
>> Well I'm using this server in a couple different production
>> environments without any issues and I know there are others on this
>> list who are as well, so I'd say your experience is not typical.
>>
>> What version of the ftp server and Java are you using? What operating
>> system?
>>
>> The debug level is set in log4j.properties.
>>
>>
>>
>>
>> -----Original Message-----
>> From: Dan [mailto:dan@tipjarawards.com]
>> Sent: Monday, April 06, 2009 1:51 PM
>> To: ftpserver-users@mina.apache.org
>> Subject: Stability and reliability issues
>>
>> We are having some serious stability/scalability issues with the ftp
> server.
>>
>> First there were hanging logins (nobody able to login but supposedly
>> max login users was reacehd according to log message). With idle
>> timeouts this should never happen as after a few minutes all the
>> "dead" logins should have been collected.
>>
>> Second problem we are now getting 'Could not connect to server' and
>> 'Connection timed out' errors with the server running after only two days.
>> It gets as far as the "CREATED" log message then hangs as a user tries
>> to connect and login. So we will be rebooting the server again as it
>> appears the server is again dead.
>>
>> I hope the focus of development is first and foremost
>> stability/reliability since adding in new features to a server that
>> keeps crashing in a production environment is very troubling.
>>
>> I am happy to provide more debug info or log info to help, it's just
>> not clear how to accomplish this. Where can I easily set the debug level?
>>
>> Any ideas? Let me know.
>>
>> Thanks,
>>
>> Dan
>>
>>
>>
>>
>>
>>
>> -----------------------------------------
>> Use of email is inherently insecure. Confidential information,
>> including account information, and personally identifiable
>> information, should not be transmitted via email, or email attachment.
>> In no event shall Citizens or any of its affiliates accept any
>> responsibility for the loss, use or misuse of any information
>> including confidential information, which is sent to Citizens or its
>> affiliates via email, or email attachment. Citizens does not guarantee
>> the accuracy of any email or email attachment, that an email will be
> received by Citizens or that Citizens will respond to any email.
>>
>> This email message is confidential and/or privileged. It is to be used
>> by the intended recipient only. Use of the information contained in
>> this email by anyone other than the intended recipient is strictly
>> prohibited. If you have received this message in error, please notify
>> the sender immediately and promptly destroy any record of this email.
>>
>>
>
>
RE: Stability and reliability issues
Posted by Dan <da...@tipjarawards.com>.
Versions we are using: RC1 and Mina M4 inside of tomcat 5.5.x on linux
32-bit.
Another crash after two days or working, had to restart server. So in a way
this is good news, worse would be crashes every month, I'm sure we can track
this bug down. We are running the server on its own machine so it is running
in a very isolated environment.
After the crash the server stays running to some extent but nobody can
connect (endless CREATED log messages but no logins), here is the Filezilla
output:
----------------------------------------
Status: Connecting to 174.129.220.134:21...
Status: Connection established, waiting for welcome message...
Error: Connection timed out
Error: Could not connect to server
----------------------------------------
Can't give a DEBUG log output since simply too much output from other
components that are running. Here is the last snippet of INFO level logging
before crash:
------------------------------------------------
Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: SENT: 250 Directory changed to /XXX/files/SyncData^M
Apr 10, 2009 3:32:12 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
messageReceived
INFO: RECEIVED: MODE S
Apr 10, 2009 3:32:12 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: SENT: 200 Command MODE okay.^M
Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
messageReceived
INFO: RECEIVED: STRU F
Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: SENT: 200 Command STRU okay.^M
Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
messageReceived
INFO: RECEIVED: TYPE I
Apr 10, 2009 3:32:13 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: SENT: 200 Command TYPE okay.^M
Apr 10, 2009 3:32:13 PM org.apache.ftpserver.listener.nio.FtpLoggingFilter
messageReceived
INFO: RECEIVED: PASV
Apr 10, 2009 3:33:15 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:33:35 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:33:55 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:34:15 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:34:35 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:34:55 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:35:15 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:35:37 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:35:57 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
Apr 10, 2009 3:36:17 PM org.apache.mina.filter.logging.LoggingFilter log
WARNING: CREATED
--------------------------------------------------------
-----Original Message-----
From: David Latorre [mailto:dvlato@gmail.com]
Sent: April-07-09 3:44 AM
To: ftpserver-users@mina.apache.org
Subject: Re: Stability and reliability issues
My answers are below:
2009/4/6 Dan <da...@tipjarawards.com>:
> We are using RC1 with Mina M4 and we start the server embedded in a
> tomcat 5.5.x webapp. Java is version 5.0 running on Linux. There was
> another user with the same "Max login" problem as I previously posted
> that problem to this group.
>
> Even when the ftp server dies the tomcat server is running fine
> throughout, still taking connections etc. Once we reboot the ftp
> server starts working again.
>
Can you provide more info on your environment? For example: are you updated
to the latest 5.0 version? Are you using SSL or plain connections )? Active
or Passive? both of them?
Since you're integrating FtpServer into Tomcat I do not know which logging
facility you're using: is it log4j? In that case, DEBUG level is set in
log4j.properties; the ready-to-use ftpserver bundled has a log4j.properties,
but i'd rather use a file appender.
> At this point my guess is there is somewhere in the login workflow
> where something isn't being closed properly. We have several users
> running batch scripts, if they aren't closing a connection etc. that
> should not be able to crash the ftp server. Maybe connections are not
> being closed or collected with an idle timeout in some cases?
Once you set the LOG level to debug can you send it along with the
configuration you are using (you aren't using the xml config unfortunately).
Are you using custom Ftplets?
>
> For now we are just going to restart the server and wait and see.
>
> Thanks,
>
> Dan
>
> -----Original Message-----
> From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
> Sent: April-06-09 2:00 PM
> To: ftpserver-users@mina.apache.org
> Subject: RE: Stability and reliability issues
>
>
> Well I'm using this server in a couple different production
> environments without any issues and I know there are others on this
> list who are as well, so I'd say your experience is not typical.
>
> What version of the ftp server and Java are you using? What operating
> system?
>
> The debug level is set in log4j.properties.
>
>
>
>
> -----Original Message-----
> From: Dan [mailto:dan@tipjarawards.com]
> Sent: Monday, April 06, 2009 1:51 PM
> To: ftpserver-users@mina.apache.org
> Subject: Stability and reliability issues
>
> We are having some serious stability/scalability issues with the ftp
server.
>
> First there were hanging logins (nobody able to login but supposedly
> max login users was reacehd according to log message). With idle
> timeouts this should never happen as after a few minutes all the
> "dead" logins should have been collected.
>
> Second problem we are now getting 'Could not connect to server' and
> 'Connection timed out' errors with the server running after only two days.
> It gets as far as the "CREATED" log message then hangs as a user tries
> to connect and login. So we will be rebooting the server again as it
> appears the server is again dead.
>
> I hope the focus of development is first and foremost
> stability/reliability since adding in new features to a server that
> keeps crashing in a production environment is very troubling.
>
> I am happy to provide more debug info or log info to help, it's just
> not clear how to accomplish this. Where can I easily set the debug level?
>
> Any ideas? Let me know.
>
> Thanks,
>
> Dan
>
>
>
>
>
>
> -----------------------------------------
> Use of email is inherently insecure. Confidential information,
> including account information, and personally identifiable
> information, should not be transmitted via email, or email attachment.
> In no event shall Citizens or any of its affiliates accept any
> responsibility for the loss, use or misuse of any information
> including confidential information, which is sent to Citizens or its
> affiliates via email, or email attachment. Citizens does not guarantee
> the accuracy of any email or email attachment, that an email will be
received by Citizens or that Citizens will respond to any email.
>
> This email message is confidential and/or privileged. It is to be used
> by the intended recipient only. Use of the information contained in
> this email by anyone other than the intended recipient is strictly
> prohibited. If you have received this message in error, please notify
> the sender immediately and promptly destroy any record of this email.
>
>
Re: Stability and reliability issues
Posted by David Latorre <dv...@gmail.com>.
My answers are below:
2009/4/6 Dan <da...@tipjarawards.com>:
> We are using RC1 with Mina M4 and we start the server embedded in a tomcat
> 5.5.x webapp. Java is version 5.0 running on Linux. There was another user
> with the same "Max login" problem as I previously posted that problem to
> this group.
>
> Even when the ftp server dies the tomcat server is running fine throughout,
> still taking connections etc. Once we reboot the ftp server starts working
> again.
>
Can you provide more info on your environment? For example: are you
updated to the latest 5.0 version? Are you using SSL or plain
connections )? Active or Passive? both of them?
Since you're integrating FtpServer into Tomcat I do not know which
logging facility you're using: is it log4j? In that case, DEBUG level
is set in log4j.properties; the ready-to-use ftpserver bundled has a
log4j.properties, but i'd rather use a file appender.
> At this point my guess is there is somewhere in the login workflow where
> something isn't being closed properly. We have several users running batch
> scripts, if they aren't closing a connection etc. that should not be able to
> crash the ftp server. Maybe connections are not being closed or collected
> with an idle timeout in some cases?
Once you set the LOG level to debug can you send it along with the
configuration you are using (you aren't using the xml config
unfortunately). Are you using custom Ftplets?
>
> For now we are just going to restart the server and wait and see.
>
> Thanks,
>
> Dan
>
> -----Original Message-----
> From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
> Sent: April-06-09 2:00 PM
> To: ftpserver-users@mina.apache.org
> Subject: RE: Stability and reliability issues
>
>
> Well I'm using this server in a couple different production environments
> without any issues and I know there are others on this list who are as well,
> so I'd say your experience is not typical.
>
> What version of the ftp server and Java are you using? What operating
> system?
>
> The debug level is set in log4j.properties.
>
>
>
>
> -----Original Message-----
> From: Dan [mailto:dan@tipjarawards.com]
> Sent: Monday, April 06, 2009 1:51 PM
> To: ftpserver-users@mina.apache.org
> Subject: Stability and reliability issues
>
> We are having some serious stability/scalability issues with the ftp server.
>
> First there were hanging logins (nobody able to login but supposedly max
> login users was reacehd according to log message). With idle timeouts this
> should never happen as after a few minutes all the "dead" logins should have
> been collected.
>
> Second problem we are now getting 'Could not connect to server' and
> 'Connection timed out' errors with the server running after only two days.
> It gets as far as the "CREATED" log message then hangs as a user tries to
> connect and login. So we will be rebooting the server again as it appears
> the server is again dead.
>
> I hope the focus of development is first and foremost stability/reliability
> since adding in new features to a server that keeps crashing in a production
> environment is very troubling.
>
> I am happy to provide more debug info or log info to help, it's just not
> clear how to accomplish this. Where can I easily set the debug level?
>
> Any ideas? Let me know.
>
> Thanks,
>
> Dan
>
>
>
>
>
>
> -----------------------------------------
> Use of email is inherently insecure. Confidential information, including
> account information, and personally identifiable information, should not be
> transmitted via email, or email attachment. In no event shall Citizens or
> any of its affiliates accept any responsibility for the loss, use or misuse
> of any information including confidential information, which is sent to
> Citizens or its affiliates via email, or email attachment. Citizens does not
> guarantee the accuracy of any email or email attachment, that an email will
> be received by Citizens or that Citizens will respond to any email.
>
> This email message is confidential and/or privileged. It is to be used by
> the intended recipient only. Use of the information contained in this email
> by anyone other than the intended recipient is strictly prohibited. If you
> have received this message in error, please notify the sender immediately
> and promptly destroy any record of this email.
>
>
RE: Stability and reliability issues
Posted by Dan <da...@tipjarawards.com>.
We are using RC1 with Mina M4 and we start the server embedded in a tomcat
5.5.x webapp. Java is version 5.0 running on Linux. There was another user
with the same "Max login" problem as I previously posted that problem to
this group.
Even when the ftp server dies the tomcat server is running fine throughout,
still taking connections etc. Once we reboot the ftp server starts working
again.
At this point my guess is there is somewhere in the login workflow where
something isn't being closed properly. We have several users running batch
scripts, if they aren't closing a connection etc. that should not be able to
crash the ftp server. Maybe connections are not being closed or collected
with an idle timeout in some cases?
For now we are just going to restart the server and wait and see.
Thanks,
Dan
-----Original Message-----
From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
Sent: April-06-09 2:00 PM
To: ftpserver-users@mina.apache.org
Subject: RE: Stability and reliability issues
Well I'm using this server in a couple different production environments
without any issues and I know there are others on this list who are as well,
so I'd say your experience is not typical.
What version of the ftp server and Java are you using? What operating
system?
The debug level is set in log4j.properties.
-----Original Message-----
From: Dan [mailto:dan@tipjarawards.com]
Sent: Monday, April 06, 2009 1:51 PM
To: ftpserver-users@mina.apache.org
Subject: Stability and reliability issues
We are having some serious stability/scalability issues with the ftp server.
First there were hanging logins (nobody able to login but supposedly max
login users was reacehd according to log message). With idle timeouts this
should never happen as after a few minutes all the "dead" logins should have
been collected.
Second problem we are now getting 'Could not connect to server' and
'Connection timed out' errors with the server running after only two days.
It gets as far as the "CREATED" log message then hangs as a user tries to
connect and login. So we will be rebooting the server again as it appears
the server is again dead.
I hope the focus of development is first and foremost stability/reliability
since adding in new features to a server that keeps crashing in a production
environment is very troubling.
I am happy to provide more debug info or log info to help, it's just not
clear how to accomplish this. Where can I easily set the debug level?
Any ideas? Let me know.
Thanks,
Dan
-----------------------------------------
Use of email is inherently insecure. Confidential information, including
account information, and personally identifiable information, should not be
transmitted via email, or email attachment. In no event shall Citizens or
any of its affiliates accept any responsibility for the loss, use or misuse
of any information including confidential information, which is sent to
Citizens or its affiliates via email, or email attachment. Citizens does not
guarantee the accuracy of any email or email attachment, that an email will
be received by Citizens or that Citizens will respond to any email.
This email message is confidential and/or privileged. It is to be used by
the intended recipient only. Use of the information contained in this email
by anyone other than the intended recipient is strictly prohibited. If you
have received this message in error, please notify the sender immediately
and promptly destroy any record of this email.
RE: Stability and reliability issues
Posted by Dan <da...@tipjarawards.com>.
The good news is we are now running a test server so we should have a clue
next time an issue arises.
Dan
-----Original Message-----
From: West, John C [mailto:John.C.West@CITIZENSBANK.com]
Sent: April-06-09 2:00 PM
To: ftpserver-users@mina.apache.org
Subject: RE: Stability and reliability issues
Well I'm using this server in a couple different production environments
without any issues and I know there are others on this list who are as well,
so I'd say your experience is not typical.
What version of the ftp server and Java are you using? What operating
system?
The debug level is set in log4j.properties.
-----Original Message-----
From: Dan [mailto:dan@tipjarawards.com]
Sent: Monday, April 06, 2009 1:51 PM
To: ftpserver-users@mina.apache.org
Subject: Stability and reliability issues
We are having some serious stability/scalability issues with the ftp server.
First there were hanging logins (nobody able to login but supposedly max
login users was reacehd according to log message). With idle timeouts this
should never happen as after a few minutes all the "dead" logins should have
been collected.
Second problem we are now getting 'Could not connect to server' and
'Connection timed out' errors with the server running after only two days.
It gets as far as the "CREATED" log message then hangs as a user tries to
connect and login. So we will be rebooting the server again as it appears
the server is again dead.
I hope the focus of development is first and foremost stability/reliability
since adding in new features to a server that keeps crashing in a production
environment is very troubling.
I am happy to provide more debug info or log info to help, it's just not
clear how to accomplish this. Where can I easily set the debug level?
Any ideas? Let me know.
Thanks,
Dan
-----------------------------------------
Use of email is inherently insecure. Confidential information, including
account information, and personally identifiable information, should not be
transmitted via email, or email attachment. In no event shall Citizens or
any of its affiliates accept any responsibility for the loss, use or misuse
of any information including confidential information, which is sent to
Citizens or its affiliates via email, or email attachment. Citizens does not
guarantee the accuracy of any email or email attachment, that an email will
be received by Citizens or that Citizens will respond to any email.
This email message is confidential and/or privileged. It is to be used by
the intended recipient only. Use of the information contained in this email
by anyone other than the intended recipient is strictly prohibited. If you
have received this message in error, please notify the sender immediately
and promptly destroy any record of this email.
RE: Stability and reliability issues
Posted by "West, John C" <Jo...@CITIZENSBANK.com>.
Well I'm using this server in a couple different production environments
without any issues and I know there are others on this list who are as
well, so I'd say your experience is not typical.
What version of the ftp server and Java are you using? What operating
system?
The debug level is set in log4j.properties.
-----Original Message-----
From: Dan [mailto:dan@tipjarawards.com]
Sent: Monday, April 06, 2009 1:51 PM
To: ftpserver-users@mina.apache.org
Subject: Stability and reliability issues
We are having some serious stability/scalability issues with the ftp
server.
First there were hanging logins (nobody able to login but supposedly max
login users was reacehd according to log message). With idle timeouts
this
should never happen as after a few minutes all the "dead" logins should
have
been collected.
Second problem we are now getting 'Could not connect to server' and
'Connection timed out' errors with the server running after only two
days.
It gets as far as the "CREATED" log message then hangs as a user tries
to
connect and login. So we will be rebooting the server again as it
appears
the server is again dead.
I hope the focus of development is first and foremost
stability/reliability
since adding in new features to a server that keeps crashing in a
production
environment is very troubling.
I am happy to provide more debug info or log info to help, it's just not
clear how to accomplish this. Where can I easily set the debug level?
Any ideas? Let me know.
Thanks,
Dan
-----------------------------------------
Use of email is inherently insecure. Confidential information,
including account information, and personally identifiable
information, should not be transmitted via email, or email
attachment. In no event shall Citizens or any of its affiliates
accept any responsibility for the loss, use or misuse of any
information including confidential information, which is sent to
Citizens or its affiliates via email, or email attachment. Citizens
does not guarantee the accuracy of any email or email attachment,
that an email will be received by Citizens or that Citizens will
respond to any email.
This email message is confidential and/or privileged. It is to be
used by the intended recipient only. Use of the information
contained in this email by anyone other than the intended recipient
is strictly prohibited. If you have received this message in error,
please notify the sender immediately and promptly destroy any
record of this email.
Re: Stability and reliability issues
Posted by ga...@aero.bombardier.com.
I have seen similar ocurrences to the "cannot connect to server" incident
mentioned. For us, this was caused by the ftpserver _sometimes_ picking a
(passive) port that our firewall was not allowing through from the client.
I changed the passive port range setting in ftpserver to match the firewall
port range and it has worked ok since. I guess it therefore follows you
could also get this if you have set up a port range and you run out of
ports momentarily under heavy demand. This can also happen with clients
such as filezilla that can open many ports at once to transfer files.
I have also seen the max logins reached error as well for a user account
that was just set up and therefore could not have reached any limit. Since
this was the first occurrence in many months of continuous operation, I
just restarted the server and everything was OK. I might peer more closely
into the source code now.
Best Regards,
Gary Bell
Re: Stability and reliability issues
Posted by Niklas Gustavsson <ni...@protocol7.com>.
On Mon, Apr 6, 2009 at 7:51 PM, Dan <da...@tipjarawards.com> wrote:
> We are having some serious stability/scalability issues with the ftp server.
Let's hope we can help you out.
> First there were hanging logins (nobody able to login but supposedly max
> login users was reacehd according to log message). With idle timeouts this
> should never happen as after a few minutes all the "dead" logins should have
> been collected.
I note you're using RC1, would it be possible for you to upgrade to
1.0.0? A fair amount of issues was fixed in between these versions.
Also, note that the maximum allowed connections are configured both on
the listener and per user, so you might be hitting either limit. Could
we verify that both these settings are correct.
> Second problem we are now getting 'Could not connect to server' and
> 'Connection timed out' errors with the server running after only two days.
> It gets as far as the "CREATED" log message then hangs as a user tries to
> connect and login. So we will be rebooting the server again as it appears
> the server is again dead.
As requested by John, a debug log would be helpful. Also, if you could
provide the output of netstat -a for the port your running FtpServer
on, and lsof for the process in which FtpServer runs.
> I hope the focus of development is first and foremost stability/reliability
> since adding in new features to a server that keeps crashing in a production
> environment is very troubling.
We're hoping to work both on hardening FtpServer, as well as adding
new features. Now, based on the general feedback we're getting on this
list, your seem to be having an unusually hard time with FtpServer,
and I sincerely hope we can help you out.
/niklas
Stability and reliability issues
Posted by Dan <da...@tipjarawards.com>.
We are having some serious stability/scalability issues with the ftp server.
First there were hanging logins (nobody able to login but supposedly max
login users was reacehd according to log message). With idle timeouts this
should never happen as after a few minutes all the "dead" logins should have
been collected.
Second problem we are now getting 'Could not connect to server' and
'Connection timed out' errors with the server running after only two days.
It gets as far as the "CREATED" log message then hangs as a user tries to
connect and login. So we will be rebooting the server again as it appears
the server is again dead.
I hope the focus of development is first and foremost stability/reliability
since adding in new features to a server that keeps crashing in a production
environment is very troubling.
I am happy to provide more debug info or log info to help, it's just not
clear how to accomplish this. Where can I easily set the debug level?
Any ideas? Let me know.
Thanks,
Dan
Re: Maximum login connections: 421
Posted by David Latorre <dv...@gmail.com>.
AKAIK, idleTime should not be a problem. It is true that
ConcurrentLoginPermission() is not in our public API ( you can always
get the source code though, with only the tests you'll learn a big
deal about FtpServer) , the constructor is this:
public ConcurrentLoginPermission(int maxConcurrentLogins,
int maxConcurrentLoginsPerIP) {
this.maxConcurrentLogins = maxConcurrentLogins;
this.maxConcurrentLoginsPerIP = maxConcurrentLoginsPerIP;
}
So in your case you should have authorities.add(new
ConcurrentLoginPermission(8, 4)); to limit the target user to 8
connections with 4 from the same IP adress.
I still think you may need to check how many connections are actually
established! Can you provide us with a 'new log file' in DEBUG mode
reproducing your issue?
2009/4/3 Dan <da...@tipjarawards.com>:
> I set the concurrent logins as follows:
>
> List<Authority> authorities = new ArrayList<Authority>();
>
> authorities.add(new WritePermission());
> authorities.add(new ConcurrentLoginPermission(4, 8));
> authorities.add(new TransferRatePermission(0, 0));
>
> setAuthorities(authorities);
>
> setMaxIdleTime(0);
>
> Is there a problem with the setMaxIdleTime? Otherwise I assume I am setting
> the logins to be a max of 4..or 8, I am not sure since my javadocs don't
> include ConcurrentLoginPermission info!
>
> Thanks,
>
> Dan
>
> -----Original Message-----
> From: David Latorre [mailto:dvlato@gmail.com]
> Sent: April-03-09 1:43 PM
> To: ftpserver-users@mina.apache.org
> Subject: Re: Maximum login connections: 421
>
> Hello Dan,
>
> You also set maximum connections per user in the UserManager ... what value
> did you use in order to configure that? And when FTP Clients open several
> connections, they log you in for each of those connections ... until we
> have an equivalent to admingui which allowed us to monitor all the
> connections you can see if DEBUG log level will help you to find out what's
> your exact problem; otherwise you can use a ftplet that gets triggered
> before "USER" command or something like that :-) And, of course, you can
> debug the server
>
>
>
>
> 2009/4/3 Dan <da...@tipjarawards.com>:
>> I agree, but the docs say "Maximum Logins", not Maximum Connections.
>>
>> Hopefully there are just "logins" that aren't being closed properly
>> over time, although I don't know how to find this out. There should be
>> a way to get status on all logins from the manager, I'm going to keep
> looking.
>>
>> -----Original Message-----
>> From: Steve Winter [mailto:steve@bluecrocodile.co.nz]
>> Sent: April-03-09 11:09 AM
>> To: ftpserver-users@mina.apache.org
>> Subject: Re: Maximum login connections: 421
>>
>> Hi Dan,
>>
>> I know that many ftp clients will open multiple simultaneous
>> connections to a server, so it may be that there are 4 people logged
>> in, each of them with
>> 8 connections open, which may account for this...??
>>
>> Just a random thought...
>>
>> Cheers
>> Steve
>>
>>
>> On 3 Apr 2009, at 15:05, Dan wrote:
>>
>>> I am getting:
>>>
>>> WARNING: SENT: 421 Maximum login limit has been reached.
>>>
>>> I have set the connection configuration as follows:
>>>
>>> ConnectionConfigFactory connectionConfigFactory = new
>>> ConnectionConfigFactory(); connectionConfigFactory.setMaxLogins(32);
>>>
>>> The thing is there aren't even close to 32 people logged in right
>>> now, are there known bugs with having hanging connections etc. that
>>> could cause this?
>>>
>>> Any hints to help debug this in the future?
>>>
>>> Thanks,
>>>
>>> Dan
>>>
>>
>>
>>
>>
>
>
RE: Maximum login connections: 421
Posted by Dan <da...@tipjarawards.com>.
I set the concurrent logins as follows:
List<Authority> authorities = new ArrayList<Authority>();
authorities.add(new WritePermission());
authorities.add(new ConcurrentLoginPermission(4, 8));
authorities.add(new TransferRatePermission(0, 0));
setAuthorities(authorities);
setMaxIdleTime(0);
Is there a problem with the setMaxIdleTime? Otherwise I assume I am setting
the logins to be a max of 4..or 8, I am not sure since my javadocs don't
include ConcurrentLoginPermission info!
Thanks,
Dan
-----Original Message-----
From: David Latorre [mailto:dvlato@gmail.com]
Sent: April-03-09 1:43 PM
To: ftpserver-users@mina.apache.org
Subject: Re: Maximum login connections: 421
Hello Dan,
You also set maximum connections per user in the UserManager ... what value
did you use in order to configure that? And when FTP Clients open several
connections, they log you in for each of those connections ... until we
have an equivalent to admingui which allowed us to monitor all the
connections you can see if DEBUG log level will help you to find out what's
your exact problem; otherwise you can use a ftplet that gets triggered
before "USER" command or something like that :-) And, of course, you can
debug the server
2009/4/3 Dan <da...@tipjarawards.com>:
> I agree, but the docs say "Maximum Logins", not Maximum Connections.
>
> Hopefully there are just "logins" that aren't being closed properly
> over time, although I don't know how to find this out. There should be
> a way to get status on all logins from the manager, I'm going to keep
looking.
>
> -----Original Message-----
> From: Steve Winter [mailto:steve@bluecrocodile.co.nz]
> Sent: April-03-09 11:09 AM
> To: ftpserver-users@mina.apache.org
> Subject: Re: Maximum login connections: 421
>
> Hi Dan,
>
> I know that many ftp clients will open multiple simultaneous
> connections to a server, so it may be that there are 4 people logged
> in, each of them with
> 8 connections open, which may account for this...??
>
> Just a random thought...
>
> Cheers
> Steve
>
>
> On 3 Apr 2009, at 15:05, Dan wrote:
>
>> I am getting:
>>
>> WARNING: SENT: 421 Maximum login limit has been reached.
>>
>> I have set the connection configuration as follows:
>>
>> ConnectionConfigFactory connectionConfigFactory = new
>> ConnectionConfigFactory(); connectionConfigFactory.setMaxLogins(32);
>>
>> The thing is there aren't even close to 32 people logged in right
>> now, are there known bugs with having hanging connections etc. that
>> could cause this?
>>
>> Any hints to help debug this in the future?
>>
>> Thanks,
>>
>> Dan
>>
>
>
>
>
Re: Maximum login connections: 421
Posted by David Latorre <dv...@gmail.com>.
Hello Dan,
You also set maximum connections per user in the UserManager ... what
value did you use in order to configure that? And when FTP Clients
open several connections, they log you in for each of those
connections ... until we have an equivalent to admingui which allowed
us to monitor all the connections you can see if DEBUG log level will
help you to find out what's your exact problem; otherwise you can use
a ftplet that gets triggered before "USER" command or something like
that :-) And, of course, you can debug the server
2009/4/3 Dan <da...@tipjarawards.com>:
> I agree, but the docs say "Maximum Logins", not Maximum Connections.
>
> Hopefully there are just "logins" that aren't being closed properly over
> time, although I don't know how to find this out. There should be a way to
> get status on all logins from the manager, I'm going to keep looking.
>
> -----Original Message-----
> From: Steve Winter [mailto:steve@bluecrocodile.co.nz]
> Sent: April-03-09 11:09 AM
> To: ftpserver-users@mina.apache.org
> Subject: Re: Maximum login connections: 421
>
> Hi Dan,
>
> I know that many ftp clients will open multiple simultaneous connections to
> a server, so it may be that there are 4 people logged in, each of them with
> 8 connections open, which may account for this...??
>
> Just a random thought...
>
> Cheers
> Steve
>
>
> On 3 Apr 2009, at 15:05, Dan wrote:
>
>> I am getting:
>>
>> WARNING: SENT: 421 Maximum login limit has been reached.
>>
>> I have set the connection configuration as follows:
>>
>> ConnectionConfigFactory connectionConfigFactory = new
>> ConnectionConfigFactory(); connectionConfigFactory.setMaxLogins(32);
>>
>> The thing is there aren't even close to 32 people logged in right now,
>> are there known bugs with having hanging connections etc. that could
>> cause this?
>>
>> Any hints to help debug this in the future?
>>
>> Thanks,
>>
>> Dan
>>
>
>
>
>
RE: Maximum login connections: 421
Posted by Dan <da...@tipjarawards.com>.
I agree, but the docs say "Maximum Logins", not Maximum Connections.
Hopefully there are just "logins" that aren't being closed properly over
time, although I don't know how to find this out. There should be a way to
get status on all logins from the manager, I'm going to keep looking.
-----Original Message-----
From: Steve Winter [mailto:steve@bluecrocodile.co.nz]
Sent: April-03-09 11:09 AM
To: ftpserver-users@mina.apache.org
Subject: Re: Maximum login connections: 421
Hi Dan,
I know that many ftp clients will open multiple simultaneous connections to
a server, so it may be that there are 4 people logged in, each of them with
8 connections open, which may account for this...??
Just a random thought...
Cheers
Steve
On 3 Apr 2009, at 15:05, Dan wrote:
> I am getting:
>
> WARNING: SENT: 421 Maximum login limit has been reached.
>
> I have set the connection configuration as follows:
>
> ConnectionConfigFactory connectionConfigFactory = new
> ConnectionConfigFactory(); connectionConfigFactory.setMaxLogins(32);
>
> The thing is there aren't even close to 32 people logged in right now,
> are there known bugs with having hanging connections etc. that could
> cause this?
>
> Any hints to help debug this in the future?
>
> Thanks,
>
> Dan
>
Re: Maximum login connections: 421
Posted by Steve Winter <st...@bluecrocodile.co.nz>.
Hi Dan,
I know that many ftp clients will open multiple simultaneous
connections to a server, so it may be that there are 4 people logged
in, each of them with 8 connections open, which may account for
this...??
Just a random thought...
Cheers
Steve
On 3 Apr 2009, at 15:05, Dan wrote:
> I am getting:
>
> WARNING: SENT: 421 Maximum login limit has been reached.
>
> I have set the connection configuration as follows:
>
> ConnectionConfigFactory connectionConfigFactory = new
> ConnectionConfigFactory();
> connectionConfigFactory.setMaxLogins(32);
>
> The thing is there aren't even close to 32 people logged in right
> now, are
> there known bugs with having hanging connections etc. that could
> cause this?
>
> Any hints to help debug this in the future?
>
> Thanks,
>
> Dan
>