Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Tue, Apr 01, 2008 at 01:39:19AM -0700, Steve Langasek wrote: Still reproducible. Any oddness with ./test_mutex -t 5 in the obj/ directory of a 4.6.21-7 source tree after a debian/rules build ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Thu, Mar 27, 2008 at 07:41:58AM -0400, Clint Adams wrote: On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote: I'm afraid it's still reproducible for me with 4.6.21-6. How about 4.6.21-7? Still reproducible. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote: I'm afraid it's still reproducible for me with 4.6.21-6. How about 4.6.21-7? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: [Pkg-db-devel] Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Mon, Mar 10, 2008 at 09:31:52PM -0400, Clint Adams wrote: On Fri, Mar 07, 2008 at 05:03:54PM -0800, Steve Langasek wrote: For my part, I don't know. A search on bugs.python.org does turn up this entry, which looks like it might be related: http://bugs.python.org/issue834461 I don't know that this explains the empty results from d.get(), but it may explain the deadlock mentioned in my last message, as the concurrent reader threads do use cursors. Are the python codepaths identical between hash and btree other than the constant, with regard to cursors or othrewise? Yes; the classes for the tests are defined as: class BTreeSimpleThreaded(SimpleThreadedBase): dbtype = db.DB_BTREE class HashSimpleThreaded(SimpleThreadedBase): dbtype = db.DB_HASH Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: [Pkg-db-devel] Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Fri, Mar 07, 2008 at 05:03:54PM -0800, Steve Langasek wrote: For my part, I don't know. A search on bugs.python.org does turn up this entry, which looks like it might be related: http://bugs.python.org/issue834461 I don't know that this explains the empty results from d.get(), but it may explain the deadlock mentioned in my last message, as the concurrent reader threads do use cursors. Are the python codepaths identical between hash and btree other than the constant, with regard to cursors or othrewise? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Thu, Mar 06, 2008 at 05:39:19PM -0500, Clint Adams wrote: On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote: I'm afraid it's still reproducible for me with 4.6.21-6. Okay. Do we know what's happening unexpectedly? The failing test is HashSimpleThreaded.test02_SimpleLocks; it starts five threads that try to write to a database of (python) type db.DB_HASH using no transactions, and occasionally reads back the results. The reading fails intermittently, with d.get() returning None instead of the value that was (supposed to be) written. All database operations are wrapped with a helper function that does exponential backoff in the case of DB_LOCK_DEADLOCK. I've seen some cases where the threads aborted with a deadlock error instead, which shouldn't be happening often enough to be worth noting: Exception in thread reader 2: Traceback (most recent call last): File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 486, in __bootstrap_inner self.run() File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 446, in run self.__target(*self.__args, **self.__kwargs) File Lib/bsddb/test/test_thread.py, line 282, in readerThread rec = dbutils.DeadlockWrap(c.next, max_retries=10) File /home/devel/canonical/python2.5-2.5.2/Lib/bsddb/dbutils.py, line 62, in DeadlockWrap return function(*_args, **_kwargs) DBLockDeadlockError: (-30995, 'DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock') The same test case using DB_BTREE works reliably, AFAICS. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Fri, Mar 07, 2008 at 12:40:08AM -0800, Steve Langasek wrote: The failing test is HashSimpleThreaded.test02_SimpleLocks; it starts five threads that try to write to a database of (python) type db.DB_HASH using no transactions, and occasionally reads back the results. The reading fails intermittently, with d.get() returning None instead of the value that was (supposed to be) written. Okay. Before I try to (blindly) extract a C testcase from that, is there any record of this problem on bugs.python.org or the Oracle web forum? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Fri, Mar 07, 2008 at 10:49:47AM -0500, Clint Adams wrote: On Fri, Mar 07, 2008 at 12:40:08AM -0800, Steve Langasek wrote: The failing test is HashSimpleThreaded.test02_SimpleLocks; it starts five threads that try to write to a database of (python) type db.DB_HASH using no transactions, and occasionally reads back the results. The reading fails intermittently, with d.get() returning None instead of the value that was (supposed to be) written. Okay. Before I try to (blindly) extract a C testcase from that, is there any record of this problem on bugs.python.org or the Oracle web forum? For my part, I don't know. A search on bugs.python.org does turn up this entry, which looks like it might be related: http://bugs.python.org/issue834461 I don't know that this explains the empty results from d.get(), but it may explain the deadlock mentioned in my last message, as the concurrent reader threads do use cursors. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Wed, Mar 05, 2008 at 01:31:00PM -0800, Steve Langasek wrote: Overriding this check and building against db4.6 leads to the following (intermittent) test failure on SMP systems: Can someone with an SMP system that exhibits this behavior try the python testsuite with libdb4.6 4.6.21-6 in case #469602 is related? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Thu, Mar 06, 2008 at 03:12:04PM -0500, Clint Adams wrote: On Wed, Mar 05, 2008 at 01:31:00PM -0800, Steve Langasek wrote: Overriding this check and building against db4.6 leads to the following (intermittent) test failure on SMP systems: Can someone with an SMP system that exhibits this behavior try the python testsuite with libdb4.6 4.6.21-6 in case #469602 is related? I'm afraid it's still reproducible for me with 4.6.21-6. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
On Thu, Mar 06, 2008 at 09:51:00PM +, Steve Langasek wrote: I'm afraid it's still reproducible for me with 4.6.21-6. Okay. Do we know what's happening unexpectedly? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
FWIW, here's the problem with db4.6 in python. Upstream has disabled building python2.5 with db4.6 in setup.py with the following explanation: max_db_ver = (4, 5) # NOTE: while the _bsddb.c code links against BerkeleyDB 4.6.x # we leave that version disabled by default as it has proven to be # quite a buggy library release on many platforms. (this in spite of the fact that there's a separate check farther down for 4.6.21 or greater.) Overriding this check and building against db4.6 leads to the following (intermittent) test failure on SMP systems: $ LD_LIBRARY_PATH=./build-shared build-shared/python Lib/bsddb/test/test_thread.py ...Exception in thread writer 0: Traceback (most recent call last): File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 486, in __bootstrap_inner self.run() File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 446, in run self.__target(*self.__args, **self.__kwargs) File ../bsddb/test/test_thread.py, line 245, in writerThread self.assertEqual(data, self.makeData(key)) File /home/devel/canonical/python2.5-2.5.2/Lib/unittest.py, line 334, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: None != '0282-0282-0282-0282-0282' Exception in thread writer 1: Traceback (most recent call last): File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 486, in __bootstrap_inner self.run() File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 446, in run self.__target(*self.__args, **self.__kwargs) File ../bsddb/test/test_thread.py, line 260, in writerThread self.assertEqual(data, self.makeData(key)) File /home/devel/canonical/python2.5-2.5.2/Lib/unittest.py, line 334, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: None != '1003-1003-1003-1003-1003' Exception in thread writer 2: Traceback (most recent call last): File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 486, in __bootstrap_inner self.run() File /home/devel/canonical/python2.5-2.5.2/Lib/threading.py, line 446, in run self.__target(*self.__args, **self.__kwargs) File ../bsddb/test/test_thread.py, line 260, in writerThread self.assertEqual(data, self.makeData(key)) File /home/devel/canonical/python2.5-2.5.2/Lib/unittest.py, line 334, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: None != '2011-2011-2011-2011-2011' . -- Ran 8 tests in 15.105s So python is broken with db4.6, which explains the rollback to db4.5. Help tracking down the root of this bug would be good. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
reassing 469221 python2.4 # breaks other packages. severity 469221 grave thanks On Tue, Mar 04, 2008 at 02:19:48AM +, Mark Robinson wrote: This update worked fine, but the dist-upgrade immediately following failed: The bug is the fact that python downgraded its libdb version, breaking everything. It has been reported already and is not an apt-listchanges bug. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpAFX4OB6rjx.pgp Description: PGP signature
Bug#469221: Processed: Re: Processed (with 1 errors): Re: Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
reassign 469221 apt-listchanges thanks there's no bug about this in python; it's unfortunate that we had to downgrade the db version, but it has to be handled in apt-listchanges. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
Package: apt-listchanges Version: 2.82 Severity: normal Hi Pierre! Today while upgrading my system, I saw this: Reading changelogs... Done Traceback (most recent call last): File /usr/bin/apt-listchanges, line 227, in ? main() File /usr/bin/apt-listchanges, line 148, in main seen.close() File /usr/lib/python2.4/bsddb/__init__.py, line 237, in close v = self.db.close() bsddb.db.DBRunRecoveryError: (-30975, 'DB_RUNRECOVERY: Fatal error, run database recovery -- PANIC: fatal region error detected; run recovery') Any ideas why this could happen? Thank you very much! Best regards, Nelson -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-listchanges depends on: ii apt 0.7.11 Advanced front-end for dpkg ii debconf [debconf-2.0] 1.5.19 Debian configuration management sy ii debianutils 2.28.4 Miscellaneous utilities specific t ii python2.4.4-6An interactive high-level object-o ii python-apt0.7.5 Python interface to libapt-pkg ii python-support0.7.6 automated rebuilding support for p ii ucf 3.005 Update Configuration File: preserv Versions of packages apt-listchanges recommends: ii exim4 4.69-2 meta-package to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-2 lightweight Exim MTA (v4) daemon -- debconf information: apt-listchanges/confirm: false apt-listchanges/which: news apt-listchanges/frontend: pager apt-listchanges/email-address: root apt-listchanges/save-seen: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469221: apt-listchanges: Failed with bsddb.db.DBRunRecoveryError error
This update worked fine, but the dist-upgrade immediately following failed:
Tue Mar 04 12:44:12 [EMAIL PROTECTED]:~# aptitude -vV upgrade
W: The upgrade command is deprecated; use safe-upgrade instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages have unmet dependencies:
libglpk0: Depends: libiodbc2 (= 3.52.6) but it is not installable
Resolving dependencies...
The following packages have been kept back:
libglpk0 [4.25-1 - 4.27-1] spamassassin{a} [3.2.3-1 - 3.2.4-1]
The following packages will be REMOVED:
python-setuptools{u} [0.6c8-2]
The following packages will be upgraded:
libglade2.0-cil [2.10.4-1 - 2.10.4-2] libglib2.0-cil [2.10.4-1 -
2.10.4-2] libgtk2.0-cil [2.10.4-1 - 2.10.4-2]
libhtml-tableextract-perl [2.10-2 - 2.10-3] libraw1394-8 [1.3.0-2 -
1.3.0-3] libraw1394-dev [1.3.0-2 - 1.3.0-3]
libsensors4 [1:3.0.1-1 - 1:3.0.1-2] lm-sensors [1:3.0.1-1 - 1:3.0.1-2]
lsb-base [3.2-1 - 3.2-2] lsb-release [3.2-1 - 3.2-2]
python-opengl [3.0.0~a6-4 - 3.0.0~b1-1] python2.4 [2.4.4-7 - 2.4.4-8]
python2.4-dev [2.4.4-7 - 2.4.4-8] python2.4-minimal [2.4.4-7 - 2.4.4-8]
sed [4.1.5-5 - 4.1.5-6] spamc [3.2.3-1 - 3.2.4-1] ytree [1.86-1 -
1.86-1.1]
17 packages upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
Need to get 7600kB of archives. After unpacking 1061kB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Get:1 http://http.us.debian.org sid/main python-opengl 3.0.0~b1-1 [447kB]
Get:2 http://http.us.debian.org sid/main sed 4.1.5-6 [250kB]
Get:3 http://http.us.debian.org sid/main lsb-base 3.2-2 [17.3kB]
Get:4 http://http.us.debian.org sid/main libglib2.0-cil 2.10.4-2 [160kB]
Get:5 http://http.us.debian.org sid/main libgtk2.0-cil 2.10.4-2 [815kB]
Get:6 http://http.us.debian.org sid/main libglade2.0-cil 2.10.4-2 [143kB]
Get:7 http://http.us.debian.org sid/main libhtml-tableextract-perl 2.10-3
[33.4kB]
Get:8 http://http.us.debian.org sid/main libraw1394-dev 1.3.0-3 [49.5kB]
Get:9 http://http.us.debian.org sid/main libraw1394-8 1.3.0-3 [26.9kB]
Get:10 http://http.us.debian.org sid/main libsensors4 1:3.0.1-2 [59.8kB]
Get:11 http://http.us.debian.org sid/main python2.4-dev 2.4.4-8 [1470kB]
Get:12 http://http.us.debian.org sid/main python2.4 2.4.4-8 [2801kB]
Get:13 http://http.us.debian.org sid/main python2.4-minimal 2.4.4-8 [967kB]
Get:14 http://http.us.debian.org sid/main spamc 3.2.4-1 [73.6kB]
Get:15 http://http.us.debian.org sid/main ytree 1.86-1.1 [76.2kB]
Get:16 http://http.us.debian.org sid/main lm-sensors 1:3.0.1-2 [193kB]
Get:17 http://http.us.debian.org sid/main lsb-release 3.2-2 [17.4kB]
Fetched 7600kB in 1min44s (72.7kB/s)
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n]?
apt-listchanges: Mailing root: apt-listchanges: changelogs for piwakawaka
apt-listchanges: Mailing root: apt-listchanges: news for piwakawaka
(Reading database ... 304267 files and directories currently installed.)
Preparing to replace python-opengl 3.0.0~a6-4 (using
.../python-opengl_3.0.0~b1-1_all.deb) ...
Unpacking replacement python-opengl ...
(Reading database ... 304345 files and directories currently installed.)
Removing python-setuptools ...
(Reading database ... 304289 files and directories currently installed.)
Preparing to replace sed 4.1.5-5 (using .../archives/sed_4.1.5-6_i386.deb) ...
Unpacking replacement sed ...
Setting up sed (4.1.5-6) ...
(Reading database ... 304289 files and directories currently installed.)
Preparing to replace lsb-base 3.2-1 (using .../lsb-base_3.2-2_all.deb) ...
Unpacking replacement lsb-base ...
Setting up lsb-base (3.2-2) ...
(Reading database ... 304289 files and directories currently installed.)
Preparing to replace libglib2.0-cil 2.10.4-1 (using
.../libglib2.0-cil_2.10.4-2_i386.deb) ...
Unpacking replacement libglib2.0-cil ...
Preparing to replace libgtk2.0-cil 2.10.4-1 (using
.../libgtk2.0-cil_2.10.4-2_i386.deb) ...
Unpacking replacement libgtk2.0-cil ...
Preparing to replace libglade2.0-cil 2.10.4-1 (using
.../libglade2.0-cil_2.10.4-2_i386.deb) ...
Unpacking replacement libglade2.0-cil ...
Preparing to replace libhtml-tableextract-perl 2.10-2 (using
.../libhtml-tableextract-perl_2.10-3_all.deb) ...
Unpacking replacement libhtml-tableextract-perl ...
Preparing to replace libraw1394-dev 1.3.0-2 (using
.../libraw1394-dev_1.3.0-3_i386.deb) ...
Unpacking replacement libraw1394-dev ...
Preparing to replace libraw1394-8 1.3.0-2 (using
.../libraw1394-8_1.3.0-3_i386.deb) ...
Unpacking replacement libraw1394-8 ...
Preparing to replace libsensors4 1:3.0.1-1 (using
.../libsensors4_1%3a3.0.1-2_i386.deb) ...
Unpacking replacement libsensors4 ...
Preparing to replace python2.4-dev 2.4.4-7 (using
.../python2.4-dev_2.4.4-8_i386.deb) ...
Unpacking
