Re: [ClusterLabs] Unable to start Apache resource
On Mon, Sep 25, 2023 at 4:50 PM Reid Wahl wrote: > > On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński > wrote: > > > > Greetings, > > > > I am facing an issue with launching a primitive resource in a two-node > > Pacemaker/Corosync cluster. I have set up a lab environment based on the > > guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise > > Server (Repeat)" [1] course. > > > > In my lab environment, I am using openSUSE Leap 15.5. > > Steps I have taken so far: > > > > - Created an IP resource > > > > --8<---cut here---start->8--- > > crm configure > > primitive p-IP_101 IPaddr2 \ > > params ip=172.17.17.101 cidr_netmask=24 nic=bond1 \ > > op start timeout=20s interval=0 \ > > op stop timeout=20s interval=0 \ > > op monitor timeout=20s interval=10s \ > > meta target-role=Started > > commit > > --8<---cut here---end--->8--- > > > > > > - Created an Apache resource > > > > crm configure edit # and added following content of the bottom of the > > file > > > > --8<---cut here---start->8--- > > primitive p-apache2_1 apache \ > > params configfile="/etc/apache2/http_1.conf" \ > > statusurl="172.17.17.101:8180" \ > > op start interval=0 timeout=40 \ > > op stop interval=0 timeout=60 \ > > op monitor interval=10 timeout=20 > > --8<---cut here---end--->8--- > > > > - Edited the Apache configuration files > > > > cp /etc/apache2/httpd.conf /etc/apache2/httpd_1.conf > > cp /etc/apache2/listen.conf /etc/apache2/listen_1.conf > > > > vi /etc/apache2/httpd_1.conf > > > > --8<---cut here---start->8--- > > Include /etc/apache2/listen_1.conf > > > > --snip-- > > Pidfile /var/run/httpd_1.pid > > --8<---cut here---end--->8--- > > > > vi /etc/apache2/listen_1.conf > > > > --8<---cut here---start->8--- > > Listen 172.17.17.101:8180 > > > > > > > > > > > > > > Listen 172.17.17.101:8443 > > > > > > > > > > --8<---cut here---end--->8--- > > > > > > - Ensured file synchronization using csync2 > > - Created a resource group with primitives for the IP and Apache resources > > > > --8<---cut here---start->8--- > > crm configure > > group g-apache2_1 p-IP_101 p-apache2_1 description="Apache2 Instance 1" > > commit > > --8<---cut here---end--->8--- > > > > - Started the resources, resulting in an error (logs provided below) > > > > --8<---cut here---start->8--- > > Failed Resource Actions: > > * p-apache2_1_start_0 on node01 'not installed' (5): call=24, > > status='complete', exitreason='environment is invalid, resource considered > > stopped', last-rc-change='Tue Sep 19 17:17:49 2023', queued=0ms, exec=39ms > > * p-apache2_1_start_0 on node02 'not installed' (5): call=26, > > status='complete', exitreason='environment is invalid, resource considered > > stopped', last-rc-change='Tue Sep 19 15:46:48 2023', queued=0ms, exec=40ms > > --8<---cut here---end--->8--- > > > > --8<---cut here---start->8--- > > crm configure rsctest p-apache2_1 > > INFO: Probing resources > > INFO: Testing on node01: p-apache2_1 > > ERROR: host node01 (exit code 5) > > > > INFO: Testing on node02: p-apache2_1 > > ERROR: host node02 (exit code 5) > > --8<---cut here---end--->8--- > > > > > > The Apache server is installed on both nodes > > > > --8<---cut here---start->8--- > > node01:~ # zypper se -i apache2 > > Loading repository data... > > Reading installed packages... > > > > S | Name| Summary | > > Type > > ---+-+--+ > > i+ | apache2 | The Apache Web Server| > > package > > i | apache2-prefork | Apache 2 "prefork" MPM (Multi-Processing Module) | > > package > > i | apache2-utils | Apache 2 utilities | > > package > > node01:~ # ssh node02 zypper se -i apache2 > > Loading repository data... > > Reading installed packages... > > > > S | Name| Summary | > > Type > > ---+-+--+ > > i+ | apache2 | The Apache Web Server| > > package > > i | apache2-prefork | Apache 2 "prefork" MPM (Multi-Processing Module) | > > package > > i | apache2-utils | Apache 2 utilities
Re: [ClusterLabs] Unable to start Apache resource
On Tue, Sep 19, 2023 at 9:10 AM Bartosz Kaczyński wrote: > > Greetings, > > I am facing an issue with launching a primitive resource in a two-node > Pacemaker/Corosync cluster. I have set up a lab environment based on the > guidelines from the "Say Goodbye to Downtime with SUSE Linux Enterprise > Server (Repeat)" [1] course. > > In my lab environment, I am using openSUSE Leap 15.5. > Steps I have taken so far: > > - Created an IP resource > > --8<---cut here---start->8--- > crm configure > primitive p-IP_101 IPaddr2 \ > params ip=172.17.17.101 cidr_netmask=24 nic=bond1 \ > op start timeout=20s interval=0 \ > op stop timeout=20s interval=0 \ > op monitor timeout=20s interval=10s \ > meta target-role=Started > commit > --8<---cut here---end--->8--- > > > - Created an Apache resource > > crm configure edit # and added following content of the bottom of the > file > > --8<---cut here---start->8--- > primitive p-apache2_1 apache \ > params configfile="/etc/apache2/http_1.conf" \ > statusurl="172.17.17.101:8180" \ > op start interval=0 timeout=40 \ > op stop interval=0 timeout=60 \ > op monitor interval=10 timeout=20 > --8<---cut here---end--->8--- > > - Edited the Apache configuration files > > cp /etc/apache2/httpd.conf /etc/apache2/httpd_1.conf > cp /etc/apache2/listen.conf /etc/apache2/listen_1.conf > > vi /etc/apache2/httpd_1.conf > > --8<---cut here---start->8--- > Include /etc/apache2/listen_1.conf > > --snip-- > Pidfile /var/run/httpd_1.pid > --8<---cut here---end--->8--- > > vi /etc/apache2/listen_1.conf > > --8<---cut here---start->8--- > Listen 172.17.17.101:8180 > > > > > > > Listen 172.17.17.101:8443 > > > > > --8<---cut here---end--->8--- > > > - Ensured file synchronization using csync2 > - Created a resource group with primitives for the IP and Apache resources > > --8<---cut here---start->8--- > crm configure > group g-apache2_1 p-IP_101 p-apache2_1 description="Apache2 Instance 1" > commit > --8<---cut here---end--->8--- > > - Started the resources, resulting in an error (logs provided below) > > --8<---cut here---start->8--- > Failed Resource Actions: > * p-apache2_1_start_0 on node01 'not installed' (5): call=24, > status='complete', exitreason='environment is invalid, resource considered > stopped', last-rc-change='Tue Sep 19 17:17:49 2023', queued=0ms, exec=39ms > * p-apache2_1_start_0 on node02 'not installed' (5): call=26, > status='complete', exitreason='environment is invalid, resource considered > stopped', last-rc-change='Tue Sep 19 15:46:48 2023', queued=0ms, exec=40ms > --8<---cut here---end--->8--- > > --8<---cut here---start->8--- > crm configure rsctest p-apache2_1 > INFO: Probing resources > INFO: Testing on node01: p-apache2_1 > ERROR: host node01 (exit code 5) > > INFO: Testing on node02: p-apache2_1 > ERROR: host node02 (exit code 5) > --8<---cut here---end--->8--- > > > The Apache server is installed on both nodes > > --8<---cut here---start->8--- > node01:~ # zypper se -i apache2 > Loading repository data... > Reading installed packages... > > S | Name| Summary | Type > ---+-+--+ > i+ | apache2 | The Apache Web Server| > package > i | apache2-prefork | Apache 2 "prefork" MPM (Multi-Processing Module) | > package > i | apache2-utils | Apache 2 utilities | > package > node01:~ # ssh node02 zypper se -i apache2 > Loading repository data... > Reading installed packages... > > S | Name| Summary | Type > ---+-+--+ > i+ | apache2 | The Apache Web Server| > package > i | apache2-prefork | Apache 2 "prefork" MPM (Multi-Processing Module) | > package > i | apache2-utils | Apache 2 utilities | > package > --8<---cut here---end--->8--- > > and the firewall is disabled. What else can I check? Are there any more logs (for example, in /var/log/messages) from the apache resource agent? The "environment is invalid, resource considered stopped" message comes from
[ClusterLabs] announcement: schedule for resource-agents release 4.13.0
Hi, This is a tentative schedule for resource-agents v4.13.0: 4.13.0-rc1: Oct 4. 4.13.0: Oct 11. The storage-mon resource agent has got a new daemon mode that can be enabled to avoid child processes remaining stuck after I/O has been unresponsive, so make sure to give it some additional testing. It can be enabled by setting daemonize=true and check_interval can be used to change from the default (30s). Full list of changes: https://github.com/ClusterLabs/resource-agents/compare/v4.12.0...main I've modified the corresponding milestones at: https://github.com/ClusterLabs/resource-agents/milestones If there's anything you think should be part of the release please open an issue, a pull request, or a bugzilla, as you see fit. If there's anything that hasn't received due attention, please let us know. Finally, if you can help with resolving issues consider yourself invited to do so. There are currently 154 issues and 48 pull requests still open. Cheers, Oyvind Albrigtsen ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/developers ClusterLabs home: https://www.clusterlabs.org/ ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
