Re: [Pacemaker] coronosyc 1.2.1 with pacemaker and openais is suse11sp1
> On 15 Apr 2015, at 10:06 pm, Timi wrote: > > Hi guys, > > we have a cluster setup with: coronosyc 1.2.1 with pacemaker and openais is > suse11sp1 on two nodes connected via direct cable for heartbeat, we checked > the connection and its ok. > > we are having this on the logs: > > 12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: info: > perform_op:2894: postponing all ops on resource floating-ip by 1000 ms > [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: debug: > rsc:floating-ip:112: monitor > [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [23676]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER > [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [9285]: debug: > rsc:internal-floating-ip:115: monitor > [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [23684]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER > [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [9285]: debug: > rsc:floating-ip:35: monitor > [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [23698]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER That wont be affecting corosync. The logs themselves might be though - debug can be very noisy. > > > this happens frequently and we believe it causes instability issues as we > sometimes after these logs the: > > corosync [TOTEM ] Process pause detected for 5370 ms, flushing membership > messages. > > > > and there it starts to panic and causes the msql to restart each 5 min. > > Has anyone any idea what might be causing this. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] coronosyc 1.2.1 with pacemaker and openais is suse11sp1
have you try to check your system resource? i had the some msg "corosync [TOTEM ] Process pause detected for 5370 ms" some time ago, the problem was kernel system use was so hight, you can try to check using sar, my system was suse 11 sp1 as your. 2015-04-15 14:06 GMT+02:00 Timi : > Hi guys, > > we have a cluster setup with: coronosyc 1.2.1 with pacemaker and openais is > suse11sp1 on two nodes connected via direct cable for heartbeat, we checked > the connection and its ok. > > we are having this on the logs: > > 12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: info: > perform_op:2894: postponing all ops on resource floating-ip by 1000 ms > [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: debug: > rsc:floating-ip:112: monitor > [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [23676]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER > [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [9285]: debug: > rsc:internal-floating-ip:115: monitor > [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [23684]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER > [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [9285]: debug: > rsc:floating-ip:35: monitor > [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [23698]: debug: > perform_ra_op: resetting scheduler class to SCHED_OTHER > > > this happens frequently and we believe it causes instability issues as we > sometimes after these logs the: > > corosync [TOTEM ] Process pause detected for 5370 ms, flushing membership > messages. > > > > and there it starts to panic and causes the msql to restart each 5 min. > > Has anyone any idea what might be causing this. > > > ___ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org -- esta es mi vida e me la vivo hasta que dios quiera ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] coronosyc 1.2.1 with pacemaker and openais is suse11sp1
Hi guys, we have a cluster setup with: coronosyc 1.2.1 with pacemaker and openais is suse11sp1 on two nodes connected via direct cable for heartbeat, we checked the connection and its ok. we are having this on the logs: 12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: info: perform_op:2894: postponing all ops on resource floating-ip by 1000 ms [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [9285]: debug: rsc:floating-ip:112: monitor [12:23] <[1]TT> Apr 03 03:40:52 flexy-db-1 lrmd: [23676]: debug: perform_ra_op: resetting scheduler class to SCHED_OTHER [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [9285]: debug: rsc:internal-floating-ip:115: monitor [12:23] <[1]TT> Apr 03 03:40:53 flexy-db-1 lrmd: [23684]: debug: perform_ra_op: resetting scheduler class to SCHED_OTHER [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [9285]: debug: rsc:floating-ip:35: monitor [12:23] <[1]TT> Apr 03 03:40:56 flexy-db-1 lrmd: [23698]: debug: perform_ra_op: resetting scheduler class to SCHED_OTHER this happens frequently and we believe it causes instability issues as we sometimes after these logs the: corosync [TOTEM ] Process pause detected for 5370 ms, flushing membership messages. and there it starts to panic and causes the msql to restart each 5 min. Has anyone any idea what might be causing this. ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
