Question

试图从Wheezy升级到Jessie（我知道，很晚）。

我已经发现，尽管心跳，起搏器和corosync版本号几乎没有变化，但其工作方式却有很大变化。我正在使用本文https://wiki.debian.org/Debian-HA/ClustersFromScratch进行安装。

但是，我无法使用原始配置启动集群。它报告 ERROR: status: crm_mon (rc=107): Connection to cluster failed: Transport endpoint is not connected

我在日志中注意到

May 25 01:07:59 [4989] domainname.com        cib:   notice: main:      Using legacy config location: /var/lib/heartbeat/crm
May 25 01:07:59 [4989] domainname.com        cib:     info: get_cluster_type:  Verifying cluster type: 'corosync'
May 25 01:07:59 [4989] domainname.com        cib:     info: get_cluster_type:  Assuming an active 'corosync' cluster
May 25 01:07:59 [4989] domainname.com        cib:     info: retrieveCib:       Reading cluster configuration file /var/lib/heartbeat/crm/cib.xml (digest: /var/lib/heartbeat/crm
May 25 01:07:59 [4992] domainname.com      attrd:     info: corosync_node_name:        Unable to get node name for nodeid 2130...
May 25 01:07:59 [4992] domainname.com      attrd:   notice: get_node_name:     Defaulting to uname -n for the local corosync node name
May 25 01:07:59 [4992] domainname.com      attrd:     info: crm_get_peer:      Node 2130... is now known as domainname.com
May 25 01:07:59 [4990] domainname.com stonith-ng:     info: corosync_node_name:        Unable to get node name for nodeid 2130...
May 25 01:07:59 [4990] domainname.com stonith-ng:   notice: get_node_name:     Defaulting to uname -n for the local corosync node name
May 25 01:07:59 [4990] domainname.com stonith-ng:     info: crm_get_peer:      Node 2130... is now known as domainname.com
May 25 01:07:59 [4992] domainname.com      attrd:     info: main:      Cluster connection active
May 25 01:07:59 [4992] domainname.com      attrd:     info: qb_ipcs_us_publish:        server name: attrd
May 25 01:07:59 [4992] domainname.com      attrd:     info: main:      Accepting attribute updates
May 25 01:07:59 [4989] domainname.com        cib:     info: validate_with_relaxng:     Creating RNG parser context
May 25 01:07:59 [4987] domainname.com pacemakerd:    error: pcmk_child_exit:   The cib process (4989) exited: Key has expired (127)

当我删除/ var / lib / heartbeat / crm时，它至少会启动，因此我可以进行crm状态。

现在：问题：旧的配置是否应该工作并且我应该在其他位置搜索（日志为HUGE），还是将目录删除并仅定义我拥有的四个资源更简单？

供参考，版本号：喘不过气来：

pacemaker/wheezy uptodate 1.1.7-1
libcorosync4/wheezy uptodate 1.4.2-3
heartbeat/wheezy uptodate 1:3.0.5-3
libheartbeat2/wheezy uptodate 1:3.0.5-3

杰西：

pacemaker:amd64/jessie-backports 1.1.16-1~bpo8+1 uptodate
corosync:amd64/jessie-backports 2.4.2-3+deb9u1~bpo8+1 uptodate
libcorosync-common4:amd64/jessie-backports 2.4.2-3+deb9u1~bpo8+1 uptodate
libcorosync4:all/jessie 1.4.6-1.1 uptodate
heartbeat:amd64/jessie 1:3.0.5+hg12629-1.2 uptodate
libheartbeat2:amd64/jessie 1:3.0.5+hg12629-1.2 uptodate

Answer 1

阅读http://www.linux-ha.org/doc/users-guide/_upgrading_from_crm_enabled_heartbeat_2_1_clusters.html#_backing_up_the_cib似乎正确的做法是删除/ var / lib / heartbeat / crm中的所有内容，除了/var/lib/heartbeat/crm/cib.xml

...不确定为什么心跳/节奏3.0.5-3像2.1一样，但是确实有道理...

...嗯，不行。

从Wheezy升级到Jessie：心跳+起搏器，使用旧版配置位置：/ var / lib / heartbeat / crm，但似乎不起作用

1 个答案: