Re: [ClusterLabs] Pacemaker remote - invalid message detected, endian mismatch

2016-09-30 Thread Jan Pokorný 
On 30/09/16 11:28 -0500, Radoslaw Garbacz wrote:
> I have posted a question about this error attached to another thread, but
> because it was old and there is no answer I thought it could have been
> missed, so I am sorry for repeating it.
> 
> Regarding the problem.
> I have a cluster, and when the cluster gets bigger (around 40 remote nodes)
> some remote nodes go offline after a while and their logs report some
> message errors, there is no indication about anything wrong in the other
> logs.

I believe I would have a plausible explanation provided it may happen
(not sure now, perhaps the ipc proxy setup would allow it) that two
messages via the same connection are transmitted, with the second one
being read as part of the first one.

Could you please try running pacemaker_remoted with
"PCMK_trace_files=remote.c" in the respective "sysconfig" file?

> Details:
> - 40 ec2 m3.xlarge nodes, 1 corosync ring member, 39 remote
> - maybe irrelevant, but either "cib" or "pengine" process goes to ~100% CPU
> - it does not happen immediately
> - smaller cluster (~20 remote nodes) does not show any problems
> - pacemaker: 1.1.15-1.1f8e642.git.el6.x86_64
> - corosync: 2.4.1-1.2.0da1.el6.x86_64
> - libqb-1.0.0-1.28.4dff.el6.x86_64
> - CentOS 6
> 
> Logs:
> 
> [...]
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_abort:crm_remote_header: Triggered assert at remote.c:119 :
> endian == ENDIAN_LOCAL
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_remote_header:Invalid message detected, endian mismatch:
> badadbbd is neither 63646330 nor the swab'd 30636463
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_abort:crm_remote_header: Triggered assert at remote.c:119 :
> endian == ENDIAN_LOCAL
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_remote_header:Invalid message detected, endian mismatch:
> badadbbd is neither 63646330 nor the swab'd 30636463
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_abort:crm_remote_header: Triggered assert at remote.c:119 :
> endian == ENDIAN_LOCAL
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_remote_header:Invalid message detected, endian mismatch:
> badadbbd is neither 63646330 nor the swab'd 30636463
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted: info:
> lrmd_remote_client_msg:   Client disconnect detected in tls msg dispatcher.
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted: info:
> ipc_proxy_remove_provider:ipc proxy connection for client
> ca8df213-6da7-4c42-8cb3-b8bc0887f2ce pid 21815 destroyed because cluster
> node disconnected.
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted: info:
> cancel_recurring_action:  Cancelling ocf operation
> monitor_all_monitor_191000
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_send_tls: Connection terminated rc = -53
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_send_tls: Connection terminated rc = -10
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> crm_remote_send:  Failed to send remote msg, rc = -10
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> lrmd_tls_send_msg:Failed to send remote lrmd tls msg, rc = -10
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:  warning:
> send_client_notify:   Notification of client
> remote-lrmd-ip-10-237-223-67:3121/b6034d3a-e296-492f-b296-725735d17e22
> failed
> Sep 27 17:18:31 [19626] ip-10-237-223-67 pacemaker_remoted:   notice:
> lrmd_remote_client_destroy:   LRMD client disconnecting remote client -
> name: remote-lrmd-ip-10-237-223-67:3121 id: b6034d3a-e296-492f-b296-
> 725735d17e22
> Sep 27 17:19:35 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> ipc_proxy_accept: No ipc providers available for uid 0 gid 0
> Sep 27 17:19:35 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> handle_new_connection:Error in connection setup (19626-21815-14):
> Remote I/O error (121)
> Sep 27 17:19:50 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> ipc_proxy_accept: No ipc providers available for uid 0 gid 0
> Sep 27 17:19:50 [19626] ip-10-237-223-67 pacemaker_remoted:error:
> handle_new_connection:Error in connection setup (19626-21815-14):
> Remote I/O error (121)
> [...]

-- 
Jan (Poki)


pgp4MIpK8j5hh.pgp
Description: PGP signature
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] hi list

2016-09-30 Thread Dimitri Maziuk 
On 09/30/2016 10:10 AM, Антон Сацкий wrote:
> so U mean that in fact IPaddr is  IPaddr2 version
>  Is there  a way to see that ip address was added  except to see logs?
>  Before i can see ip using ifconfig

They removed ifconfig fro the default package set in RH7 so better get
used to "ip".

-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu



signature.asc
Description: OpenPGP digital signature
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] hi list

2016-09-30 Thread Ken Gaillot 
On 09/30/2016 10:10 AM, Антон Сацкий wrote:
> so U mean that in fact IPaddr is  IPaddr2 version
>  Is there  a way to see that ip address was added  except to see logs?
>  Before i can see ip using ifconfig
> Regards and thanks for reply.

