cluster will not start. dlm: no local IP address has been set

B

bread-baker

Member
Mar 6, 2010
432
0
16
during a backup i saw this in log: clvmd not running on node fbc158

so on fbc158 i tried to start clvm :
Code: 
root@homenet-fbc158 /etc # init.d/clvm start
Starting Cluster LVM Daemon: clvmclvmd could not connect to cluster manager
Consult syslog for more information
 failed!
syslog:
Code: 
Nov 24 09:32:11 fbc158 kernel: dlm: no local IP address has been set
Nov 24 09:32:11 fbc158 kernel: dlm: cannot start dlm lowcomms -107

nodes:
Code: 
pvecm nodes
Node  Sts   Inc   Joined               Name
   1   M    268   2011-11-18 08:58:24  fbc158
   2   M    288   2011-11-21 20:06:58  fbc10

pvecm status
Code: 
Version: 6.2.0
Config Version: 4
Cluster Name: fbcandover
Cluster Id: 37452
Cluster Member: Yes
Cluster Generation: 288
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2  
Active subsystems: 1
Flags: 
Ports Bound: 0  
Node name: fbc158
Node ID: 1
Multicast addresses: 239.192.146.222 
Node addresses: 10.100.100.158


hostname info:
Code: 
 # hostname
fbc158

grep fbc158 /etc/hosts
10.100.100.158 fbc158.fantinibakery.com fbc158 

root@homenet-fbc158 /etc # ping fbc158
PING fbc158.fantinibakery.com (10.100.100.158) 56(84) bytes of data.
64 bytes from fbc158.fantinibakery.com (10.100.100.158): icmp_req=1 ttl=64 time=0.020 ms
64 bytes from fbc158.fantinibakery.com (10.100.100.158): icmp_req=2 ttl=64 time=0.019 ms



pveversion -v
pve-manager: 2.0-10 (pve-manager/2.0/7a10f3e6)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-52
pve-kernel-2.6.32-6-pve: 2.6.32-52
lvm2: 2.02.86-1pve1
clvm: 2.02.86-1pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.7-1
pve-cluster: 1.0-11
qemu-server: 2.0-3
pve-firmware: 1.0-13
libpve-common-perl: 1.0-7
libpve-access-control: 1.0-2
libpve-storage-perl: 2.0-6
vncterm: 1.0-2
vzctl: 3.0.29-3pve3
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.1-1

any suggestions ?
 
Last edited:
Code: 
root@homenet-fbc158 /var/log # zgrep dlm syslog*
syslog:Nov 24 09:20:00 fbc158 kernel: dlm: no local IP address has been set
syslog:Nov 24 09:20:00 fbc158 kernel: dlm: cannot start dlm lowcomms -107
syslog:Nov 24 09:23:53 fbc158 kernel: dlm: no local IP address has been set
syslog:Nov 24 09:23:53 fbc158 kernel: dlm: cannot start dlm lowcomms -107
syslog:Nov 24 09:29:21 fbc158 kernel: dlm: no local IP address has been set
syslog:Nov 24 09:29:21 fbc158 kernel: dlm: cannot start dlm lowcomms -107
syslog:Nov 24 09:30:25 fbc158 kernel: dlm: no local IP address has been set
syslog:Nov 24 09:30:25 fbc158 kernel: dlm: cannot start dlm lowcomms -107
syslog:Nov 24 09:32:11 fbc158 kernel: dlm: no local IP address has been set
syslog:Nov 24 09:32:11 fbc158 kernel: dlm: cannot start dlm lowcomms -107
syslog.3.gz:Nov 21 20:06:46 fbc158 kernel: Modules linked in: kvm_intel kvm vzethdev vznetdev simfs vzrst nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 vzcpt nfs lockd fscache nfs_acl auth_rpcgss sunrpc vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter dlm xt_multiport xt_limit configfs xt_dscp ipt_REJECT ip_tables drbd vzevent ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse bridge stp llc ext4 jbd2 snd_hda_codec_realtek snd_pcsp snd_hda_intel snd_hda_codec i915 snd_hwdep snd_pcm drm_kms_helper snd_timer drm i2c_i801 snd i2c_algo_bit soundcore tpm_tis i2c_core snd_page_alloc tpm shpchp video tpm_bios serio_raw parport_pc output parport ext3 jbd mbcache ata_generic pata_acpi pata_it821x ata_piix e1000e [last unloaded: scsi_wait_scan]
syslog.6.gz:Nov 18 08:59:12 fbc158 kernel: dlm: no local IP address has been set
syslog.6.gz:Nov 18 08:59:12 fbc158 kernel: dlm: cannot start dlm lowcomms -107

this is one of 2 test systems at home.

I had not done much work on them since the 1-st beta iso .
 
after reboot it started:
Code: 
Nov 24 12:07:59 fbc158 kernel: dlm: Using TCP for communications
Nov 24 12:07:59 fbc158 kernel: dlm: got connection from 2

Code: 
pvecm status
Version: 6.2.0
Config Version: 4
Cluster Name: fbcandover
Cluster Id: 37452
Cluster Member: Yes
Cluster Generation: 328
Membership state: Cluster-Member
Nodes: 2
Expected votes: 2
Total votes: 2
Node votes: 1
Quorum: 2  
Active subsystems: 6
Flags: 
Ports Bound: 0 11  
Node name: fbc158
Node ID: 1
Multicast addresses: 239.192.146.222 
Node addresses: 10.100.100.158

I am not sure why it is working now.

we did have a power failure a couple of weeks ago, and that may have had something to do with the issue.
 
This is happening to me as well... quite randomly: I reboot a node and I get the issue then I re-reboot and the issue is gone...
I am running 2.0 beta with latest updates.
 
Having this very same problem on all my 4 nodes. It just become after I lost my backup and templates storage nfs mountpoint.
Rebooting node is not very good option.

:~# /etc/init.d/rgmanager start
Starting Cluster Service Manager: [FAILED]

:~# tail /var/log/syslog
Jan 8 09:46:06 PXX kernel: dlm: no local IP address has been set
Jan 8 09:46:06 PXX kernel: dlm: cannot start dlm lowcomms -107


:~# pveversion -v
pve-manager: 2.1-14 (pve-manager/2.1/f32f3f46)
running kernel: 2.6.32-14-pve
proxmox-ve-2.6.32: 2.1-74
pve-kernel-2.6.32-10-pve: 2.6.32-63
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.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-49
pve-firmware: 1.0-18
libpve-common-perl: 1.0-30
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-31
vncterm: 1.0-3
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-8
ksm-control-daemon: 1.1-1
 
Bumping this old thread with an update. I ran into this problem today on PVE 2.3 and wanted to post how I solved it. It is related to the cman service.

Executing the following commands on all of our nodes resolved the "dlm lowcomms -107" error.

Code: 
/etc/init.d/cman restart
/etc/init.d/pve-cluster restart

I also recommend adding a sleep 5 if you are issuing these commands via an SSH loop to a large PVE cluster.


See: http://permalink.gmane.org/gmane.linux.redhat.cluster/19782
 
You must log in or register to reply here.
Top Bottom
Back