# Problem after group resources in Pacemaker Cluster

**URL:** <https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945>\
**Category:** SLES High Availability Extension\
**Created:** [April 11, 2020, 11:34am UTC](https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945 "2020-04-11T11:34:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramesh](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@Ramesh](https://forums.suse.com/u/Ramesh)\
**Post date:** [April 11, 2020, 11:34am UTC](https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945/1 "2020-04-11T11:34:08Z")

</div>

[B]Operating System: Suse Linux for SAP Applications 12 SP4

Number of Cluster Nodes: 2[/B]

We have two resources pri\_apache2\_1 & ip\_apache2\_1\_132, these two resources are running fine. But When I group them to one with Pacemaker and trying to start them, then I am getting following errors

pri\_apache2\_2\_start\_0 on slesdbpcs02 ‘unknown error’ (1): call=180, status=Timed Out, exitreason=’’,  
last-rc-change=‘Sat Apr 11 03:25:38 2020’, queued=0ms, exec=40004ms

- pri\_apache2\_2\_start\_0 on slesdbpcs01 ‘unknown error’ (1): call=202, status=Timed Out, exitreason=’’,  
last-rc-change=‘Sat Apr 11 03:24:58 2020’, queued=0ms, exec=40006ms

Logs show:

2020-04-11T03:25:15.159297+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:16.195409+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:17.270873+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:18.317998+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:19.359485+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:20.406012+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up  
2020-04-11T03:25:21.444691+05:30 slesdbpcs01 apache(pri\_apache2\_2)[110725]: INFO: waiting for apache /etc/apache2/httpd\_2.conf to come up

Configuration:

slesdbpcs01:/etc/apache2 # crm configure show pri\_apache2\_1  
primitive pri\_apache2\_1 apache \  
op start timeout=120 interval=0 \  
op stop timeout=160 interval=0 \  
op monitor interval=10 timeout=20 \  
params configfile="/etc/apache2/httpd\_1.conf" \  
meta target-role=Started  
slesdbpcs01:/etc/apache2 # crm configure show ip\_apache2\_1\_132  
primitive ip\_apache2\_1\_132 IPaddr2 \  
params ip=192.168.1.132 cidr\_netmask=24 nic=eth0 \  
op monitor interval=0  
slesdbpcs01:/etc/apache2 #  
slesdbpcs01:/etc/apache2 #  
slesdbpcs01:/etc/apache2 # crm resource locate pri\_apache2\_1 ip\_apache2\_1\_132  
resource pri\_apache2\_1 is running on: slesdbpcs01  
resource ip\_apache2\_1\_132 is running on: slesdbpcs01  
slesdbpcs01:/etc/apache2 #

---

<div class="post-metadata">

**Author:** ![johngoutbeck](https://avatars.discourse-cdn.com/v4/letter/j/439d5e/32.png) [@johngoutbeck](https://forums.suse.com/u/johngoutbeck)\
**Post date:** [April 12, 2020, 11:42pm UTC](https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945/2 "2020-04-12T23:42:20Z")

</div>

Hello;

Its complaining about ‘pri\_apache2\_2’.

Do you have a resource called ‘pri\_apache2\_2’? Does it have a separate httpd\_2.conf for this resource?

The resources for apache should have different httpxx.conf files

Hope this helps

---

<div class="post-metadata">

**Author:** ![strahil-nikolov-dxc](https://avatars.discourse-cdn.com/v4/letter/s/58956e/32.png) [@strahil-nikolov-dxc](https://forums.suse.com/u/strahil-nikolov-dxc)\
**Post date:** [April 14, 2020, 11:28pm UTC](https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945/3 "2020-04-14T23:28:08Z")

</div>

It seems the logs are showing pacemaker having a problem to find the config ( /etc/apache2/httpd\_2.conf) for pri\_apache\_2\_2.  
Do you have any ordering or colocation rules involving pri\_apache\_2\_2 resource ?

---

<div class="post-metadata">

**Author:** ![Ramesh](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@Ramesh](https://forums.suse.com/u/Ramesh)\
**Post date:** [May 9, 2020, 8:21am UTC](https://forums.suse.com/t/problem-after-group-resources-in-pacemaker-cluster/34945/4 "2020-05-09T08:21:35Z")

</div>

[{“insert”:"Now this is resolved. Even I don’t remember how did i fix this as this happened 2 week back and also forgot to take notes immediately. Till now i have taken notes on the stuff i remember. Find the attachment for the same. I remember problem is with PID.  
“},{“insert”:{“embed-external”:{“data”:{“url”:“https:\/\/forums.suse.com\/uploads\/025\/5M8J9VKN5ZX3.pdf”,“name”:“Pacemaker-Multi Apache Instances-MySQL-DRBD.pdf”,“type”:“application\/pdf”,“size”:262864,“mediaID”:354,“dateInserted”:“2020-05-09T08:21:24+00:00”,“insertUserID”:44760,“foreignType”:“embed”,“foreignID”:44760,“embedType”:“file”,“format”:null,“bodyRaw”:null},“loaderData”:{“type”:“file”,“file”:[],“progressEventEmitter”:{“listeners”:[null]}}}}},{“insert”:”  
"}]
