Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-18 Thread Reynolds, John F - San Mateo, CA - Contractor
With respect, I've given up on the ocf:heartbeat:apache module. I've set up my Apache resource with: # systemctl disable apache2 # crm configure primitive ncoa_apache systemd:apache2 # crm configure modgroup grp_ncoa add ncoa_apache # crm configure show ncoa_apache primitive ncoa_apache

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-17 Thread Ken Gaillot
On Wed, 2019-10-16 at 13:33 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > > mailto:kgail...@redhat.com] > > Sent: Monday, October 14, 2019 12:02 PM > > > > If you have SELinux enabled, check for denials. The cluster > > processes have a different SELinux context than systemd, so

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-16 Thread Reynolds, John F - San Mateo, CA - Contractor
>mailto:kgail...@redhat.com] >Sent: Monday, October 14, 2019 12:02 PM > >If you have SELinux enabled, check for denials. The cluster processes have a >different SELinux context than systemd, so policies might not be set up >correctly. >-- >Ken Gaillot Alas, SELinux is not in use. I am

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-14 Thread Ken Gaillot
On Fri, 2019-10-11 at 17:15 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > > If pacemaker is managing a resource, the service should not be > > enabled to start on boot (regardless of init or systemd). Pacemaker > > will start and stop the service as needed according to the cluster

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-12 Thread Reynolds, John F - San Mateo, CA - Contractor
> If pacemaker is managing a resource, the service should not be enabled to > start on boot (regardless of init or systemd). Pacemaker will start and stop > the service as needed according to the cluster configuration. Apache startup is disabled in systemctl, and there is no apache script in

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Jan Pokorný
On 07/10/19 10:27 -0500, Ken Gaillot wrote: > Additionally, your pacemaker configuration is using the apache OCF > script, so the cluster won't use /etc/init.d/apache2 at all (it invokes > the httpd binary directly). See my parallel response. > Keep in mind that the httpd monitor action requires

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Ken Gaillot
On Fri, 2019-10-04 at 14:10 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > Good morning. > > I’ve just upgraded a two-node active-passive cluster from SLES11 to > SLES12. This means that I’ve gone from /etc/init.d scripts to > systemd services. > > On the SLES11 server, this

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Jan Pokorný
On 04/10/19 14:10 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > I've just upgraded a two-node active-passive cluster from SLES11 to > SLES12. This means that I've gone from /etc/init.d scripts to > systemd services. > > On the SLES11 server, this worked: > >

[ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-04 Thread Reynolds, John F - San Mateo, CA - Contractor
Good morning. I've just upgraded a two-node active-passive cluster from SLES11 to SLES12. This means that I've gone from /etc/init.d scripts to systemd services. On the SLES11 server, this worked: I had