I'm trying to debug a new ENC setup. I created a short perl script to
output a few lines of YAML. It runs fine on the puppet server but when I
try it on a client I get this error:
Warning: Error 400 on SERVER: Failed to find client.domain.org via exec:
Execution of the '/etc/puppet/ENC/plug0.pl
:
>
>
>
>
> On Mon, Feb 3, 2014 at 9:45 AM, Jon Yeargers
> > wrote:
>
>> Right. So how would I declare this dependency setup if I stop using node
>> files?
>>
>
> Even if you use an ENC, Puppet will still consult your site manifest, so
> using an ENC does
?
>
> Regards,
> El 03/02/2014 16:13, "Jon Yeargers" >
> escribió:
>
>> I need to convert my resource based system to ENC. It's mostly
>> straightforward but I'm not sure how to handle operations like these:
>>
>> Class['apt']
I need to convert my resource based system to ENC. It's mostly
straightforward but I'm not sure how to handle operations like these:
Class['apt'] -> Package<| |>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group a
I corrected the problem by including this in my /etc/init.d/
I have a group of services that are supposed to be maintained by puppet
agent. Up until I moved from 2.6 to 3.4 they were kept up to date and
running (as expected).
Since the upgrade of the puppet agent these services are no longer being
monitored. I'm sure that the server is still seeing the f
Running 'puppet agent --test' - after 5-10 minutes of execution this error
appeared:
err: Could not run Puppet configuration client: execution expired
When I ran the same command the execution resumed and continued to
completion.
--
You received this message because you are subscribed to the
I'm using the puppetforge 'apt' module to deal with some repositories. It
has 'always-apt-update' as a property and I've had it set to 'true' but I'm
wondering what happens if I don't.
Is the puppet package manager 'smart' enough to get the latest versions of
packages that it's monitoring ('en
Answer here:
http://stackoverflow.com/questions/14607385/puppet-does-not-start-a-service-varnish-when-puppet-apply-is-run
On Friday, December 13, 2013 11:07:01 AM UTC-8, Jon Yeargers wrote:
>
> Just out of curiosity I created my own 'dmidecode' package with a trivial
ithout
> this dependency
> b) fetch all deb packages you require and install them in one go using
> dpkg -i --force-depends or similar.
>
> Option (a) is simple if you're versed in the creation of Debian
> packages, and pretty difficult if you're not.
>
So am I SOL on this? Is ARM considered an 'unsupported architecture' until
I can create a 'dmidecode' for this platform?
On Wednesday, December 11, 2013 10:55:11 AM UTC-8, Jon Yeargers wrote:
>
> I can wget and install facter but the issues continue:
>
> root@
11, 2013 9:50:07 AM UTC-8, Jeff Bachtel wrote:
>
> You can fetch it directly (wget, curl, whatever) from
>
>
> http://apt.puppetlabs.com/pool/squeeze/main/f/facter/facter_1.6.18-1puppetlabs1_all.deb
>
> Jeff
>
> On 12/11/2013 12:39 PM, Jon Yeargers wrote:
>
> root@plug
cking depends. The puppet install should succeed after that.
>
> I think facter's dmidecode dependency should be a Suggests vice a Depends,
> and it might be worth filing a bugrep to get it changed.
>
> Jeff
>
>
> On 12/11/2013 10:31 AM, Jon Yeargers wrote:
>
> I
epends : dmidecode but it is not installable
If I do 'apt-cache search dmidecode' it isn't available.
On Wednesday, December 11, 2013 7:26:02 AM UTC-8, Jon Yeargers wrote:
>
> 'apt-get update' ran fine this time.
>
> 'apt-get install puppet'
On Tue, Dec 10, 2013 at 12:01 PM, Moses Mendoza
> >
> wrote:
> > On Tue, Dec 10, 2013 at 10:52 AM, Jon Yeargers
> > >
> wrote:
> >> I updated the repository file using the official puppet-recommended
> version.
> >> The corrected line is:
>
>
> Have you tried the instructions here:
>
> http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-debian-and-ubuntu
>
>
> Because what apt is making of your configuration is plain wrong.
>
> On 12/10/2013 05:50 PM, Jon Yeargers wrote:
> > I
achine and then
rebuild the package file myself in a private repository.
On Tuesday, December 10, 2013 8:22:36 AM UTC-8, Jon Yeargers wrote:
>
> I've tried using 'gem' to install the latest build but it brings down lots
> of (seemingly) unnecessary bits with it. (examples,
eadache.
>
> Jeff
>
>
> On Thu, Dec 5, 2013 at 7:29 PM, Jon Yeargers
> > wrote:
>
>> After I got puppetdb working I was looking about at the various bits of
>> data available. Looking at the 'nodes' option I was suprised to see this:
>>
I've tried using 'gem' to install the latest build but it brings down lots
of (seemingly) unnecessary bits with it. (examples, docs, etc)
On Thursday, December 5, 2013 9:16:15 AM UTC-8, Jon Yeargers wrote:
>
> I'm looking to deploy several hundred ARM based machines
On further inspections the YAML files are still being created but not the
puppet db entries.
On Thursday, December 5, 2013 4:29:44 PM UTC-8, Jon Yeargers wrote:
>
> After I got puppetdb working I was looking about at the various bits of
> data available. Looking at the 'nodes
After I got puppetdb working I was looking about at the various bits of
data available. Looking at the 'nodes' option I was suprised to see this:
"report_timestamp" : null
for every node. They all have this for their puppet.conf:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/va
(This is actually two questions):
Running 'puppet agent --test' on a 1Ghz ARM based (Debian 6) fanless PC.
It's pretty common to see the 'catalog run' take 120-300 seconds. Is this
typical?
Second (and possibly related): when I do a 'puppet agent --test (--noop)' I
get this set of messages:
d the results of running
> puppetdb-ssl-setup ... the more information the better in these kinds
> of cases.
>
> Also - is PuppetDB listening to port 8080?
>
> On Thu, Dec 5, 2013 at 9:15 PM, Jon Yeargers >
> wrote:
> > I used 'puppetdb-ssl-setup' (afte
cally, so try
> this first. For ssl-host I usually recommend something like ::1 or
> 0.0.0.0 to listen on all ports for simplicity, but you can make this
> explicit if you like.
>
> ken.
>
>
>
> On Thu, Dec 5, 2013 at 7:48 PM, Jon Yeargers >
> wrote:
> &g
I did `yum update` on my puppet server about a week ago. Up to that point I
had puppet and puppetdb running on the same machine. Since the update
puppetdb doesn't appear to be listening on port 8081 anymore.
When I run `puppet agent --test` on a client I get this error:
err: Could not retri
I'm looking to deploy several hundred ARM based machines in the near
future. At this point the puppet agent version available via apt (Debian 6)
is 2.6.
I tried adding the apt.puppetlabs.com repository but it won't install on my
systems as the CPU type isn't supported.
What are my options t
26 matches
Mail list logo
