When I try to start Z Server i get the following error messages: File "/WWW/Docs/product_development/teams/AMD_framework/dev/Zope/ZServer/medusa/asyncore.py", line 205, in bind return self.socket.bind (addr) socket.error: (98, 'Address already in use') I don't use the number 98 in any address or port (http=80, ftp='' and monitor='') so what could this error be about ?
You have another process that is "bind" to port 98... this is the registered port for "tacnews". try "netstat -a" under the shell... ----- Message d'origine ----- De : Ulf Byskov <ulf.byskov@comptel.com> À : <zope@zope.org> Envoyé : lundi 13 mars 2000 11:28 Objet : [Zope] socket problem
When I try to start Z Server i get the following error messages:
File
"/WWW/Docs/product_development/teams/AMD_framework/dev/Zope/ZServer/medusa/a syncore.py",
line 205, in bind return self.socket.bind (addr) socket.error: (98, 'Address already in use')
I don't use the number 98 in any address or port (http=80, ftp='' and monitor='') so what could this error be about ?
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Olivier Deckmyn wrote:
You have another process that is "bind" to port 98...
this is the registered port for "tacnews".
try "netstat -a" under the shell...
You know, I have a similar problem... I have 6 aliased IP addresses. I'm running 3 zopes, at the moment. All of them have been told what IP address to use. The first can listen to 8099 and 8021 no problem, but the rest of them complain. if I do -f '' and -m '' everything is fine, but they're all listening to 8080, so what's the gig? netstat shows localhost:8099 and *:8021, and the same for the other server that I set to 9023 and 9023 respectively. Does Zserver listen indiscriminately on ftp and monitor? -- mindlace@imeme.net good design is as close as I want to get to ideology.
mindlace wrote:
Olivier Deckmyn wrote:
You have another process that is "bind" to port 98...
this is the registered port for "tacnews".
try "netstat -a" under the shell...
You know, I have a similar problem... I have 6 aliased IP addresses. I'm running 3 zopes, at the moment. All of them have been told what IP address to use. The first can listen to 8099 and 8021 no problem, but the rest of them complain.
if I do -f '' and -m '' everything is fine, but they're all listening to 8080, so what's the gig?
netstat shows localhost:8099 and *:8021, and the same for the other server that I set to 9023 and 9023 respectively.
Does Zserver listen indiscriminately on ftp and monitor?
The FTP handler does not accept a hostname argument in it's constructor. This is probably an artifact of the medusa code. Shouldn't be a hard fix. The monitor server is hardwired to localhost. I believe this was a security decision. You can hack z2.py any way you like to remedy it. -Michel
participants (4)
-
Michel Pelletier -
mindlace -
Olivier Deckmyn -
Ulf Byskov