"ip address show" (which can be abbreviated "ip a")

See https://tty1.net/blog/2010/ifconfig-ip-comparison_en.html

>  
> 
> 2016-09-30 16:14 GMT+03:00 Klaus Wenninger  >:
> 
> On 09/30/2016 02:39 PM, Антон Сацкий wrote:
> > Greeting for everyone
> > Got a question is it normal?
> >
> > below i can see
> >
> > Running /etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 
> 
> >  > start
> > IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Adding
> > inet address 10.0.10.113/24 
>  with broadcast
> > address 10.0.10.255 to device eth1
> > IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO:
> > Bringing device eth1 up
> >
> > but when i run ifconfig
> > i cant see 10.0.10.113 as eth1:0
> 
> That is fine IPaddr uses subinterfaces.
> As this is not the state of the art way to setup
> multiple IP addresses on one physical interface
> anymore IPaddr2 doesn't use subinterfaces
> anymore.
> 
> Regards,
> Klaus
> 
> 
> >
> >
> > BUT IT EXIST
> > i can ping 10.0.10.113  from pouter  and it is this  server
> >
> > PS
> > heartbeat.x86_64
> > 3.0.4-2.el6
> > @epe
> >
> > Centos  6.8
> >
> >
> >
> > Sep 30 15:02:24 voipserver.drbd heartbeat: [1568]: WARN:
> > string2msg_ll: node [asterisk.retail.ua
>  ]
> > failed authentication
> > Sep 30 15:02:28 voipserver.drbd heartbeat: [1568]: info: Heartbeat
> > shutdown in progress. (1568)
> > Sep 30 15:02:28 voipserver.drbd heartbeat: [2768]: info: Giving up all
> > HA resources.
> > ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Releasing
> > resource group: voipserver.drbd drbddisk::r0
> > Filesystem::/dev/drbd0::/replica::ext4
> > IPaddr::10.0.10.113/24/eth1/10.0.10.255 
> 
> >  > mysqld asterisk httpd
> > ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
> > /etc/init.d/httpd  stop
> > ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
> > /etc/init.d/asterisk  stop
> > ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
> > /etc/init.d/mysqld  stop
> > Sep 30 15:02:29 voipserver.drbd heartbeat: [1568]: WARN:
> > string2msg_ll: node [asterisk.retail.ua
>  ]
> > failed authentication
> > ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
> > /etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 
> 
> >  > stop
> > IPaddr(IPaddr_10.0.10.113)[2960]:2016/09/30_15:02:30 INFO: IP
> > status = ok, IP_CIP=
> > /usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_10.0.10.113)[2934]:
> > 2016/09/30_15:02:30 INFO:  Success
> > ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
> > /etc/ha.d/resource.d/Filesystem /dev/drbd0 /replica ext4 stop
> > Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
> > Running stop for /dev/drbd0 on /replica
> > Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
> > Trying to unmount /replica
> > Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
> > unmounted /replica successfully
> >
> 
> /usr/lib/ocf/resource.d//heartbeat/Filesystem(Filesystem_/dev/drbd0)[3042]:
> > 2016/09/30_15:02:31 INFO:  Success
> > ResourceManager(default)[2781]:2016/09/30_15:02:31 info: Running
> > /etc/ha.d/resource.d/drbddisk r0 stop
> > Sep 30 15:02:31 voipserver.drbd heartbeat: [2768]: info: All HA
> > resources relinquished.
> > Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: WARN: 1 lost
> > packet(s) for [voipbackup.drbd] [358:360]
> > Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: info: No pkts
> > missing from voipbackup.drbd!
> > Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing
> > HBFIFO process 1578 with signal 15
> > Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing
> > HBWRITE process 1580 with signal 15
> > Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]:

Re: [ClusterLabs] hi list

2016-09-30 Thread israel 

On 09/30/2016 04:39, Антон Сацкий wrote:

Greeting for everyone
Got a question is it normal?

below i can see

Running /etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255
[1] start
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Adding
inet address 10.0.10.113/24 [2] with broadcast address 10.0.10.255 to
device eth1
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO:
Bringing device eth1 up

but when i run ifconfig

i cant see 10.0.10.113 as eth1:0


When creating an address using the ocf:heartbeat:IPaddr2 module (not 
sure if module is the right terminology, but whatever), you need to 
specify the iflabel= option to get it to show up in ifconfig. Otherwise 
it doesn't show up, as you have noticed. If you used some other module 
to create the IP address, then I couldn't say if the same solution 
applies.


Israel Brewster
Ravn Alaska
Systems Analyst II



