Re: [ClusterLabs] Antw: VIP monitoring failing with Timed Out error

Hi Ulrich/Anyone, Could you please reply to the mail ? On Wed, Oct 28, 2015 at 3:22 PM, Pritam Kharat < pritam.kha...@oneconvergence.com> wrote: > Resource migration to STANDBY node failed. And log on STANDBY node says > Timed Out of VIP monitoring . What might be the reason for VIP TimedOut.

[ClusterLabs] Antw: Resource placement strategy and utilization AND resource location preference

>>> "Vallevand, Mark K" schrieb am 27.10.2015 um >>> 22:24 in Nachricht <37343dddcd2d454baaea374e80d73...@us-exch13-5.na.uis.unisys.com>: > How do the resource placement strategy and utilization AND resource location > preference relate? > > I mean, is it one or the

Re: [ClusterLabs] Antw: VIP monitoring failing with Timed Out error

Resource migration to STANDBY node failed. And log on STANDBY node says Timed Out of VIP monitoring . What might be the reason for VIP TimedOut. HA configuration is this way -> root@sc-node-2:~# crm configure show node $id="1" sc-node-1 node $id="2" sc-node-2 primitive oc-service-manager

Re: [ClusterLabs] VIP monitoring failing with Timed Out error

On 10/28/2015 03:51 AM, Pritam Kharat wrote: > Hi All, > > I am facing one issue in my two node HA. When I stop pacemaker on ACTIVE > node, it takes more time to stop and by this time VIP migration with other > resources migration fails to STANDBY node. (I have seen same issue in > ACTIVE node

[ClusterLabs] restarting resources after configuration changes

Hi, I am having problems restarting resources (e.g apache) after a configuration file change. I have tried 'pcs resource restart resourceid', which says 'resource successfully restarted', but the httpd process does not restart and hence my configuration changes in httpd.conf does not take

[ClusterLabs] [Enhancement] When STONITH is not completed, a resource moves.

Hi All, The following problem produced us in Pacemaker1.1.12. While STONITH was not completed, a resource moved it. The next movement seemed to happen in a cluster. Step1) Start a cluster. Step2) Node 1 breaks down. Step3) Node 1 is reconnected before practice is completed from node 2

Re: [ClusterLabs] restarting resources after configuration changes

Centos/redhat: try `service httpd configtest` to validate the config changes first …. Regards, Andrew Gray. RHCSA, Professional Unix Administration. Ph: (07) 3664 5112 From: - - [mailto:kri...@googlemail.com] Sent: Wednesday, 28 October 2015 8:21 PM To: users@clusterlabs.org Subject:

[ClusterLabs] Antw: ORACLE 12 and SLES HAE (Sles 11sp3)

Probably if Oracle 12 is compatible with Oracle 11, the RAs will continue to work. >>> "Cristiano Coltro" schrieb am 28.10.2015 um 09:45 in Nachricht <56309953026ff...@prv-mh.provo.novell.com>: > Hi, > most of the SLES 11 sp3 with HAE are migrating Oracle Db. > The

[ClusterLabs] Antw: VIP monitoring failing with Timed Out error

>>> Pritam Kharat schrieb am 28.10.2015 um >>> 09:51 in Nachricht

[ClusterLabs] ORACLE 12 and SLES HAE (Sles 11sp3)

Hi, most of the SLES 11 sp3 with HAE are migrating Oracle Db. The migration will be from Oracle 11 to Oracle 12 They have verified that the Oracles cluster resources actually supports - Oracle 10.2 and 11.2 Command used: usando il comando "crm ra info ocf:heartbeat:SAPDatabase" So seems they

[ClusterLabs] VIP monitoring failing with Timed Out error

Hi All, I am facing one issue in my two node HA. When I stop pacemaker on ACTIVE node, it takes more time to stop and by this time VIP migration with other resources migration fails to STANDBY node. (I have seen same issue in ACTIVE node reboot case also) Last change: Wed Oct 28 02:52:57 2015

Re: [ClusterLabs] ORACLE 12 and SLES HAE (Sles 11sp3)

On Wed, Oct 28, 2015 at 11:45 AM, Cristiano Coltro wrote: > Hi, > most of the SLES 11 sp3 with HAE are migrating Oracle Db. > The migration will be from Oracle 11 to Oracle 12 > > They have verified that the Oracles cluster resources actually supports > - Oracle 10.2 and 11.2