After last weeks update to version 2.2 I noticed that I was having a problem with iscsi not starting when system boots (1 node out of 4) . The cluster had been running since Aug and never restarted it till now. So I don't think it's related to anything updated this past week.
Anyway, several long days and getting kind of punchy, don't want it to end up trashed. I can start it manually
And its good to go.
Just hoping to narrow down why it will not start on its own... . I have compared dmesg between servers and nothing is jumping out at me, thanks for any help or tips
Current pveversion -v
Anyway, several long days and getting kind of punchy, don't want it to end up trashed. I can start it manually
Code:
/etc/init.d/open-iscsi start
And its good to go.
Just hoping to narrow down why it will not start on its own... . I have compared dmesg between servers and nothing is jumping out at me, thanks for any help or tips
Current pveversion -v
Code:
pve-manager: 2.2-26 (pve-manager/2.2/c1614c8c)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-80
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-16-pve: 2.6.32-80
pve-kernel-2.6.32-14-pve: 2.6.32-74
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-1
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-28
qemu-server: 2.0-64
pve-firmware: 1.0-21
libpve-common-perl: 1.0-37
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-34
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1