do with my playing
with certname, etc.
I'm aware that this thread has become a bit helper-unfriendly. I've
followed on really only for future readers who may find the question and
wonder whether anything further was known.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255<-- only
On Thursday, 18 February 2016 05:18:19 UTC+1, Henrik Lindberg wrote:
>
> On 18/02/16 02:10, warron.french wrote:
> > Can someone please clearly explain why/when to use:
> > puppet apply versus Puppet agent?
> >
>
> puppet agent makes requests to the master - the master compiles the
> catalog.
temporarily out of ideas and search queries. If anyone can shed any
light, I'd much appreciate it. If not, this all at least serves to
document for those who search these things later.
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255<-- only when I'm in the UK
http://ml-week.com
puppet/ssl/loire.example.com.pem" /f
2. puppet agent -t
Exiting; failed to retrieve certificate and waitforcert is disabled
1,[T] jeff@loire:~ $
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 255<-- only when I'm in the UK
http://ml-week.com/ <http://www.ml-week.com/>* prochaine edition,
host's
A record, there's a CNAME called puppet. (Note that telnetting to
loire.example.com 8140 connects: the tcp6 is a netstat artefact as far as I
know.)
Reflection, poking, and googling are drawing blanks for me. Any
suggestions ?
Jeff Abrahamson
+33 6 24 40 01 57
+44 7920 594 2
On 15 February 2016 at 17:44, Toni Schmidbauer
wrote:
> Jeff Abrahamson writes:
> > 1. The puppet master is running under apache2. I assume it's healthy,
> > in so much as it doesn't complain and I'm serving on 8140. But I'd
> > love a better way to conf
n a similar vein, I'd like to do automated testing for the master as
well. So this is (1) and (2) together, since I'm not sure how to test the
master.
4. Our github repository is private. Is standard (best) practice to give
the puppet master ssh keys to github without passphrase? Ca
