Gfw 2.0.9 stops listening after a while on TCP port (GNTP)

[FloW]

Hi there,

I'm setting up gfw to act as an alert collector and relay growl messages to other computers.

Every day, after a few hours, gfw stops listening to incoming connections on tcp/23053 (the port is not listed as "listening" when I run a nestat -an). If I stop and start gfw again, the port opens again and the notifications are being sent and received properly.

The version installed is Growl v.2.0.9 on Windows XP - no firewall.

Do you have any suggestion or idea as where the problem might be located ?

Thank you.

Regards,

Florent

[Brian Dunnington]

That is not a problem I have encountered or had anyone else report to me. I leave Growl running for days or weeks at a time and havent seen this issue, so nothing springs to mind off the top of my head.

Do you get a lot of notifications in the timeframe when GfW *is* listening? Or do most of your notifications come from a single app? I am wondering if maybe a sending app is leaving the socket open or in a funny state, causing it to be shutdown by the OS? Could be something else, just throwing ideas out at this point.

--
You received this message because you are subscribed to the Google Groups "growl for windows" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growl-for-windows/-/htMsrsWsau8J.
To post to this group, send email to growl-fo...@googlegroups.com.
To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.

[FloW]

Hi,

Thank you for your reply.

I only send test notifications from time to time for now.

I do have a lot of computers (somewhere between 40 and 60) that try to subscribe to my relay but fail because they do not have the correct password. I just restarted growl and ran netstat -an periodically to see the amount of connections.

It seems tat there is a lot of TCP connectins between my relay and te other machines that have the incorrect password setup that stay open.

For instance, after 10 minutes of running, I have over 80 connections in TIME WAIT status - a lot of them are to-from the same IP address  - below is a small extract :
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.2:49612     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.2:49623     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.2:49626     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.2:49627     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.5:64006     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.9:60053     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.9:60072     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.9:60089     TIME_WAIT
  TCP    172..xxx.xxx.3:23053     172..xxx.xxx.9:60106     TIME_WAIT

Could this be the problem? Shouldn't GfW close the connection instead of leaving it open?

Le lundi 21 mai 2012 20:30:12 UTC+2, briandunnington a écrit :

That is not a problem I have encountered or had anyone else report to me. I leave Growl running for days or weeks at a time and havent seen this issue, so nothing springs to mind off the top of my head.

Do you get a lot of notifications in the timeframe when GfW *is* listening? Or do most of your notifications come from a single app? I am wondering if maybe a sending app is leaving the socket open or in a funny state, causing it to be shutdown by the OS? Could be something else, just throwing ideas out at this point.

On Mon, May 21, 2012 at 6:34 AM, FloW <floren...@netasq.com> wrote:

Hi there,

I'm setting up gfw to act as an alert collector and relay growl messages to other computers.

Every day, after a few hours, gfw stops listening to incoming connections on tcp/23053 (the port is not listed as "listening" when I run a nestat -an). If I stop and start gfw again, the port opens again and the notifications are being sent and received properly.

The version installed is Growl v.2.0.9 on Windows XP - no firewall.

Do you have any suggestion or idea as where the problem might be located ?

Thank you.

Regards,

Florent

--
You received this message because you are subscribed to the Google Groups "growl for windows" group.
To view this discussion on the web visit https://groups.google.com/d/msg/growl-for-windows/-/htMsrsWsau8J.

To post to this group, send email to growl-for-windows@googlegroups.com.
To unsubscribe from this group, send email to growl-for-windows+unsubscribe@googlegroups.com.