BUT IT EXIST

i can ping 10.0.10.113  from pouter  and it is this  server

PS
heartbeat.x86_64
3.0.4-2.el6

@epe

Centos  6.8

Sep 30 15:02:24 voipserver.drbd heartbeat: [1568]: WARN:
string2msg_ll: node [asterisk.retail.ua [3]] failed authentication
Sep 30 15:02:28 voipserver.drbd heartbeat: [1568]: info: Heartbeat
shutdown in progress. (1568)
Sep 30 15:02:28 voipserver.drbd heartbeat: [2768]: info: Giving up all
HA resources.
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Releasing
resource group: voipserver.drbd drbddisk::r0
Filesystem::/dev/drbd0::/replica::ext4
IPaddr::10.0.10.113/24/eth1/10.0.10.255 [1] mysqld asterisk httpd
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/httpd  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/asterisk  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/mysqld  stop
Sep 30 15:02:29 voipserver.drbd heartbeat: [1568]: WARN:
string2msg_ll: node [asterisk.retail.ua [3]] failed authentication
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 [1] stop
IPaddr(IPaddr_10.0.10.113)[2960]:2016/09/30_15:02:30 INFO: IP
status = ok, IP_CIP=
/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_10.0.10.113)[2934]:
 2016/09/30_15:02:30 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/Filesystem /dev/drbd0 /replica ext4 stop
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Running stop for /dev/drbd0 on /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Trying to unmount /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
unmounted /replica successfully
/usr/lib/ocf/resource.d//heartbeat/Filesystem(Filesystem_/dev/drbd0)[3042]:
   2016/09/30_15:02:31 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:31 info: Running
/etc/ha.d/resource.d/drbddisk r0 stop
Sep 30 15:02:31 voipserver.drbd heartbeat: [2768]: info: All HA
resources relinquished.
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: WARN: 1 lost
packet(s) for [voipbackup.drbd] [358:360]
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: info: No pkts
missing from voipbackup.drbd!
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing
HBFIFO process 1578 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing
HBWRITE process 1580 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing
HBREAD process 1581 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process
1578 exited. 3 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process
1580 exited. 2 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process
1581 exited. 1 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info:
voipserver.drbd Heartbeat shutdown complete.
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Pacemaker
support: false
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: WARN: Logging
daemon is disabled --enabling logging daemon is recommended
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info:
**
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Configuration
validated. Starting heartbeat 3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: heartbeat:
version 3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Heartbeat
generation: 1475232448
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat started on port 694 (694) interface eth1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat closed on port 694 interface eth1 - Status: 1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_TriggerHandler: Added signal manual handler
Sep 30 15:13:29 voipserver.drbd heartbeat:

Re: [ClusterLabs] Pacemaker dependency fails when upgrading OS (Amazon Linux)

2016-09-30 Thread Ken Gaillot 
On 09/29/2016 05:30 PM, neeraj ch wrote:
> Hello, 
> 
> I have pacemaker cluster running on Amazon Linux 2013.03 , details as
> follows.
> 
> OS : Amazon Linux 2013.03  64 bit (based off on el6)
> Pacemaker version : 1.1.12 downloaded
> form 
> http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/CentOS_CentOS-6/
> I downloaded all of pacemakers dependencies from the same repository as
> well.
> corosync version : 1.4.1
> 
> I worked well until I tried to update using yum update. It looks like
> yum wants to update perl. As soon as I run the update, a dependency
> error is popping showing the pacemaker dependency perl(
> module_compat_5.10.0) will change. 

I believe the only perl used by pacemaker is in the
fence_legacy/fence_pcmk fence agents, and the crm_report tool. If you
don't use any of those, you should be fine with ignoring the dependency.

Since Amazon Linux is derived from RHEL, you'd probably have more luck
with the corosync/pacemaker/etc. packages from the comparable CentOS
version instead. There are some library version differences between
RHEL/CentOS and AL though, so no guarantees.

> did any one else have a similar problem ?  Any help would be much
> appreciated.  
> 
> Thank you 
> 
> 
> 
> ___
> Users mailing list: Users@clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
> 


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] hi list

2016-09-30 Thread Антон Сацкий 
Greeting for everyone
Got a question is it normal?

below i can see

Running /etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 start
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Adding inet
address 10.0.10.113/24 with broadcast address 10.0.10.255 to device eth1
IPaddr(IPaddr_10.0.10.113)[2085]:2016/09/30_15:13:39 INFO: Bringing
device eth1 up

but when i run ifconfig
i cant see 10.0.10.113 as eth1:0


BUT IT EXIST
i can ping 10.0.10.113  from pouter  and it is this  server

