Console messages; what does these mean?
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? -- Best regards / Mvh., Steen Suder Linux Systems Administrator sfs@sciatl.dk
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. -- 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 ------------------------------------------
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 ------------------------------------------
On Tue, Nov 23, 1999 at 05:25:08PM +0100, Martijn Pieters wrote:
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
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.
Steen & Martjin - Yes, these messages are coming from PostgreSQL. I've observed them when trying to get the DA to work better with the Zope 2.0 transaction machinery. As far as I remember, once a transaction has been rolled back through a ZPygreSQLDA, Zope never puts that connection back in 'transaction' mode: i.e. it never calls the _begin, _finish, (or _abort) methods of the DB at transaction boundries. I can trigger this by making an SQL syntax error in a ZSQL method. Only way I could get things back in sync was to use the DAs management interface to close and reopen the DB connection. This is the primary reason the version of this DA on my www.zope.org page is marked 'beta'. Ross -- Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu> NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005
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
These messages are not from Zope code. They look like they might be coming from an external database. Are you using an SQL database with Zope? Jim -- Jim Fulton mailto:jim@digicool.com Technical Director (888) 344-4332 Python Powered! Digital Creations http://www.digicool.com http://www.python.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
On Tue, 23 Nov 1999, Jim Fulton wrote:
[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
These messages are not from Zope code. They look like they might be coming from an external database. Are you using an SQL database with Zope?
I bet it's Postgres (I see these messages too). You can verify it by going into psql and executing a rollback without a "begin". -Petru
participants (5)
-
Jim Fulton -
Martijn Pieters -
Petru Paler -
Ross J. Reedstrom -
Steen Suder