The puppet agent writes its own pidfile, to $vardir/run/agent.pid
depending on what is in puppet.conf. If you are seeing problems with
that, I would encourage you to open a bug upstream.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Sorry, I should have said pidfile is written to $rundir/agent.pid.
$rundir defaults to $vardir/run if not specified in puppet.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
That looks like a bug with the puppet-alternatives module. There is
already a github issue open at https://github.com/adrienthebo/puppet-
alternatives/pull/3 that looks like it covers this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This is probably related to upstream bug
https://projects.puppetlabs.com/issues/21337
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1215282
Title:
Possible puppet performance
no-rubygems patch
-- Stig Sandbeck Mathisen s...@debian.org Mon, 04 Mar 2013 08:48:15
+0100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1143009/+subscriptions
--
Matthaus Owens
Release Manager, Puppet Labs
--
You received this bug
Andrea,
Can you post the output of your puppet run using `puppet agent -t --trace
--debug` on the agent? That might help figure out what's going on.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Andrea,
The first example was master and agent on the same machine, so it found the
module in the modulepath without pluginsync. The second example was agent and
master on different machines.
Can you post the output of your puppet.conf and `puppet agent -t --trace
--debug` on the agent? That
And running it from a remote agent had the correct content as well once
pluginsync=true was added to the agent's puppet.conf.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286
So if the problem is that custom facts don't get to agents by default
after installing the puppet package, a solution could be to add
pluginsync=true to the puppet.conf in the package, but that might be
surprising to users, depending on what behavior they expect.
Side note: pluginsync defaults to
Robie,
I used a puppetmaster in both cases. In the first example the agent and master
were on the same sytem, in the second they were on seperate systems.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
10 matches
Mail list logo
