Date: Mon, 6 Jun 2005 21:34:21 +0100 From: Geraint Edwards <gedge-lists@yadn.org> To: Gerhard Schmidt <estartu@augusta.de> Cc: freebsd-python@freebsd.org Subject: Re: new to python/zope - installation woes Message-ID: <20050606203421.GA24268@cymru.serf.org> In-Reply-To: <20050606141759.GA1547@augusta.de> References: <20050603160153.GA56758@cymru.serf.org> <20050606141759.GA1547@augusta.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Gerhard Schmidt <estartu@augusta.de> said (on Mon, Jun 06, 2005 at 04:17:59PM +0200): > On Fri, Jun 03, 2005 at 05:01:53PM +0100, Geraint Edwards wrote: > > However, 'bar' never gets any logs - it all seems to go to > > .../foo/log/... > > and the logs don't get anything interesting in them when things > > go horribly wrong (see later). > > Did you set different ports for both zope servers default is > 8080. If both zope servers are configured for 8080 bar gets > never started, because the port is allready used. Yup - that's exactly what I'd done wrongly. Good spot. > try the bin/runzope script in your instance home. It prints the > debug infomation to stdout. Is very usefull when debug startup problems. That's a good tip - thanks. > Thats a problem of your products. Product dependency are quite a > pain in the ass. Ask your customer about this Products and install > them in <instance_home>/Products. That's what I've done - this is someone else's job to identify. > Running Zope/Plone without inside knowlegde of Zope is not such > a good Idea. You should spend some time and learn about Zope. It seems to be running happily now. I was being over-optimistic/foolish/naive to rush in without more RTFM'ing. Thanks again for all the advice. -- Geraint A. Edwards (aka "Gedge") gedge@yadn.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050606203421.GA24268>