"config validation failed" while adding HA managed VM

F

FORCED-INDUCTN

Member
May 5, 2010
44
0
6
California, USA
Hello.

I'm trying to make some VMs HA managed, but when I hit "activate" in the "HA" tab I get this error message:

config validation failed: /usr/sbin/ccs_config_validate: line 186: 674512 Aborted ccs_config_dump > $tempfile (500)


I have run into problems like this before, and tried to run ccs_config_validate manually against the config however it says the config is fine? I used this command:

ccs_config_validate -f /etc/pve/cluster.conf.new

Bellow is my working cluster.conf:

Code: 
<?xml version="1.0"?>
<cluster config_version="5" name="x">
  <cman keyfile="/var/lib/pve-cluster/corosync.authkey"/>
  <fencedevices>
    <fencedevice agent="fence_ipmilan" ipaddr="x.x.x.x" lanplus="1" login="ADMIN" name="ironworks-ipmi" passwd="x" power_wait="5"/>
    <fencedevice agent="fence_ipmilan" ipaddr="x.x.x.x" lanplus="1" login="ADMIN" name="forge-ipmi" passwd="x" power_wait="5"/>
  </fencedevices>
  <quorumd interval="8" label="do-prod.fortress" tko="10" votes="1">
    <heuristic interval="3" program="ping 10.1.69.10 -c1 -w1" score="1" tko="4"/>
    <heuristic interval="3" program="ip addr | grep eth0 | grep -q UP" score="2" tko="3"/>
  </quorumd>
  <totem token="54000"/>
  <clusternodes>
    <clusternode name="ironworks" nodeid="1" votes="1">
      <fence>
        <method name="1">
          <device name="ironworks-ipmi"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="forge" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device name="forge-ipmi"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <rm/>
</cluster>

Here is the non working config:
Code: 
<?xml version="1.0"?>
<cluster config_version="6" name="do-prod">
  <cman keyfile="/var/lib/pve-cluster/corosync.authkey"/>
  <fencedevices>
    <fencedevice agent="fence_ipmilan" ipaddr="x" lanplus="1" login="ADMIN" name="ironworks-ipmi" passwd="x" power_wait="5"/>
    <fencedevice agent="fence_ipmilan" ipaddr="x" lanplus="1" login="ADMIN" name="forge-ipmi" passwd="x" power_wait="5"/>
  </fencedevices>
  <quorumd interval="8" label="do-prod.fortress" tko="10" votes="1">
    <heuristic interval="3" program="ping 10.1.69.10 -c1 -w1" score="1" tko="4"/>
    <heuristic interval="3" program="ip addr | grep eth0 | grep -q UP" score="2" tko="3"/>
  </quorumd>
  <totem token="54000"/>
  <clusternodes>
    <clusternode name="ironworks" nodeid="1" votes="1">
      <fence>
        <method name="1">
          <device name="ironworks-ipmi"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="forge" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device name="forge-ipmi"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <rm>
    <pvevm autostart="1" vmid="144"/>
  </rm>
</cluster>

Is this just a simple formatting issue?


--Will
 
Last edited:
There is a syntax error in your config:

Code: 
<fencedevice agent="fence_ipmilan" ipaddr="x" lanplus="1" login="ADMIN" name="forge-ipmi" passwd="x power_wait="5"/>

Please note the missing '"' in the password attribute. But I guess you introduced that typo when posting the file?

Also try to validate with:

# ccs_config_validate -l /etc/pve/cluster.conf.new

Maybe that gives more detailed error description?
 
dietmar said:
There is a syntax error in your config:

Code: 
<fencedevice agent="fence_ipmilan" ipaddr="x" lanplus="1" login="ADMIN" name="forge-ipmi" passwd="x power_wait="5"/>

Please note the missing '"' in the password attribute. But I guess you introduced that typo when posting the file?

Also try to validate with:

# ccs_config_validate -l /etc/pve/cluster.conf.new

Maybe that gives more detailed error description?
Click to expand...

Thanks for the response dietmar. I appologize, I did introduce that typo when creating this post (I have now fixed the typo). I ran ccs_config_validate -l /etc/pve/cluster.conf.new and it appears to have crashed?!

