Yes agreed, there are two issues on that:
https://tickets.puppetlabs.com/browse/SERVER-1717 and
https://tickets.puppetlabs.com/browse/PUP-7102. We tried to fix it earlier,
but had to revert due to acceptance test failures. The need for world
readable (or changing the owner or group to puppet) is
Thanks to all that contributed. I managed to solve the issue. Transpires
that the permissions on the files and directories (0640 for the most part)
was not sufficient. I had to ensure that all files in question had 0644
and directories at 0755 permissions set to get this to work. A simple
Thanks to all that contributed. I managed to solve the issue. Transpires
that the permissions on the files and directories (0644 for the most part)
was not sufficient. I had to ensure that all files in question had 0644
and directories at 0755 permissions set to get this to work. A simple
On 28.09.19 12:15, Martin Alfke wrote:
> Hi Dirk,
>
> you are including class accounts within node default classification.
> The accounts module does not do anything unless you add data to it.
>
> Please look at https://github.com/puppetlabs/puppetlabs-accounts and check if
> the following
Hi Dirk,
you are including class accounts within node default classification.
The accounts module does not do anything unless you add data to it.
Please look at https://github.com/puppetlabs/puppetlabs-accounts and check if
the following example is working:
node default {
accounts::user {
On 27.09.19 18:11, Dan Crisp wrote:
> Thanks for the reply John,
>
> The issue still persists unfortunately.
>
> I've ensured that Selinux isn't enforcing on both the server side and
> client and then restarted the Puppet service on the master server. The
> server logs whilst running the agent
Thanks for the reply John,
The issue still persists unfortunately.
I've ensured that Selinux isn't enforcing on both the server side and
client and then restarted the Puppet service on the master server. The
server logs whilst running the agent read as follows:
10.20.25.83 - - -
On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>
> Please see below. Apologies, there is a lot of detail here:
>
> Debug: Using settings: adding file resource 'confdir':
> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet",
> :ensure=>:directory,
Please see below. Apologies, there is a lot of detail here:
Debug: Using settings: adding file resource 'confdir':
'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
Debug: Using settings: adding file
This file does nothing. All the lines therein are commented out. In fact,
I have in the past moved this file out of the way then put it back just to
rule out it was doing anything weird.
Dan.
On Friday, September 27, 2019 at 10:58:49 AM UTC+1, Dirk Heinrichs wrote:
>
> Am Donnerstag, den
Am Donnerstag, den 26.09.2019, 06:20 -0700 schrieb Dan Crisp:
/etc/puppetlabs/code/environments/production:
total 20
-rw-r--r--. 1 root root 808 Sep 25 20:47 environment.conf
What does this one contain? I don't have these in my environments.
Bye...
Dirk
--
Dirk Heinrichs
Senior Systems
11 matches
Mail list logo
