Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

debconf: DbDriver "templatedb": could not sync

184 views
Skip to first unread message

Udo Mueller

unread,
Sep 6, 2006, 1:40:09 PM9/6/06
to
Hello debian-devel,

please CC because i am not subscribed!

Yesterday i did a dist-upgrade on an etch system. Most of the
packages were installed and configured correct but some failed with
this error:


DbDriver "templatedb": could not sync /var/cache/debconf/templates.dat-new: Input-/Output error

The filesystem on this partition is LVM with ext3.
fsck.ext3 runs without any error message.
I can create, open, edit and delete files without any problems.
The command "sync" works fine, too.

The following packages were installed:

(sry its in german):

[INSTALLIEREN, ABHÄNGIGKEITEN] librpcsecgss3
[INSTALLIEREN, ABHÄNGIGKEITEN] libssp0
[INSTALLIEREN, ABHÄNGIGKEITEN] python2.4
[INSTALLIEREN, ABHÄNGIGKEITEN] python2.4-minimal
[ENTFERNEN, ABHÄNGIGKEITEN] librpcsecgss2
[AKTUALISIERUNG] base-files 3.1.14 -> 3.1.16
[AKTUALISIERUNG] cpp-4.1 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] cupsys 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] cupsys-bsd 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] cupsys-client 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] cupsys-common 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] foomatic-db 20060712-1 -> 20060822-1
[AKTUALISIERUNG] foomatic-filters 3.0.2-20060712-1 -> 3.0.2-20060712-3
[AKTUALISIERUNG] g++-4.1 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] gcc-4.1 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] gcc-4.1-base 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] ifupdown 0.6.7 -> 0.6.7-0.1
[AKTUALISIERUNG] initramfs-tools 0.75 -> 0.77b
[AKTUALISIERUNG] libc6 2.3.6-15 -> 2.3.6.ds1-4
[AKTUALISIERUNG] libc6-amd64 2.3.6-15 -> 2.3.6.ds1-4
[AKTUALISIERUNG] libc6-dev 2.3.6-15 -> 2.3.6.ds1-4
[AKTUALISIERUNG] libc6-i686 2.3.6-15 -> 2.3.6.ds1-4
[AKTUALISIERUNG] libcompress-zlib-perl 1.41-1 -> 1.42-1
[AKTUALISIERUNG] libcupsimage2 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] libcupsys2 1.2.2-1 -> 1.2.2-2
[AKTUALISIERUNG] libgcc1 1:4.1.1-5 -> 1:4.1.1-11
[AKTUALISIERUNG] libio-socket-ssl-perl 0.994-1 -> 0.999-1
[AKTUALISIERUNG] libkrb53 1.4.3-9 -> 1.4.4~beta1-1
[AKTUALISIERUNG] libpci2 2:2.1.11-2 -> 2:2.1.11-3
[AKTUALISIERUNG] libstdc++6 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] libstdc++6-4.1-dev 4.1.1-5 -> 4.1.1-11
[AKTUALISIERUNG] libwrap0 7.6.dbs-9 -> 7.6.dbs-11
[AKTUALISIERUNG] locales 2.3.6-15 -> 2.3.6.ds1-4
[AKTUALISIERUNG] manpages 2.34-1 -> 2.39-1
[AKTUALISIERUNG] manpages-dev 2.34-1 -> 2.39-1
[AKTUALISIERUNG] nfs-common 1:1.0.9-5 -> 1:1.0.9-10
[AKTUALISIERUNG] pciutils 1:2.2.1-2 -> 1:2.2.4~pre4-1
[AKTUALISIERUNG] python 2.3.5-11 -> 2.4.3-11
[AKTUALISIERUNG] python-minimal 2.3.5-11 -> 2.4.3-11
[AKTUALISIERUNG] reportbug 3.21.2 -> 3.29.3
[AKTUALISIERUNG] tcpd 7.6.dbs-9 -> 7.6.dbs-11
[AKTUALISIERUNG] ucf 2.0013 -> 2.0014

The problem is that i cant install any other packages because
dpkg complains that packages are not configured yet.

If i run "dpkg --configure -a" dpkg gets interrupted with the above
error message.

I already asked google but with "could not sync" it only shows urls
to the debconf source code.

Anyone has a solution for this problem?

Mit freundlichen Grüßen

Udo Müller

--
ComputerService Udo Müller Tel.: 0441-36167578
Schöllkrautweg 16 Fax.: 0441-36167579
26135 Oldenburg in...@cs-ol.de Mobil: 0162-4365411

signature.asc

Wouter Verhelst

unread,
Sep 6, 2006, 3:30:08 PM9/6/06
to
On Wed, Sep 06, 2006 at 07:29:13PM +0200, Udo Mueller wrote:
> fsck.ext3 runs without any error message.

Did you do "fsck -f", or just "fsck"? In case you did the latter, please
run it with -f again.

--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22


--
To UNSUBSCRIBE, email to debian-dev...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Joey Hess

unread,
Sep 6, 2006, 3:40:09 PM9/6/06
to
Udo Mueller wrote:
> DbDriver "templatedb": could not sync /var/cache/debconf/templates.dat-new: Input-/Output error

This looks very likely to be a disk problem. FWIW, it's calling fsync(2)
on that file.

> The filesystem on this partition is LVM with ext3.
> fsck.ext3 runs without any error message.
> I can create, open, edit and delete files without any problems.
> The command "sync" works fine, too.

None of which rule out a problem with your disk. You could use the
badblocks command to test the whole disk for bad blocks. Or look at
smartctl output and/or dmesg for problems.

--
see shy jo

signature.asc

Udo Mueller

unread,
Sep 7, 2006, 5:10:09 PM9/7/06
to
Hallo Wouter,

if you replay plz CC me.

* Wouter Verhelst schrieb [06-09-06 20:26]:


> On Wed, Sep 06, 2006 at 07:29:13PM +0200, Udo Mueller wrote:
> > fsck.ext3 runs without any error message.
>
> Did you do "fsck -f", or just "fsck"? In case you did the latter, please
> run it with -f again.

I ran it without -f. Today i had physical access and ran fsck -f. It
showed no errors.

But: The disc space is provided by a DAS Raid system. The DAS is
directly attached to the box and a backup tape is attached to the
DAS.

While rebooting Debian i noticed some errors which are backup-tape
related scsi errors.
After these errors were removed dpkg work fine again.

Dont know the exact reasons but it works now.

signature.asc
0 new messages