'Address already in use' error

I've been developing a pylons app for a while now locally
under OS X
and all seems fine, but recently I've started getting this
error when
I try to start the server:

  File
"/Library/Frameworks/Python.framework/Versions/2.4//lib
/
python2.4/SocketServer.py", line 341, in server_bind
    self.socket.bind(self.server_address )
  File "<string>", line 1, in bind
socket.error: (48, 'Address already in use')

I had this error a while back and after a restart of my
machine it
went away, but now it is there permanently.

Can anyone help me understand what this is? My searches so
far have
proved fruitless.

Thanks,
Dave


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

There must be other python/paster processes running
somewhere. Do a
"ps -aux | grep python" and kill them, as
appropriate.


On 5/27/07, Dave <dave.w.evansgmail.com> wrote:
>
> I've been developing a pylons app for a while now
locally under OS X
> and all seems fine, but recently I've started getting
this error when
> I try to start the server:
>
>   File
"/Library/Frameworks/Python.framework/Versions/2.4//lib
/
> python2.4/SocketServer.py", line 341, in
server_bind
>     self.socket.bind(self.server_address )
>   File "<string>", line 1, in bind
> socket.error: (48, 'Address already in use')
>
> I had this error a while back and after a restart of my
machine it
> went away, but now it is there permanently.
>
> Can anyone help me understand what this is? My searches
so far have
> proved fruitless.
>
> Thanks,
> Dave
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

one thing, just using kill <process number> on Linux,
you would have
to use kill -9, maybe its the same on OSX

On May 27, 8:01 pm, Anil <replic...gmail.com> wrote:
> There must be other python/paster processes running
somewhere. Do a
> "ps -aux | grep python" and kill them, as
appropriate.
>
> On 5/27/07, Dave <dave.w.ev...gmail.com> wrote:
>
>
>
> > I've been developing a pylons app for a while now
locally under OS X
> > and all seems fine, but recently I've started
getting this error when
> > I try to start the server:
>
> >   File
"/Library/Frameworks/Python.framework/Versions/2.4//lib
/
> > python2.4/SocketServer.py", line 341, in
server_bind
> >     self.socket.bind(self.server_address )
> >   File "<string>", line 1, in
bind
> > socket.error: (48, 'Address already in use')
>
> > I had this error a while back and after a restart
of my machine it
> > went away, but now it is there permanently.
>
> > Can anyone help me understand what this is? My
searches so far have
> > proved fruitless.
>
> > Thanks,
> > Dave


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

On Sun, May 27, 2007 at 01:55:55PM -0700, voltron wrote:
> one thing, just using kill <process number> on
Linux, you would have
> to use kill -9, maybe its the same on OSX

Better not. Sending the signal 9 (SIGKILL) is a very harsh
way that may
even lead to inconsistencies and make you need to reboot the
system.
Use a normal kill without any signal number and you should
be fine.

I have many coworkers who are so used to blindly sending
signals 9
around and wonder why their systems become instable. 

 Christoph


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

On 5/27/07, Christoph Haas <emailchristoph-haas.de>
wrote:
>
> On Sun, May 27, 2007 at 01:55:55PM -0700, voltron
wrote:
> > one thing, just using kill <process number>
on Linux, you would have
> > to use kill -9, maybe its the same on OSX
>
> Better not. Sending the signal 9 (SIGKILL) is a very
harsh way that may
> even lead to inconsistencies and make you need to
reboot the system.
> Use a normal kill without any signal number and you
should be fine.
>
> I have many coworkers who are so used to blindly
sending signals 9
> around and wonder why their systems become instable.


I remember reading this great rant somewhere about the
harmfulness of
using kill -9.  The post went so far as to say that if you
actually
need to use kill -9, you should just uninstall the software
because
it's garbage to begin with.  Alas, I couldn't find it via a
quick
google.

Happy Hacking!
-jj

