[ClusterLabs] pacemaker apache and umask on CentOS 7

Ken Gaillot kgaillot at redhat.com
Wed Apr 20 10:31:12 EDT 2016

On 04/20/2016 09:11 AM, fatcharly at gmx.de wrote:
> Hi,
> I´m running a 2-node apache webcluster on a fully patched CentOS 7 (pacemaker-1.1.13-10.el7_2.2.x86_64 pcs-0.9.143-15.el7.x86_64).
> Some files which are generated by the apache are created with a umask 137 but I need this files created with a umask of 117.
> To change this I first tried to add a umask 117 to /etc/sysconfig/httpd & rebooted the system. This had no effekt.
> So I found out (after some research) that this is not working under CentOS 7 and that this had to be changed via systemd.
> So I created a directory "/etc/systemd/system/httpd.service.d" and put there a "umask.conf"-File with this content: 
> [Service]
> UMask=0117
> Again I rebooted the system but no effekt.
> Is the pacemaker really starting the apache over the systemd ? And how can I solve the problem ?
> Any suggestions are welcome
> Kind regards
> fatcharly

It depends on the resource agent you're using for apache.

If you were using systemd:httpd, I'd expect /etc/sysconfig/httpd or the
httpd.service.d override to work.

Since they don't, I'll guess you're using ocf:heartbeat:apache. In that
case, the file specified by the resource's envfiles parameter (which
defaults to /etc/apache2/envvars) is the right spot. So, you could
configure envfiles=/etc/sysconfig/httpd, or you could keep it default
and add your umask to /etc/apache2/envvars.

More information about the Users mailing list