Are you sure that SUDO has permissions on every aspect of your computer?
Have you tried as root?
Is the SQLite 3 driver installed?
Regards
2011/10/18 Chris
> Hi,
>
> I'm getting the following error when I try to set up stored
> configurations. It appears in the master logs when the agent proces
Hi,
I am using the cloud provisioner to bootstrap some ec2 nodes, and these
clients are signed using a randomly generated certname, which is put in
/etc/puppet.conf at the bootstrap time (eg certname =
d7bcd693-73fd-495f-0876-ff91ea1e).
But my puppet code repo also manages the puppet.conf fil
I created a feature request https://projects.puppetlabs.com/issues/10167
On 19 oct, 11:06, Alexandre Fouché wrote:
> Hi,
>
> I am using the cloud provisioner to bootstrap some ec2 nodes, and these
> clients are signed using a randomly generated certname, which is put in
> /etc/puppet.conf at the
On Mon, 17 Oct 2011 17:53:39 +0200
Martijn Grendelman wrote:
> Hi,
Hi,
[...]
> These give me errors like:
>
> Could not parse for environment production: Could not match
> ${::operatingsystem} at...
Where are you setting those vars?
I've seen that, on 2.6, setting those vars in selectors doe
Sent to early :-)
source => $::operatingsystem ? {
*without quotes.
> Isn't that supposed to work?
>
> Best regards,
> Martijn Grendelman
HTH,
Arnau
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to pupp
Why not use RVM ? It wll be easy to create a ruby env with its gems.
It is in /usr/local and completely independant from the system ruby
and all gems. I enforce not putting any files on the system which are
not part of a RPM.
For example, i use the puppetmaster and puppet rpms, so that both run
an
Why not use RVM ? It wll be easy to create a ruby env with its gems.
It is in /usr/local and completely independant from the system ruby
and all gems. I enforce not putting any files on the system which are
not part of a RPM.
For example, i use the puppetmaster and puppet rpms, so that both run
an
$operatingsystem
"$operatingsystem"
"${operatingsystem}"
${operatingsystem}
Produce exactly the same thing.
One would assume that the short forms for expression interpolation i.e.:
${operatingsystem}
"$operatingsystem"
would recognize an initial empty namespace (i.e. "::operatingsystem").
If not
I am in an environment that has a development, QA, and production
sub-environments.
All machines are built in "dev" then moved to qa/prod as needed.
Because a machine's IP and hostname changes in this move, I set up certnames
that are the machine's MAC address.
I use cobbler to set up the machin
Creating your own init script if one is not provided is definitely the best
approach; but failing that, you can still use the "service" resource as a
glorified exec; I've done this w/ my arpwatch daemon on redhat boxes since
it's otherwise difficult to run multiple arpwatch daemons:
##
# maintains
Hi,
I was previously using an EC2 AMI where i was logging as root, and i
could bootstrap nodes.
I am now using Amazon AMIs ( http://aws.amazon.com/fr/amazon-linux-ami
) and they require login as ec2-user.
The problem is that if i run puppet node bootstrap --login ec2-user,
it will detect it and ru
On Wed, Oct 19, 2011 at 2:06 AM, Alexandre Fouché <
alexandre.fou...@gmail.com> wrote:
> Hi,
>
> I am using the cloud provisioner to bootstrap some ec2 nodes, and these
> clients are signed using a randomly generated certname, which is put in
> /etc/puppet.conf at the bootstrap time (eg certname =
RPM itself does not mean that there is a service. A service is an init
script that is placed in /etc/init.d and the appropriate installation
commands used.
You could create an init script and then execute chkconfig --add
that will add it. You need a header in the init
script that is parsed by chk
The documentation says:
"Defined types have a number of built-in variables available, including
$name and $title, which are set to the title of the resource when it is
declared."
How can I find out what the other "built-in variables" are?
Is it the meta parameters?
I Understand that since 2.6
I got it installed in the end:
1) Only install dev libraries for the architecture you are using (gcc
and mysql dev)
2) Gems from source (not RPM) were used
3) Active record can not be the latest version (down grade was required)
The only other option is to roll your own RPM or scavenge them from
Great, i had not seen this one, thank you !
On 19 oct, 18:18, Nigel Kersten wrote:
> On Wed, Oct 19, 2011 at 2:06 AM, Alexandre Fouché <
>
>
>
>
>
>
>
>
>
> alexandre.fou...@gmail.com> wrote:
> > Hi,
>
> > I am using the cloud provisioner to bootstrap some ec2 nodes, and these
> > clients are sig
On Wed, Oct 19, 2011 at 1:07 PM, Alexandre wrote:
> Great, i had not seen this one, thank you !
>
>
It should be significantly easier to find out this info, it's not you :)
In an ideal world you could run a command as simple as "facter -p" to get
access to all of these variables, but not all make
Hey, Henrik.
Argh, the language guide. Anyway, I was about to say $title and $name
were the only ones, but then I remembered $module_name and
$caller_module_name (http://docs.puppetlabs.com/guides/faq.html#are-
there-variables-available-other-than-those-provided-by-facter). Those
MIGHT be what the
I'm currently working on automating our Nagios monitoring with Puppet.
My plan is to have three different Nagios servers... one in each data
center. I'd like to have the Chicago (location => 'CH3') Nagios
server only monitor servers who also reside in that data center.
My question is, how do I g
I agree; try as root.
Also, what does your puppet.conf look like on the puppet master?
Kevin.
On Oct 18, 6:07 am, Chris wrote:
> Hi,
>
> I'm getting the following error when I try to set up stored
> configurations. It appears in the master logs when the agent process
> runs.
>
> $ sudo /usr/sbi
Hello,
You can use the "tag" argument to mark different resources and then
collect only the resources with a certain tag.
See an example on this page:
http://docs.puppetlabs.com/guides/exported_resources.html
On 11-10-19 05:48 PM, Kevin Wolf wrote:
> I'm currently working on automating our Nagi
21 matches
Mail list logo