-- 
http://jjinux.blogspot.co
m/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Yes, actually I read up about the dangers of using kill -9,
but what
do you do when kill does not work as I mentioned? I found no
other way
to kill these renegade Paster server processes.

I also found out that these Zombies are caused when using
the --reload
switch, if something goes wrong, youŽll have 5 or 6 of em
stacked,
kill one process, the others are there, kill the others,
check up the
"killed" and surprisingly, they are
"awake" again.





On May 28, 8:24 am, "Shannon -jj Behrens"
<jji...gmail.com> wrote:
> On 5/27/07, Christoph Haas <e...christoph-haas.de> wrote:
>
>
>
> > On Sun, May 27, 2007 at 01:55:55PM -0700, voltron
wrote:
> > > one thing, just using kill <process
number> on Linux, you would have
> > > to use kill -9, maybe its the same on OSX
>
> > Better not. Sending the signal 9 (SIGKILL) is a
very harsh way that may
> > even lead to inconsistencies and make you need to
reboot the system.
> > Use a normal kill without any signal number and
you should be fine.
>
> > I have many coworkers who are so used to blindly
sending signals 9
> > around and wonder why their systems become
instable. 
>
> I remember reading this great rant somewhere about the
harmfulness of
> using kill -9.  The post went so far as to say that if
you actually
> need to use kill -9, you should just uninstall the
software because
> it's garbage to begin with.  Alas, I couldn't find it
via a quick
> google.
>
> Happy Hacking!
> -jj
>
> --http://jjinux.blogspot.co
m/


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Thanks for the response, unfortunately I can't see any
processes
specific to python or paster. I have changed my ini file to
use port
5001 and it works again, but it would be nice to work out
what is
causing the problem.

Can I tell which processes are using which ports? I thought
netstat
would show me something using port 5000 but it doesn't seem
to list
any.

Dave

On May 27, 7:01 pm, Anil <replic...gmail.com> wrote:
> There must be other python/paster processes running
somewhere. Do a
> "ps -aux | grep python" and kill them, as
appropriate.
>
> On 5/27/07, Dave <dave.w.ev...gmail.com> wrote:
>
>
>
> > I've been developing a pylons app for a while now
locally under OS X
> > and all seems fine, but recently I've started
getting this error when
> > I try to start the server:
>
> >   File
"/Library/Frameworks/Python.framework/Versions/2.4//lib
/
> > python2.4/SocketServer.py", line 341, in
server_bind
> >     self.socket.bind(self.server_address )
> >   File "<string>", line 1, in
bind
> > socket.error: (48, 'Address already in use')
>
> > I had this error a while back and after a restart
of my machine it
> > went away, but now it is there permanently.
>
> > Can anyone help me understand what this is? My
searches so far have
> > proved fruitless.
>
> > Thanks,
> > Dave


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

netstat -lp

 this will show you pid and process name

 CS

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

If you're getting this with "paster serve
--reload" after you quit the
application and try to restart it, the problem seems to be
in the OS.
On Linux Ubuntu it quits properly, but on Linux Gentoo it
leaves
threads running.

If you're getting it with "paster serve
--monitor-restart", it's
probably related to the problem I mentioned in another
thread
("Daemonizing and auto-restart"): the application
successfully starts
but Paste for some reason doesn't think it has, so it
deletes the PID,
which causes it to start again, which raises a "port
already in use"
error, so it deletes the PID and starts again, which raises
a "port
already in use" error...

On 5/28/07, Cezary Statkiewicz <c.statkiewiczgmail.com> wrote:
>
> netstat -lp
>
>  this will show you pid and process name

I use "lsof -i 111.222.333.444:8080" but netstat may
be more convenient.

-- 
Mike Orr <sluggostergmail.com>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "pylons-discuss" group.
To post to this group, send email to pylons-discussgooglegroups.com
To unsubscribe from this group, send email to
pylons-discuss-unsubscribegooglegroups.com
For more options, visit this group at h
ttp://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---