PS
heartbeat.x86_64
3.0.4-2.el6
@epe

Centos  6.8



Sep 30 15:02:24 voipserver.drbd heartbeat: [1568]: WARN: string2msg_ll:
node [asterisk.retail.ua] failed authentication
Sep 30 15:02:28 voipserver.drbd heartbeat: [1568]: info: Heartbeat shutdown
in progress. (1568)
Sep 30 15:02:28 voipserver.drbd heartbeat: [2768]: info: Giving up all HA
resources.
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Releasing
resource group: voipserver.drbd drbddisk::r0
Filesystem::/dev/drbd0::/replica::ext4 IPaddr::
10.0.10.113/24/eth1/10.0.10.255 mysqld asterisk httpd
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/httpd  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/asterisk  stop
ResourceManager(default)[2781]:2016/09/30_15:02:28 info: Running
/etc/init.d/mysqld  stop
Sep 30 15:02:29 voipserver.drbd heartbeat: [1568]: WARN: string2msg_ll:
node [asterisk.retail.ua] failed authentication
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/IPaddr 10.0.10.113/24/eth1/10.0.10.255 stop
IPaddr(IPaddr_10.0.10.113)[2960]:2016/09/30_15:02:30 INFO: IP status =
ok, IP_CIP=
/usr/lib/ocf/resource.d//heartbeat/IPaddr(IPaddr_10.0.10.113)[2934]:
2016/09/30_15:02:30 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:30 info: Running
/etc/ha.d/resource.d/Filesystem /dev/drbd0 /replica ext4 stop
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Running stop for /dev/drbd0 on /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
Trying to unmount /replica
Filesystem(Filesystem_/dev/drbd0)[3050]:2016/09/30_15:02:31 INFO:
unmounted /replica successfully
/usr/lib/ocf/resource.d//heartbeat/Filesystem(Filesystem_/dev/drbd0)[3042]:
2016/09/30_15:02:31 INFO:  Success
ResourceManager(default)[2781]:2016/09/30_15:02:31 info: Running
/etc/ha.d/resource.d/drbddisk r0 stop
Sep 30 15:02:31 voipserver.drbd heartbeat: [2768]: info: All HA resources
relinquished.
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: WARN: 1 lost packet(s)
for [voipbackup.drbd] [358:360]
Sep 30 15:02:31 voipserver.drbd heartbeat: [1568]: info: No pkts missing
from voipbackup.drbd!
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBFIFO
process 1578 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBWRITE
process 1580 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: killing HBREAD
process 1581 with signal 15
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1578
exited. 3 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1580
exited. 2 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: Core process 1581
exited. 1 remaining
Sep 30 15:02:33 voipserver.drbd heartbeat: [1568]: info: voipserver.drbd
Heartbeat shutdown complete.
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Pacemaker support:
false
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: WARN: Logging daemon is
disabled --enabling logging daemon is recommended
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info:
**
Sep 30 15:13:29 voipserver.drbd heartbeat: [1569]: info: Configuration
validated. Starting heartbeat 3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: heartbeat: version
3.0.4
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Heartbeat
generation: 1475232448
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat started on port 694 (694) interface eth1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: glib: UDP
Broadcast heartbeat closed on port 694 interface eth1 - Status: 1
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_TriggerHandler: Added signal manual handler
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_TriggerHandler: Added signal manual handler
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info:
G_main_add_SignalHandler: Added signal handler for signal 17
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Local status now
set to: 'up'
Sep 30 15:13:29 voipserver.drbd heartbeat: [1570]: info: Link
voipserver.drbd:eth1 up.
Sep 30 15:13:31 voipserver.drbd heartbeat: [1570]: info: Link
voipbackup.drbd:eth1 up.
Sep 30 15:13:31 voipserver.drbd heartbeat: [1570]: info: Status update for
node voipbackup.drbd: status active

[ClusterLabs] Pacemaker dependency fails when upgrading OS (Amazon Linux)

2016-09-30 Thread neeraj ch 
Hello,

I have pacemaker cluster running on Amazon Linux 2013.03 , details as
follows.

OS : Amazon Linux 2013.03  64 bit (based off on el6)
Pacemaker version : 1.1.12 downloaded form
http://download.opensuse.org/repositories/network:/ha-clustering:/Stable/CentOS_CentOS-6/
I downloaded all of pacemakers dependencies from the same repository as
well.
corosync version : 1.4.1

I worked well until I tried to update using yum update. It looks like yum
wants to update perl. As soon as I run the update, a dependency error is
popping showing the pacemaker dependency perl( module_compat_5.10.0) will
change.

did any one else have a similar problem ?  Any help would be much
appreciated.

Thank you
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org