[ClusterLabs] pacemakerd: undefined symbol: crm_procfs_process_info
philipp.achmueller at arz.at
philipp.achmueller at arz.at
Wed Mar 23 17:40:47 UTC 2016
hi,
tried migration from 1.1.13 to 1.1.14 (with latest files from github) -
now i'm unable to start pacemaker. corosync is running fine:
$ pcs cluster start
Starting Cluster...
Starting Pacemaker Cluster Manager[FAILED]
Error: unable to start pacemaker
$ cat corosync.log
...
Mar 23 18:34:34 [13127] lnx0083a corosync notice [MAIN ] Corosync
Cluster Engine ('2.3.3.139-3f51'): started and ready to provide service.
Mar 23 18:34:34 [13127] lnx0083a corosync info [MAIN ] Corosync
built-in features: pie relro bindnow
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] Initializing
transport (UDP/IP Unicast).
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] Initializing
transmit/receive security (NSS) crypto: none hash: none
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] Initializing
transport (UDP/IP Unicast).
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] Initializing
transmit/receive security (NSS) crypto: none hash: none
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] The network
interface [192.168.200.18] is now up.
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync configuration map access [0]
Mar 23 18:34:34 [13127] lnx0083a corosync info [QB ] server name:
cmap
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync configuration service [1]
Mar 23 18:34:34 [13127] lnx0083a corosync info [QB ] server name:
cfg
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync cluster closed process group service v1.01 [2]
Mar 23 18:34:34 [13127] lnx0083a corosync info [QB ] server name:
cpg
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync profile loading service [4]
Mar 23 18:34:34 [13127] lnx0083a corosync notice [QUORUM] Using quorum
provider corosync_votequorum
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync vote quorum service v1.0 [5]
Mar 23 18:34:34 [13127] lnx0083a corosync info [QB ] server name:
votequorum
Mar 23 18:34:34 [13127] lnx0083a corosync notice [SERV ] Service engine
loaded: corosync cluster quorum service v0.1 [3]
Mar 23 18:34:34 [13127] lnx0083a corosync info [QB ] server name:
quorum
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {192.168.200.18}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {192.168.200.19}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {192.168.200.20}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {192.168.200.21}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] The network
interface [10.1.102.18] is now up.
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {10.1.102.18}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {10.1.102.19}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {10.1.102.20}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] adding new UDPU
member {10.1.102.21}
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] A new
membership (192.168.200.18:1496) was formed. Members joined: 1
Mar 23 18:34:34 [13127] lnx0083a corosync notice [TOTEM ] A new
membership (192.168.200.18:1500) was formed. Members joined: 2 3 4
Mar 23 18:34:34 [13127] lnx0083a corosync notice [QUORUM] This node is
within the primary component and will provide service.
Mar 23 18:34:34 [13127] lnx0083a corosync notice [QUORUM] Members[4]: 1 2
3 4
Mar 23 18:34:34 [13127] lnx0083a corosync notice [MAIN ] Completed
service synchronization, ready to provide service.
Mar 23 18:34:34 [13141] lnx0083a pacemakerd: notice: mcp_read_config:
Configured corosync to accept connections from group 2035: OK (1)
Mar 23 18:34:34 [13141] lnx0083a pacemakerd: notice: main: Starting
Pacemaker 1.1.14 (Build: 535193a): agent-manpages ascii-docs ncurses
libqb-logging libqb-ipc lha-fenci
ng upstart nagios corosync-native atomic-attrd libesmtp acls
Mar 23 18:34:34 [13141] lnx0083a pacemakerd: info: main: Maximum
core file size is: 18446744073709551615
Mar 23 18:34:34 [13141] lnx0083a pacemakerd: info: qb_ipcs_us_publish:
server name: pacemakerd
there isn't any hintful message in /var/log/messages
$ sudo pacemakerd -F
Pacemaker 1.1.14 (Build: 535193a)
Supporting v3.0.10: agent-manpages ascii-docs ncurses libqb-logging
libqb-ipc lha-fencing upstart nagios corosync-native atomic-attrd
libesmtp acls
$ sudo pacemakerd -V
pacemakerd: symbol lookup error: pacemakerd: undefined symbol:
crm_procfs_process_info
---
i'm running my cluster on SLES11.3
corosync 2.3.3.139-3f51
libqb 1.0rc4.2-6fc2
any hints on that?
thank you!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160323/8f5aa268/attachment-0003.html>
More information about the Users
mailing list