multiple zope instances on one ip address
I am trying to set up more than one zope instance and failing... I have configured two seperate installations (different versions, in fact) of zope, and lets say I try to run one on 192.168.0.1:2000 and the other on 192.168.0.1:8000. If the port 2000 one starts first, it will also answer requests for port 8000. If I then kill the port 2000 one, the port 8000 one will then be able to answer requests. I want both to run without interfering with each other. BTW, I start them with: firstinstance/z2.py -X -w192.168.0.1:2000 -u nobody secondinstance/z2.py -X -w192.168.0.1:8000 -u nobody If this just the way things are, or am I missing something? thanks!
Hi matt, this is a typical "cant be" situation ;) If you really start zope that way, it would work. If you are on linux, try fuser -n tcp 2000 and fuser -n tcp 8000 to see the procids of the processes serving on either port. HTH Tino Wildenhain --On Sonntag, 29. April 2001 08:57 -0700 matt <matt@tidalpool.org> wrote:
I am trying to set up more than one zope instance and failing...
I have configured two seperate installations (different versions, in fact) of zope, and lets say I try to run one on 192.168.0.1:2000 and the other on 192.168.0.1:8000. If the port 2000 one starts first, it will also answer requests for port 8000. If I then kill the port 2000 one, the port 8000 one will then be able to answer requests. I want both to run without interfering with each other.
BTW, I start them with: firstinstance/z2.py -X -w192.168.0.1:2000 -u nobody secondinstance/z2.py -X -w192.168.0.1:8000 -u nobody
If this just the way things are, or am I missing something?
thanks!
_______________________________________________ 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 )
this is a typical "cant be" situation ;) If you really start zope that way, it would work. If you are on linux, try fuser -n tcp 2000 and fuser -n tcp 8000 to see the procids of the processes serving on either port.
fuser confirms that the right set of pythons is attached to each port, but the same behaviour persists. Keep in mind that whatever one starts first serves for both ports, but if it is killed, the other takes over for both ports. They run happily side by side in the meatime, no errors about locked files or whatnot.
Erm... no :) This simply cant be, really :) One zope does not "take over another port" this simply does not happen :-) I do run more then one zope at the same time on different ports and I never saw such behavior. I would like to have a look at your z2.py (both), start (both) and var/Z2.pid (both). Please send them (privately) to me. Please include the output of the fuser-command with the files. HICH Tino --On Montag, 30. April 2001 08:48 -0700 matt <matt@tidalpool.org> wrote:
this is a typical "cant be" situation ;) If you really start zope that way, it would work. If you are on linux, try fuser -n tcp 2000 and fuser -n tcp 8000 to see the procids of the processes serving on either port.
fuser confirms that the right set of pythons is attached to each port, but the same behaviour persists. Keep in mind that whatever one starts first serves for both ports, but if it is killed, the other takes over for both ports. They run happily side by side in the meatime, no errors about locked files or whatnot.
participants (2)
-
matt -
Tino Wildenhain