Has anyone ever experienced blank output from "rpm -qa" in a container? I created a Fedora 10 template using vzpkgcache command and my own metadata list of packages. Tried "rpm --rebuilddb" to no avail. OpenVZ kernel is 2.6.18-92.1.13.el5.028stab059.3 [root@f10 /]# rpm -qa [root@f10 /]# ll /var/lib/rpm total 11408 -rw-r--r-- 1 root root 1355776 Nov 25 17:07 Basenames -rw-r--r-- 1 root root 12288 Nov 25 17:06 Conflictname -rw-r--r-- 1 root root 192512 Nov 25 17:07 Dirnames -rw-r--r-- 1 root root 1323008 Nov 25 17:07 Filemd5s -rw-r--r-- 1 root root 12288 Nov 25 17:07 Group -rw-r--r-- 1 root root 12288 Nov 25 17:07 Installtid -rw-r--r-- 1 root root 12288 Nov 25 17:07 Name -rw-r--r-- 1 root root 8323072 Nov 25 17:07 Packages -rw-r--r-- 1 root root 90112 Nov 25 17:07 Providename -rw-r--r-- 1 root root 40960 Nov 25 17:07 Provideversion -rw-r--r-- 1 root root 12288 Nov 25 16:58 Pubkeys -rw-r--r-- 1 root root 114688 Nov 25 17:07 Requirename -rw-r--r-- 1 root root 65536 Nov 25 17:07 Requireversion -rw-r--r-- 1 root root 40960 Nov 25 17:07 Sha1header -rw-r--r-- 1 root root 24576 Nov 25 17:07 Sigmd5 -rw-r--r-- 1 root root 12288 Nov 25 17:07 Triggername
Has anyone else seen this and have more info or a fix? I haven't been able to figure it out yet, it seems like the rpm database just disappeared.
fwiw, I figured it out with help from irc: /dev/urandom had somehow been turned into a file instead of a proper device file. I thought I had already checked that, but I must have been in the wrong VE. Once /dev/urandom had been recreated properly, everything worked just fine.