Skip to main content

debconf: DbDriver "config": could not open /var/cache/debconf/config.dat

Chances are, you'll run into a few odd errors with Ubuntu's apt-get package manager. I've had my fair share; there was one that struck me as kind of odd. Luckily there was a simple solution. In my case, one such issue that popped up was that there was a conflict in a dependency and apt-get couldn't resolve it. In trying to resolve it, I issued apt-get -f install. It still failed on me.

root@axis:~# apt-get -f install
Reading package lists... Done
Building dependency tree      
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 63 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
debconf: DbDriver "config": could not open /var/cache/debconf/config.dat
Setting up man-db ( ...
debconf: DbDriver "config": could not open /var/cache/debconf/config.dat
dpkg: error processing man-db (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

It had me stumped at first- I tried clearing the cache and even rebuilding the apt-get config files. Turns out the issue is much simpler; there was no /var/cache/debconf directory!

 After issuing mkdir /var/cache/debconf, I was able to proceed with the rest of the update. The hint was: debconf: DbDriver "config": could not open /var/cache/debconf/config.dat. Like any good sysadmin, I decided to see what was in /var/cache/debconf- but as the directory didn't exist.. I created it manually and ran the command again.



  1. i tried this, but it gives me this error debconf: DbDriver "config": could not open /var/cache/debconf/config.dat

  2. Did you make sure the directory exists? Do "ls -lad /var/cache/debconf" to see. If it doesn't exist, you need to create it as root ("sudo mkdir /var/cache/debconf"). It is also possible that if your directory does exist, and config.dat is corrupted, that you'll need to move the existing config.dat out of the way ("sudo mv /var/cache/debconf/config.dat ~/." - this will put it in your home directory) and do an "apt-get clean" and try running the install again.

  3. Holy heck. I know you posted this months ago, but after messing around in aptitude, triple checking my sources list, and finally drilling down until I got that error (could not open /var/cache/debconf/, where previously I was getting a generic failure on linux-image-2.6.32-5-686 package, this saved me. Quickly made the directory, and re-ran the dist-upgrade. That's one less coffee I'll need today ^__^_
    Thank you.


Post a Comment

Popular posts from this blog

Starting vmtoolsd as a service on Red Hat / CentOS

If you're like me;  you may manage virtual servers within vSphere.. Linux ones.  Red Hat ones, in particular, but this applies to CentOS as well.

A long, long time ago, in a galaxy far away, the vmware-tools setup procedure installed the necessary init script for you.  Lately though, for new images that I've been building - those init scripts aren't getting installed by the vmware tools installation package.  So they don't start up on reboot.  VMware based backups failed; clock were going askew, you name it.   I need that daemon started on reboot.

Without a SysV init script handy, I had to roll my own.. and this is the result;  despite having worked with Linux for well over 15 years, setting up SysV init scripts remain somewhat of a black art.  The ones on our older system were more complicated than we needed.  I was aiming for something simpler and portable.

With RHEL 7, the rumor mills are abuzz with systemd so that may change. But, I'm a practical system admini…

Attempting to use dd on Mac OSX? Resource Busy?

If you're trying to use the dd command to image a usb disk or another device and you're running into an error that looks like:

# dd: /dev/disk#: Resource busy

There is a simple solution.

Use OSX's Disk Utility and unmount any of the partitions you have mounted on that particular disk without unmounting or ejecting the disk itself.

Afterwards, attempt the dd command again.


Attempting to use the umount utility in Mac OSX will result in a "Resource busy -- try 'diskutil unmount'".  The command-line equivalent would be:

# sudo diskutil unmount /Volumes/<disk in question>


# sudo diskutil unmount /Volumes/FLASHUSB

NetApp: Disabling snapshot for a volume on Data OnTAP

This is one of those things that isn't always very obvious. Sometimes, you need to disable snapshots for a volume.

Why in the world would someone want to disable a perfectly good feature of NetApp NAS Storage? Server/data migration for one. Disabling it temporarily will prevent the volume from filling up the snapshot directory. Maybe your volume doesn't need snapshots (data always changing, and can not be recoverable even with snapshots- such as oracle data dirs, in which case snapshots are useless).
You have to perform simple but important tasks. If your volume has a schedule, turn it off.

somefiler> snap sched rootvol Volume rootvol: 2 4 8@2,4,6,12,164
somefiler> snap sched rootvol 0 0 0 
somefiler> snap sched rootvol Volume rootvol: 0 0 0

That takes care of that. Next step is to disable the automatic snapshot option.

somefiler> vol options rootvol nosnap on

Now if you issue vol options rootvol You should see an option that says nosnap=on.

Lastly, you'l…