> On 27 Apr 2015, at 6:35 pm, Patrick Zwahlen wrote:
>
>> Apart from those scary logs, does anything actually break?
>> What your seeing is probably just ignorable noise from the older version
>> - I would expect the underlying cib to resolve things correctly.
>
> Thanks Andrew for the response
> Apart from those scary logs, does anything actually break?
> What your seeing is probably just ignorable noise from the older version
> - I would expect the underlying cib to resolve things correctly.
Thanks Andrew for the response.
After starting the new 1.1.12 and trying to migrate my resourc
> On 26 Apr 2015, at 7:27 pm, Patrick Zwahlen wrote:
>
>> map your ip cluster to hostname using /etc/hosts and try to use an
>> example like this
>> http://clusterlabs.org/doc/fr/Pacemaker/1.1-
>> pcs/html/Clusters_from_Scratch/_sample_corosync_configuration.html
>
> I've added "name: fqdn" in
> map your ip cluster to hostname using /etc/hosts and try to use an
> example like this
> http://clusterlabs.org/doc/fr/Pacemaker/1.1-
> pcs/html/Clusters_from_Scratch/_sample_corosync_configuration.html
I've added "name: fqdn" in my corosync.conf and I don't have those hostname
logs anymore.
Th
map your ip cluster to hostname using /etc/hosts and try to use an
example like this
http://clusterlabs.org/doc/fr/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/_sample_corosync_configuration.html
2015-04-25 12:19 GMT+02:00 Patrick Zwahlen :
>> Are you sure your cluster hostnames are ok?
>>
>> get_
> Are you sure your cluster hostnames are ok?
>
> get_node_name: Could not obtain a node name for corosync nodeid 2
(Confused with pacemaker<->clusterlabs mailinglists. Sorry for the
double-post)
Cluster works perfectly on CentOS 7.0, even though I have these logs as
well. Might be due to corosy
Are you sure your cluster hostnames are ok?
get_node_name: Could not obtain a node name for corosync nodeid 2
2015-04-24 17:09 GMT+02:00 Patrick Zwahlen :
> Hi,
>
> I'm running a CentOS 7.0 2-nodes cluster providing iSCSI/SAN features. In
> order to upgrade to CentOS 7.1, I'm testing the whole p
Hi,
I'm running a CentOS 7.0 2-nodes cluster providing iSCSI/SAN features. In order
to upgrade to CentOS 7.1, I'm testing the whole process in VMs and it fails.
I've now stripped my config down to a pair of DRBD MS with IPADDR2
(cluster.cfg) attached.
>From a running cluster, here are the step
