On Fri, Aug 03, 2001 at 04:08:15PM -0300, Ben Armstrong wrote: > On Fri, Aug 03, 2001 at 08:24:55PM +0200, Stefan Heimann wrote: > > > # zopectl start > > > Starting Zope........................................ failed. > > > > Maybe another service uses the ports (for http it's usually 8080, for > > fto 8021) Zope tries to listen on. > > Nope, that's not it. Zope has changed the default to one that is > unlikely to conflict. Also, I verified that the port Zope is looking > for (port 9673) is not being used with netstat beforehand. > > In any event, what I really need to know is how to get this thing to > speak to me ... I see a /var/lib/zope/var/Z2.log, and can see on my > running server the web server accesses, but on the failed server, this > log is empty (as I would expect it to be ... as it merely records > accesses). How can I get Zope to "spill its guts" about what it is > doing on startup? There's no -v switch or anything like that in > zopectl. >
Do you have another PPC machine you can test this on? Have you ruled out any hardware problems? Can you use a simple tcp/udp tool (like netcat) to bind to the needed port? Did you try a custom kernel? Mike
