Fresh install fails in minutes
I've just set up a fresh new Red Hat 9 installation, and dropped in a fresh install of Zope 2.6.1 (from the binary tarball on the Zope site, which I believe includes its own Python interpreter). I'm currently testing it out by starting it like this: su - zope -s /bin/sh -c "/opt/zope/start" Yes, the /opt/zope/var directory is properly owned by the zope user. It works fine for a few minutes, but after I poke around a bit (especially once I hit the management interface), it suddenly stops responding to requests. The process is still running, and it's still accepting connections, but it completely ignores those connections. Nothing is logged (not even the requests I'm making) after it stops responding. I'm running it through Apache via FastCGI, but I've also tried running only the HTTP server on port 8080, and the same thing happens there. Any ideas what I should be looking for? -- Take care, Scott \\'unsch ... Oh give me a phone, with a modem on loan...
Scott Wunsch wrote:
I've just set up a fresh new Red Hat 9 installation, and dropped in a fresh install of Zope 2.6.1 (from the binary tarball on the Zope site,
Maybe you should read the mail archives and stop using a broken OS ;-) cheers, Chris
This question has been answered already today. Look through the archives. -aj --On Donnerstag, 22. Mai 2003 9:56 Uhr -0600 Scott Wunsch <zope@tracking.wunsch.org> wrote:
I've just set up a fresh new Red Hat 9 installation, and dropped in a fresh install of Zope 2.6.1 (from the binary tarball on the Zope site, which I believe includes its own Python interpreter). I'm currently testing it out by starting it like this:
su - zope -s /bin/sh -c "/opt/zope/start"
Yes, the /opt/zope/var directory is properly owned by the zope user.
It works fine for a few minutes, but after I poke around a bit (especially once I hit the management interface), it suddenly stops responding to requests. The process is still running, and it's still accepting connections, but it completely ignores those connections. Nothing is logged (not even the requests I'm making) after it stops responding. I'm running it through Apache via FastCGI, but I've also tried running only the HTTP server on port 8080, and the same thing happens there.
Any ideas what I should be looking for?
-- Take care, Scott \\'unsch
... Oh give me a phone, with a modem on loan...
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Scott Wunsch wrote:
I've just set up a fresh new Red Hat 9 installation, and dropped in a fresh install of Zope 2.6.1 (from the binary tarball on the Zope site, which I believe includes its own Python interpreter). I'm currently testing it out by starting it like this:
su - zope -s /bin/sh -c "/opt/zope/start"
Yes, the /opt/zope/var directory is properly owned by the zope user.
It works fine for a few minutes, but after I poke around a bit (especially once I hit the management interface), it suddenly stops responding to requests. The process is still running, and it's still accepting connections, but it completely ignores those connections. Nothing is logged (not even the requests I'm making) after it stops responding. I'm running it through Apache via FastCGI, but I've also tried running only the HTTP server on port 8080, and the same thing happens there.
Any ideas what I should be looking for?
Download RedHat 9.0 RPM from http://www.zope.org/Members/medienlabor/packages and look into /usr/share/doc/zope/README.RedHat Cheers, M.
Scott Wunsch wrote at 2003-5-22 09:56 -0600:
I've just set up a fresh new Red Hat 9 installation, and dropped in a fresh install of Zope 2.6.1.... ... It works fine for a few minutes, but after I poke around a bit (especially once I hit the management interface), it suddenly stops responding to requests.
Apparently, the Redhat 9 "pthreads" library is buggy. Search the archives to learn how to work around this bug. Dieter
participants (5)
-
Andreas Jung -
Chris Withers -
Dieter Maurer -
Marcus Schopen -
Scott Wunsch