I found the issue, digging more through the files that the puppet client
service was accessing, I found that /etc/sysconfig/puppet was being
referenced,
PUPPET_EXTRA_OPTS="--server @@PUPPET4_SERVER@@"
I checked our other servers that were working and found that those
referenced the fqdn of
That might be getting closer to the issue, the agent runs as the user
'puppet' but I'm running the agent manually as root...our other systems
work fine in this config though, I'm looking for what files might have the
wrong permissions for this but so far not finding any differences.
On
Is the puppet agent running as the same user when run as a daemon and when
run via 'puppet agent' from the command line? I've seen that make a
difference.
On Monday, 3 July 2017 15:49:06 UTC+2, aaron@gmail.com wrote:
>
>
>>>
>>>
--
You received this message because you are subscribed to
Thanks Peter, I may be running into a different problem now,
in /var/log/messages I get the error:
puppet-agent[808]: Could not request certificate: getaddrinfo: Name or
service not known
which seems to indicate issues resolving my master address, but I have no
trouble resolving the hostname
You can specify which client certificate(s) to clean by means of:
# puppet cert clean
On Friday, 16 June 2017 00:31:57 UTC+2, aaron@gmail.com wrote:
>
> I'm running into an issue on one of our puppet4 servers where the agent
> only works when run as 'puppet agent -t' but fails when run
