|
The package "puppetdb" creates template /etc/puppetdb/conf.d/jetty.ini with proper permissions of puppetdb:puppetdb.
When running /sbin/puppetdb ssl-setup the file permissions change to "root" "root". If your umask is restrictive (e.g. 027) puppetdb start failes.
The attached fix keeps the original file permissions initially set via rpm:
{{--- /usr/libexec/puppetdb/puppetdb-ssl-setup.ORG 2015-10-14 00:23:52.000000000 +0200
+++ /usr/libexec/puppetdb/puppetdb-ssl-setup 2016-04-07 09:04:05.218000000 +0200
@@ -98,6 +98,8 @@
backupfile $3
tmp=$3.tmp.`date +%s`
sed "s/$1/$(echo $2 | sed -e 's/[\/&]/
&/g')/g" $3 > $tmp
+ chown --reference $3 $tmp
+ chmod --reference $3 $tmp
mv $tmp $3
}
@@ -114,6 +116,8 @@
backupfile $2
tmp=$2.tmp.`date +%s`
sed "/$1/ s/^/# /" $2 > $tmp
+ chown --reference $2 $tmp
+ chmod --reference $2 $tmp
mv $tmp $2
}
@@ -131,6 +135,8 @@
tmp=$2.tmp.`date +%s`
cat $2 > $ {tmp}
echo $1 >> ${tmp}
+ chown --reference $2 $tmp
+ chmod --reference $2 $tmp
mv $ {tmp}
$2
}}}
|
