public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Scislowicz <adams@fourelle.com>
To: linux-kernel@vger.kernel.org
Subject: dead programs LISTEN sockets remain in netstat (Kernel Version 2.4.18-rc4 SMP)
Date: Wed, 04 Sep 2002 18:54:56 -0700	[thread overview]
Message-ID: <3D76B970.8080709@fourelle.com> (raw)

Quick Summary: Rarely, but several times in the past few weeks now after 
I kill off a process nicely(SIGTERM) its LISTEN sockets remain open...

Some Detail: Because of this, Squid or our server side app cannot 
respawn(cannot bind to socket as it's in use), sometimes its squid's 
socket that remains in the LISTEN state and other times it's been out 
server side app. These are the apps running on our servers which are 
restarted most often. I don't see how an application could be 
responsible for this behaviour after it is dead. So now I look to the 
kernel ;)

My diagnostics below:

lsof -n -P | grep 9000 finds nothing, however netstate shows TCP/9000 in 
listen state w/ no parent program?
**** NETSTAT OUTPUT ****
bash-2.04# netstat -antp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         
State       PID/Program name  
tcp        0      0 0.0.0.0:8001            0.0.0.0:*               
LISTEN      -                  
tcp        0      0 127.0.0.1:9666          0.0.0.0:*               
LISTEN      9826/lcdd          
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               
LISTEN      -                  
tcp        0      0 0.0.0.0:8008            0.0.0.0:*               
LISTEN      -                  
tcp        0      0 127.0.0.1:9875          0.0.0.0:*               
LISTEN      -                  
...
**** END OF NETSTAT OUTPUT ****

ps aux reports no zombie processes...

any help? do you need more info? I have a system in this state now.

thank you :)
/)dam.. .  . d o n ' t   s t o p.


                 reply	other threads:[~2002-09-05  1:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D76B970.8080709@fourelle.com \
    --to=adams@fourelle.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox