x86 container on PVE 3.1 with GlusterFS - PRNG is not seeded

Hello,


i´ve created a new ProxmoxVE installation with bare metal iso on a 8GB SLC SDHC memory card (/dev/sdb no swap). VM storage is /dev/sda with xfs filesystem and glusterfs on top mounted in ProxmoxVE via glusterfs plugin.


Creating a x64 container, everything works like expected. A x86 container throws these errors:


Code:
root@ct01 ~# /etc/init.d/ssh start
Starting OpenBSD Secure Shell server: sshdPRNG is not seeded
 [COLOR=#ff0000]failed![/COLOR]


recreating /dev/null, /dev/urandom, /dev/random doesn't solves the issue


When doing an upgrade:


Code:
root@ct01 ~# apt-get upgrade
/usr/bin/mandb: can´s create index cache /var/cache/man/XXXXX: Value too large for defined data type


System information:
proxmox-ve-2.6.32: 3.1-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.1-43 (running version: 3.1-43/1d4b0dfb)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-13
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1


glusterfs mount:
Code:
root@hi-pve02:~# mount | grep gluster/dev/sda1 on /data/glusterfs/pve-data/brick1 type xfs (rw,noatime,nodiratime,attr2,delaylog,nobarrier,inode64,allocsize=64k,logbsize=64k,sunit=128,swidth=256,noquota)
127.0.0.1:pve-data on /mnt/pve/gfs type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)

Any ideas?

Regards
Thomas
 
Last edited:
Some Follow-Up:

Creating a x86 container directly on mounted /dev/sda1 (/data/glusterfs/pve-data/brick1) works like expected.
Creating a x86 container directly on mounted glusterfs (/data/glusterfs/pve-data/brick1/brick) also works like expected.


So, the only part left is the proxmox fuse mount of the glusterfs...
 
Last edited:
I have the same problem with proxmox 3.2.


I created a container from debian-7.0-standard_7.0-2_i386.tar.gz which works until I try an update of openssh in this container (from version 6.0p1-4 to 6.0p1-4+deb7u1), then ssh does not start (PRNG is not seeded) and there are messages like yours (can´t create index cache /var/cache/man/XXXXX: Value too large for defined data type)


Using the (manually downloaded) container debian-7.0-standard_7.0-2_amd64.tar.gz from http://download.proxmox.com/appliances/system/debian-7.0-standard_7.0-2_amd64.tar.gz works fine.
 
Last edited: