Exiting SocketServer: socket.error: (98, 'Address already in use')

[Magnus Lycka]

I have a socket server like below which I want to exit when
it's out of data. If I interrupt the client, I'll get a
broken pipe on the server side, and after a Ctrl-C, I can
restart the server again, but if I let it run out of data,
and exit via handle_error as can be seen below, I will get
a socket.error: (98, 'Address already in use') when I try
to restart the server. (Unless I wait a minute or so, or
use another port.) I feel like I'm waving a dead chicken
here. I can't seem to find any proper description on how to
handle this in the docs for SocketServer or socket, and my
futile experiments seem to lead nowhere... Neither Nutshell
nor the Essential Reference helped me solve this.

I'm using Python 2.2.3 on Linux. Why doesn't my socket
get released by the OS when I exit via my handle_error?

class MyRequestHandle r(SocketServer. BaseRequestHand ler):
def handle(self):
while True:
[snip]
try:
[snip]
except [snip]:
# Done!
# Uncommenting the next line makes no difference
# self.request.cl ose()
sys.exit()

class ExitableSocketS erver(SocketSer ver.TCPServer):
def handle_error(se lf, request, client_address) :
exc_info = sys.exc_info()
if exc_info and isinstance(exc_ info[1], SystemExit):
request.shutdow n(2)
request.close()
del request
self.socket.shu tdown(2)
self.socket.clo se()
del self.socket
sys.exit()
SocketServer.TC PServer.handle_ error(self, request, client_address)

....

server = ExitableSocketS erver(('', port), MyRequestHandle r)
server.serve_fo rever()

[Dennis Lee Bieber]

On Mon, 30 May 2005 20:04:02 +0200, Magnus Lycka <ly***@carmen.s e>
declaimed the following in comp.lang.pytho n:

I'm using Python 2.2.3 on Linux. Why doesn't my socket
get released by the OS when I exit via my handle_error?
Not a Python problem...

Normal socket behavior IS to lock out for some period of time.

Check the options available when creating the socket. (I'm not
heavily familiar with socket programming, hence the vagueness) Some
option for "Reuse Address"...

SO_REUSEADDR is the constant in socket.h... And appears to be
visible in socket.py

-- =============== =============== =============== =============== == <
wl*****@ix.netc om.com | Wulfraed Dennis Lee Bieber KD6MOG <
wu******@dm.net | Bestiaria Support Staff <
=============== =============== =============== =============== == <
Home Page: <http://www.dm.net/~wulfraed/> <
Overflow Page: <http://wlfraed.home.ne tcom.com/> <

[Andrew Dalke]

Magnus Lyckå wrote:

Why doesn't my socket
get released by the OS when I exit via my handle_error?

Hi Magnus,

I wrote about this at
http://www.dalkescientific.com/writi...ng_xmlrpc.html

The reason for it is described at
http://hea-www.harvard.edu/~fine/Tech/addrinuse.html

You can set the class variable "allow_reuse_ad dress = True" in
your derived ExitableSocketS erver to get the behaviour you
expect, at the expense of some problems mentioned in the
above URL.

Andrew
da***@dalkescie ntific.com

[Magnus Lycka]

Thank's a lot Andrew and Dennis.

Andrew Dalke wrote:

You can set the class variable "allow_reuse_ad dress = True" in
your derived ExitableSocketS erver to get the behaviour you
expect, at the expense of some problems mentioned in the
above URL.

Ok. I added a STOP message to my protocol, so now the client
shuts down the socket first (when it has read the STOP), and
then it seems to work much better. What I did, in case the
client gets behind, was this in my handle method: I send a STOP
message repeatedly with a delay. When the client gets the first
one, it will close the socket, and I will get an exception the
next time I try to send. This seems to work well, without
(I hope) introducing any new potential problems.

....
delay = 1
print "No more data to serve. Send STOP message."
print "Waiting for client to close socket."
while 1:
try:
self.request.se nd("STOP\n")
time.sleep(dela y)
print '.'
finally:
sys.exit()