update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseOpeningError: Couldn't open base /var/cache/apt-xapian-index/index.3/postlist.tmp to write: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base A

Bug #811034 reported by Ross Gardiner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
New
Undecided
Unassigned

Bug Description

Occured while updating, machine is i386 Oneiric Alpha2 in VirtualBox.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apt-xapian-index 0.43ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Fri Jul 15 14:01:45 2011
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --update -q
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--update', '-q']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with DatabaseError in buildIndex(): Modifications failed (DatabaseOpeningError: Couldn't open base /var/cache/apt-xapian-index/index.3/postlist.tmp to write: No such file or directory), and cannot set consistent table revision numbers: Couldn't reread base A
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Ross Gardiner (ross-gmx) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #633003, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.