Proxmox 2.2 open-iscsi iscsi will not start on one node

[davlaw]

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

/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

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

 

[tom]

any hints in dmesg or syslog?

 

[davlaw]

iscsi and mutlitpath relationship , mutlitpath will not run properly without iscsi running first. I can answer that, but iscsi does not have a dependency on mutlitpath . Guess that is the question I'm hung on right now..

syslog is showing several lines with an exit code 255, but that appears I guess because of iscsid is not running, once running guessing its non issue. I'm still going thru the logs

Nov  2 09:22:31 proliant02 kernel: svc: failed to register lockdv1 RPC service (errno 97).
Nov   2 09:22:31 proliant02 pvestatd[2639]: WARNING: command  '/usr/bin/iscsiadm --mode discovery --type sendtargets --portal  172.16.0.3' failed: exit code 255
Nov  2 09:22:31 proliant02  pvestatd[2639]: WARNING: command '/usr/bin/iscsiadm --mode node  --targetname iqn.2008-09.com.scalecomputing:adl001 --login' failed: exit  code 255
Nov  2 09:22:32 proliant02 pvestatd[2639]: WARNING: command  '/usr/bin/iscsiadm --mode discovery --type sendtargets --portal  172.16.0.4' failed: exit code 255
Nov  2 09:22:32 proliant02  pvestatd[2639]: WARNING: command '/usr/bin/iscsiadm --mode node  --targetname iqn.2008-09.com.scalecomputing:domaincontl --login' failed:  exit code 255
Nov  2 09:22:32 proliant02 pvestatd[2639]: WARNING:  command '/usr/bin/iscsiadm --mode discovery --type sendtargets --portal  172.16.0.6' failed: exit code 255

 

[davlaw]

ummm... mean anything? this was in daemon.log

Nov  2 10:16:07 proliant02 iscsid: Missing or Invalid version from /sys/module/scsi_transport_iscsi/version. Make sure a up to date scsi_transport_iscsi m
odule is loaded and a up todate version of iscsid is running. Exiting...

but then, suppose after I gave the command manually

Nov  2 10:18:08 proliant02 iscsid: iSCSI logger with pid=11519 started!
Nov  2 10:18:09 proliant02 iscsid: transport class version 2.0-870. iscsid version 2.0-871
Nov  2 10:18:09 proliant02 iscsid: iSCSI daemon with pid=11520 started!

gonna look...

contents of version

2.0-870

 

[davlaw]

Well I hope this will be correct...

Remembered runlevels, installed sysv-rc-conf and found that open-scsi was not set to be started on said server, at any runlevel. Set to match other servers in cluster.

Have not tested yet but makes a lot of sense based on behavior. Had to look into this again since I started fencing and needed server to restart without any help ...

 

[davlaw]

svc: failed to register lockdv1 RPC service (errno 97).

nope, no good, starting getting mulltipath errors right after this error and still had to start iscsi manually. STill looking... and more goggling...