Code: 
[ironworks/etc/pve] ccs_config_validate -l /etc/pve/cluster.conf.new
*** glibc detected *** ccs_config_dump: free(): invalid next size (fast): 0x0000000001314610 ***
======= Backtrace: =========
/lib/libc.so.6(+0x71e16)[0x7f6adc18fe16]
/lib/libc.so.6(cfree+0x6c)[0x7f6adc194b8c]
ccs_config_dump[0x400f87]
ccs_config_dump[0x401068]
======= Memory map: ========
00400000-00402000 r-xp 00000000 fd:00 1482997                            /usr/sbin/ccs_config_dump
00601000-00602000 rw-p 00001000 fd:00 1482997                            /usr/sbin/ccs_config_dump
0130c000-0132d000 rw-p 00000000 00:00 0                                  [heap]
7f6ad4000000-7f6ad4021000 rw-p 00000000 00:00 0
7f6ad4021000-7f6ad8000000 ---p 00000000 00:00 0
7f6ada8d8000-7f6ada8ee000 r-xp 00000000 fd:00 442538                     /lib/libgcc_s.so.1
7f6ada8ee000-7f6adaaed000 ---p 00016000 fd:00 442538                     /lib/libgcc_s.so.1
7f6adaaed000-7f6adaaee000 rw-p 00015000 fd:00 442538                     /lib/libgcc_s.so.1
7f6adaaee000-7f6adaafa000 r-xp 00000000 fd:00 442805                     /lib/libnss_files-2.11.3.so
7f6adaafa000-7f6adacf9000 ---p 0000c000 fd:00 442805                     /lib/libnss_files-2.11.3.so
7f6adacf9000-7f6adacfa000 r--p 0000b000 fd:00 442805                     /lib/libnss_files-2.11.3.so
7f6adacfa000-7f6adacfb000 rw-p 0000c000 fd:00 442805                     /lib/libnss_files-2.11.3.so
7f6adacfb000-7f6adad03000 r-xp 00000000 fd:00 1482893                    /usr/lib/lcrso/config_cmanpre.lcrso
7f6adad03000-7f6adaf03000 ---p 00008000 fd:00 1482893                    /usr/lib/lcrso/config_cmanpre.lcrso
7f6adaf03000-7f6adaf04000 rw-p 00008000 fd:00 1482893                    /usr/lib/lcrso/config_cmanpre.lcrso
7f6adaf04000-7f6adaf84000 r-xp 00000000 fd:00 443144                     /lib/libm-2.11.3.so
7f6adaf84000-7f6adb184000 ---p 00080000 fd:00 443144                     /lib/libm-2.11.3.so
7f6adb184000-7f6adb185000 r--p 00080000 fd:00 443144                     /lib/libm-2.11.3.so
7f6adb185000-7f6adb186000 rw-p 00081000 fd:00 443144                     /lib/libm-2.11.3.so
7f6adb186000-7f6adb19d000 r-xp 00000000 fd:00 1475818                    /usr/lib/libz.so.1.2.3.4
7f6adb19d000-7f6adb39c000 ---p 00017000 fd:00 1475818                    /usr/lib/libz.so.1.2.3.4
7f6adb39c000-7f6adb39d000 rw-p 00016000 fd:00 1475818                    /usr/lib/libz.so.1.2.3.4
7f6adb39d000-7f6adb4e4000 r-xp 00000000 fd:00 1475198                    /usr/lib/libxml2.so.2.7.8
7f6adb4e4000-7f6adb6e3000 ---p 00147000 fd:00 1475198                    /usr/lib/libxml2.so.2.7.8
7f6adb6e3000-7f6adb6ec000 rw-p 00146000 fd:00 1475198                    /usr/lib/libxml2.so.2.7.8
7f6adb6ec000-7f6adb6ee000 rw-p 00000000 00:00 0
7f6adb6ee000-7f6adb6ef000 r-xp 00000000 fd:00 1482936                    /usr/lib/lcrso/config_xml.lcrso
7f6adb6ef000-7f6adb8ef000 ---p 00001000 fd:00 1482936                    /usr/lib/lcrso/config_xml.lcrso
7f6adb8ef000-7f6adb8f0000 rw-p 00001000 fd:00 1482936                    /usr/lib/lcrso/config_xml.lcrso
7f6adb8f0000-7f6adb8f9000 r-xp 00000000 fd:00 1483232                    /usr/lib/lcrso/objdb.lcrso
7f6adb8f9000-7f6adbaf8000 ---p 00009000 fd:00 1483232                    /usr/lib/lcrso/objdb.lcrso
7f6adbaf8000-7f6adbaf9000 rw-p 00008000 fd:00 1483232                    /usr/lib/lcrso/objdb.lcrso
7f6adbaf9000-7f6adbafb000 r-xp 00000000 fd:00 443143                     /lib/libdl-2.11.3.so
7f6adbafb000-7f6adbcfb000 ---p 00002000 fd:00 443143                     /lib/libdl-2.11.3.so
7f6adbcfb000-7f6adbcfc000 r--p 00002000 fd:00 443143                     /lib/libdl-2.11.3.so
7f6adbcfc000-7f6adbcfd000 rw-p 00003000 fd:00 443143                     /lib/libdl-2.11.3.so
7f6adbcfd000-7f6adbd14000 r-xp 00000000 fd:00 443126                     /lib/libpthread-2.11.3.so
7f6adbd14000-7f6adbf13000 ---p 00017000 fd:00 443126                     /lib/libpthread-2.11.3.so
7f6adbf13000-7f6adbf14000 r--p 00016000 fd:00 443126                     /lib/libpthread-2.11.3.so
7f6adbf14000-7f6adbf15000 rw-p 00017000 fd:00 443126                     /lib/libpthread-2.11.3.so
7f6adbf15000-7f6adbf19000 rw-p 00000000 00:00 0
7f6adbf19000-7f6adbf1e000 r-xp 00000000 fd:00 1476011                    /usr/lib/libcoroipcc.so.4.0.0
7f6adbf1e000-7f6adc11d000 ---p 00005000 fd:00 1476011                    /usr/lib/libcoroipcc.so.4.0.0
7f6adc11d000-7f6adc11e000 rw-p 00004000 fd:00 1476011                    /usr/lib/libcoroipcc.so.4.0.0
7f6adc11e000-7f6adc277000 r-xp 00000000 fd:00 443131                     /lib/libc-2.11.3.so
7f6adc277000-7f6adc476000 ---p 00159000 fd:00 443131                     /lib/libc-2.11.3.so
7f6adc476000-7f6adc47a000 r--p 00158000 fd:00 443131                     /lib/libc-2.11.3.so
7f6adc47a000-7f6adc47b000 rw-p 0015c000 fd:00 443131                     /lib/libc-2.11.3.so
7f6adc47b000-7f6adc480000 rw-p 00000000 00:00 0
7f6adc480000-7f6adc48c000 r-xp 00000000 fd:00 1476014                    /usr/lib/libconfdb.so.4.1.0
7f6adc48c000-7f6adc68c000 ---p 0000c000 fd:00 1476014                    /usr/lib/libconfdb.so.4.1.0
7f6adc68c000-7f6adc68d000 rw-p 0000c000 fd:00 1476014                    /usr/lib/libconfdb.so.4.1.0
7f6adc68d000-7f6adc6ab000 r-xp 00000000 fd:00 443127                     /lib/ld-2.11.3.so
7f6adc89d000-7f6adc8a1000 rw-p 00000000 00:00 0
7f6adc8a7000-7f6adc8aa000 rw-p 00000000 00:00 0
7f6adc8aa000-7f6adc8ab000 r--p 0001d000 fd:00 443127                     /lib/ld-2.11.3.so
7f6adc8ab000-7f6adc8ac000 rw-p 0001e000 fd:00 443127                     /lib/ld-2.11.3.so
7f6adc8ac000-7f6adc8ad000 rw-p 00000000 00:00 0
7fff10e10000-7fff10e25000 rw-p 00000000 00:00 0                          [stack]
7fff10e9e000-7fff10ea0000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
/usr/sbin/ccs_config_validate: line 186: 80026 Aborted                 ccs_config_dump > $tempfile

Unable to get the configuration

Is "-l" the syntax ccs_config_validate uses when activating config changes? This could explain why my config appears to be fine, but fails validation?


--Will
 
Last edited:
dietmar said:
What is the output of

# pveversion -v
Click to expand...

[ironworks~] pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1


[forge~] pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-18-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-48
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1

Those are the two servers in question.

--Will
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back