I have kind of a stupid question about sockets. When starting zope (using z2.py -D) I get: ------ 2000-03-25T18:56:54 PROBLEM(100) ZServer Computing default hostname ------ 2000-03-25T18:56:54 INFO(0) ZServer Medusa (V1.13) started at Sat Mar 25 10:56:54 2000 Hostname: milo Port:8080 ------ 2000-03-25T18:56:54 INFO(0) ZServer FTP server started at Sat Mar 25 10:56:54 2000 Authorizer:None Hostname: milo Port: 8021 ------ 2000-03-25T18:56:54 INFO(0) ZServer PCGI Server started at Sat Mar 25 10:56:54 2000 Unix socket: /usr/local/src/Zope-2.1.4-src/var/pcgi.soc Traceback (innermost last): File "/usr/local/src/Zope-2.1.4-src/z2.py", line 551, in ? port=MONITOR_PORT) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line 264, in __init__ monitor_server.__init__ (self, hostname, port) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line 168, in __init__ self.bind ((hostname, port)) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/asyncore.py", line 205, in bind return self.socket.bind (addr) socket.error: (49, "Can't assign requested address") Using z2.py -D -m '' (disabling the monitor), everything works fine. (Except no monitor, obviously). Using -m with other socket numbers results in the same error. (49, "Can't... ). FreeBSD 3.4, Zope 2.1.4, running as root. Any ideas what to try? I would like to use the monitor, if just for the coolness factor. Thanks in advance. Patrick Lewis <pl@teleport.com>
Patrick Lewis wrote:
Using z2.py -D -m '' (disabling the monitor), everything works fine. (Except no monitor, obviously). Using -m with other socket numbers results in the same error. (49, "Can't... ).
netstat -a should tell you what ports are being listened to. try ./start -m '9898' and if it works, well, then you've probably got something listening to the monitor port. Note that while http can be virtualized (listen on selective IP's), monitor and ftp cannot, so you have to pick your ports accordingly. ethan fremen -- http://mindlace.net __________________ mindlace@imeme.net I don't want The Truth but I wouldn't mind a Big Analogy.
On Sun, Mar 26, 2000 at 04:56:15AM +0000, mindlace wrote:
Patrick Lewis wrote:
Using z2.py -D -m '' (disabling the monitor), everything works fine. (Except no monitor, obviously). Using -m with other socket numbers results in the same error. (49, "Can't... ).
netstat -a should tell you what ports are being listened to. try ./start -m '9898' and if it works, well, then you've probably got something listening to the monitor port.
Note that while http can be virtualized (listen on selective IP's), monitor and ftp cannot, so you have to pick your ports accordingly.
ethan fremen
netstat -a shows only ssh, http, smtp, sunrpc, and syslog sockets open. Nothing too wierd. Like I said, using other socket numbers (e.g. 9898) doesn't seem to fix it.
Ok, I was able to solve my problem, so for future generations, here it goes. My loopback device (lo0) was not configured properly. Apparently, the monitor attaches to the localhost via the loopback device. I fixed lo0, and now everything works great. Thanks to everyone who gave hints where to look. On Sat, Mar 25, 2000 at 11:10:03AM -0800, Patrick Lewis wrote:
I have kind of a stupid question about sockets. When starting zope (using z2.py -D) I get:
<SNIP>
------ 2000-03-25T18:56:54 INFO(0) ZServer PCGI Server started at Sat Mar 25 10:56:54 2000 Unix socket: /usr/local/src/Zope-2.1.4-src/var/pcgi.soc Traceback (innermost last): File "/usr/local/src/Zope-2.1.4-src/z2.py", line 551, in ? port=MONITOR_PORT) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line 264, in __init__ monitor_server.__init__ (self, hostname, port) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/monitor.py", line 168, in __init__ self.bind ((hostname, port)) File "/usr/local/src/Zope-2.1.4-src/ZServer/medusa/asyncore.py", line 205, in bind return self.socket.bind (addr) socket.error: (49, "Can't assign requested address")
Using z2.py -D -m '' (disabling the monitor), everything works fine. (Except no monitor, obviously). Using -m with other socket numbers results in the same error. (49, "Can't... ).
FreeBSD 3.4, Zope 2.1.4, running as root. Any ideas what to try? I would like to use the monitor, if just for the coolness factor.
participants (3)
-
mindlace -
Patrick Lewis -
Patrick Lewis