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 read as follows:
Are you positive the user and group really haven't been created?
And have you changed
node 'default' { ... }
to
node default { ... }
i.e. without the single quotes, as suggested? And afterwards restarted
the Puppetserver process by means of, e.g. systemctl restart puppetserver?
If so, and this hasn't helped, you may want to try to narrow the problem
down by simplifying the default node manifest even more, by making
site.pp look like this (verbatim):
node default {
fail('Failing deliberately on default node manifest')
}
Don't forget to restart the Puppetserver after that to make sure the
change is picked up.
When you then run the Puppet agent on the troublesome node it should
fail hard with the message defined above. If it does then you know at
least that site.pp is read and a catalog is created and applied for that
node. If it does not then there must be something else amiss that is not
obvious from the information and details you posted.
HTH
Andreas
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/48f7aa63-ed60-d5c8-d36c-d302c01d4130%40ptmx.org.
signature.asc
Description: OpenPGP digital signature
