At 02:27 PM 11/23/99 , Steen Suder , Zope list <zope@zope.org> wrote:
At 12:54 PM 11/23/99 , Steen Suder wrote:
The following snip is taken from the console of our Zope server after a crash (or whatever it was):
[root@getafix ZOPE-2.0.0]# /opt/mtg/Z/ZOPE-2.0.0/start [root@getafix ZOPE-2.0.0]# NOTICE: BeginTransactionBlock and not in default state NOTICE: EndTransactionBlock and not inprogress/abort state NOTICE: BeginTransactionBlock and not in default state NOTICE: EndTransactionBlock and not inprogress/abort state NOTICE: BeginTransactionBlock and not in default state NOTICE: EndTransactionBlock and not inprogress/abort state NOTICE: BeginTransactionBlock and not in default state NOTICE: EndTransactionBlock and not inprogress/abort state
I know it's only Zope 2.0.0; I'm waiting for 2.1. Zope was started _without_ the -D switch. OS is RedHat 6.0 / i386.
I'm curious to know what this is all about; can someone enlighten me?
It's a known bug, that is fixed in 2.1.0.
Oops, I'm babling. It looks like a known bug in Zope, but actually this one is different. These are messages from PostgreSQL. They appear when no transaction in PostgreSQL was started because PostgreSQL doesn't start one until there is something to roll back, or something along these lines. If an error occurs somewhere else in Zope, and your transaction is rolled back, PostgreSQL throws above warning to tell you that it didn't see anything waranting a rollback. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------