I saw an error like this when the client was 0.25.x and the server was 0.24.x.
On Apr 26, 2010, at 9:06 PM, Grzegorz Marszałek wrote:
> Hello!
>
> What does this error means?
>
> err: Could not retrieve catalog from remote server: Could not intern from
> pson: Could not convert from pson: Cou
"Gabriel - IP Guys" writes:
> Dear Guys (and girls and autobots),
>
> I look at the issues that some people have on this list, and I am genuinely
> embarrassed to post my issues!
As Mike says, don't be: everyone has to start somewhere, and you are
apparently interested and brave enough to give a
Thomas Bellman writes:
> On 2010-04-26 13:08, Yann wrote:
>
>> It seems my puppet is running with an incorrect locale:
>>
>> LANG=C
>> [...]
>> LC_MESSAGES=C
>> [...]
>> LC_ALL=C
>>
>> r...@venice:/tmp# /usr/bin/vmbuilder kvm ubuntu
>> 2010-04-26 11:58:14,501 INFO: Cleaning up
>> locale-gen do
Hello!
What does this error means?
err: Could not retrieve catalog from remote server: Could not intern
from pson: Could not convert from pson: Could not find relationship
target "Nagios_hostgroup[]"
I cannot find it anywhere in my config... I have only 2
nagios_hostgroups, exported to s
Should the following approach to optionally including site-specific
information in modules work? It's the third pattern documented at
http://serialized.net/2009/07/puppet-module-patterns/
In my case, I have
modules/manifests/ntp/init.pp
import "classes/*"
if ($ntp_servers) {
$servers = $ntp_s
On Tue, Apr 27, 2010 at 1:03 AM, R.I.Pienaar wrote:
>
> puppet really needs a downcase function.
>
> --
>
> module Puppet::Parser::Functions
newfunction(:downcase, :type => :rvalue) do |args|
args[0].downcase
end
end
Ohad
--
You received this message because yo
AFAIK, it does get evaluated each time :)
On Tue, Apr 27, 2010 at 8:02 AM, James Turnbull wrote:
> On 27/04/2010 2:17 AM, R.I.Pienaar wrote:
>
>>
>> - "Douglas Garstang" wrote:
>>
>> I wasn't able to get this to run for only CentOS. I tried a few
>>> different things in the site.pp. I wish
On 27/04/2010 2:17 AM, R.I.Pienaar wrote:
- "Douglas Garstang" wrote:
I wasn't able to get this to run for only CentOS. I tried a few
different things in the site.pp. I wish I could put a case statement
site.pp is a special file, it doesn't get evaluated on every run the same way
that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/10 7:42 AM, Sebastian Kayser wrote:
> Greetings,
>
> I am new to the Redmine Wiki which powers the Puppet Wiki. I wanted to
> fix a link in the Downloading Puppet -> Solaris section [1], but when I
> try to edit the page, the shown page sourc
Greetings,
I am new to the Redmine Wiki which powers the Puppet Wiki. I wanted to
fix a link in the Downloading Puppet -> Solaris section [1], but when I
try to edit the page, the shown page source / markup doesn't match with
what is listed as valid markup in the editing help [2]. Headings use
onl
I hate this bug. This is actually just cosmetic. There are two easy ways to
fix it.
1) Set puginsync to false on every client. (Using puppet)
2) Setup an plugin folder.
I recommend just using 1 for now, and dealing with it later since it's just a
cosmetic bug until you try to use plugins.
A
>
> Apr 26 11:12:36 ext-web1.fr.xxx.com puppetd[17974]: Starting Puppet
> client version 0.24.5
> Apr 26 11:12:37 ext-web1.fr.xxx.com puppetd[17974]:
> (/File[/var/lib/puppet/lib]) Failed to retrieve current state of
> resource: No specified source was found from puppet://puppet/plugins
> Apr 26 11
Running puppet on ubuntu for the first time. Getting this.
Apr 26 11:12:36 ext-web1.fr.xxx.com puppetd[17974]: Starting Puppet
client version 0.24.5
Apr 26 11:12:37 ext-web1.fr.xxx.com puppetd[17974]:
(/File[/var/lib/puppet/lib]) Failed to retrieve current state of
resource: No specified source wa
Your site.pp should look like:
include os::setup
Package {
require => Class["os::setup"]
}
other wise the classes is not avaiable, how should puppet set a relation to
something that is not included in its manifests?
Oh, well... that's also ugly. :(
what?
--
You received this message b
On Mon, Apr 26, 2010 at 10:51 AM, Peter Meier wrote:
> Your site.pp should look like:
>
> include os::setup
> Package {
> require => Class["os::setup"]
> }
>
> other wise the classes is not avaiable, how should puppet set a relation to
> something that is not included in its manifests?
Oh,
begin
We do offer public training courses. I think its the best way to
understand how to use Puppet (but I am biased since I teach the course :) ).
end #shameless plug
On Mon, Apr 26, 2010 at 7:20 AM, Mike Pountney wrote:
> Hi Gabriel,
>
> Please post away, the list is very friendly to newbs, a
Your site.pp should look like:
include os::setup
Package {
require => Class["os::setup"]
}
other wise the classes is not avaiable, how should puppet set a
relation to something that is not included in its manifests?
cheers pete
--
You received this message because you are subscrib
On Mon, Apr 26, 2010 at 8:51 AM, Bernd Adamowicz <
bernd.adamow...@esailors.de> wrote:
> OK. Actually it worked when I added:
>
>
> $hibernate_connection_dialect=$templates_eval::providevars::hibernate_connection_dialect
>
> This solves the base problem but at the same time creates another one: I
On Mon, Apr 26, 2010 at 10:45 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>> So, apparently the net-snmp module can't find os::setup class. Not
>> sure why...
>
> you need to include it somewhere first.
>
> most people have some kind of common class they include on all machines,
>
- "Alan Barrett" wrote:
> On Mon, 26 Apr 2010, R.I.Pienaar wrote:
> > puppet really needs a downcase function.
>
> $var = "Mixed CaSe sTUff"
> $downcased_var = inline_template("<%= var.downcase %>")
obvious, and obviously ugly :)
--
You received this message because you are subscribed to
- "Douglas Garstang" wrote:
> So, apparently the net-snmp module can't find os::setup class. Not
> sure why...
you need to include it somewhere first.
most people have some kind of common class they include on all machines, you'd
include it there
--
R.I.Pienaar
--
You received this mes
On Mon, 26 Apr 2010, R.I.Pienaar wrote:
> puppet really needs a downcase function.
$var = "Mixed CaSe sTUff"
$downcased_var = inline_template("<%= var.downcase %>")
--apb (Alan Barrett)
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post t
On Mon, Apr 26, 2010 at 10:23 AM, Douglas Garstang
wrote:
> On Mon, Apr 26, 2010 at 10:20 AM, R.I.Pienaar wrote:
>>> and I include it in every single module (shame I can't include it at
>>> site.pp). As far as I know, including one class in another does not
>>> guarantee that the other class gets
Well that's weird and mildly confusing. The class is opsys::centos but
we're really including opsys::CentOS. Nice.
because puppet can't have any classes started with capitalized letters
(global resource identifier clash) and anything else behind is anyway
downcased (class tEST == class test)
On Mon, Apr 26, 2010 at 10:20 AM, R.I.Pienaar wrote:
>> and I include it in every single module (shame I can't include it at
>> site.pp). As far as I know, including one class in another does not
>> guarantee that the other class gets evaluated first, even though the
>> other class has a default P
> and I include it in every single module (shame I can't include it at
> site.pp). As far as I know, including one class in another does not
> guarantee that the other class gets evaluated first, even though the
> other class has a default Package{} or does it? Docs on this
> stuff in puppet a
- "Peter Meier" wrote:
> > right, classes cant have Caps as the first char (or maybe even
> > anywhere? not sure).
> >
> > anyway, you'd probably need to look at a case statement then that
> > includes opsys::centos for $operatingsystem == CentOS and similar
> > for your other operatin
On Mon, Apr 26, 2010 at 10:03 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>
>> Apr 26 09:58:15 s_...@app09.fr.xxx.com puppetd[12785]: Could not
>> retrieve catalog: Syntax error at '::CentOS' at
>> /etc/puppet/modules/opsys/manifests/init.pp:1 on node
>> app09.fr.xxx.com
>>
>> wher
right, classes cant have Caps as the first char (or maybe even
anywhere? not sure).
anyway, you'd probably need to look at a case statement then that
includes opsys::centos for $operatingsystem == CentOS and similar
for your other operating systems. :(
puppet does that already for us:
$
On Mon, Apr 26, 2010 at 10:02 AM, Peter Meier wrote:
>> class opsys::CentOS {
>
> class opsys::centos {
But...
app09 ~:# facter | grep "operatingsystem =>"
operatingsystem => CentOS
facter reports CentOS, not centos
Doug.
--
You received this message because you are subscribed to the Google
- "Douglas Garstang" wrote:
> Apr 26 09:58:15 s_...@app09.fr.xxx.com puppetd[12785]: Could not
> retrieve catalog: Syntax error at '::CentOS' at
> /etc/puppet/modules/opsys/manifests/init.pp:1 on node
> app09.fr.xxx.com
>
> where the include has:
>
> include "opsys::${operatingsystem}"
>
class opsys::CentOS {
class opsys::centos {
cheers pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr.
On Mon, Apr 26, 2010 at 9:55 AM, Peter Meier wrote:
>
>> include opsys::$operatingsystem
>
> include "opsys::${operatingsystem}"
Well, that's weird. Now I am getting this:
Apr 26 09:58:15 s_...@app09.fr.xxx.com puppetd[12785]: Could not
retrieve catalog: Syntax error at '::CentOS' at
/etc/puppet
include opsys::$operatingsystem
include "opsys::${operatingsystem}"
cheers pete
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email t
On Mon, Apr 26, 2010 at 9:48 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>
>> include opsys::$operatingsystem
>
> they are, you didnt read my example properly.
Ah, quotes...
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To po
- "Douglas Garstang" wrote:
> include opsys::$operatingsystem
they are, you didnt read my example properly.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscrib
On Mon, Apr 26, 2010 at 9:31 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>
>> On Mon, Apr 26, 2010 at 9:17 AM, R.I.Pienaar wrote:
>> >
>> > - "Douglas Garstang" wrote:
>> >
>> >> I wasn't able to get this to run for only CentOS. I tried a few
>> >> different things in the sit
On Mon, Apr 26, 2010 at 9:37 AM, Julian Simpson wrote:
>
>> The first poster said he would include os::centos in his module. What
>> happens if the module might be running on either CentOS or Ubuntu? I
>> don't think 'include os::centos' will work so great on an Ubuntu
>> system. How do you make i
- "Douglas Garstang" wrote:
> On Mon, Apr 26, 2010 at 9:31 AM, R.I.Pienaar wrote:
> >
> > - "Douglas Garstang" wrote:
> >
> >> On Mon, Apr 26, 2010 at 9:17 AM, R.I.Pienaar
> wrote:
> >> >
> >> > - "Douglas Garstang" wrote:
> >> >
> >> >> I wasn't able to get this to run for only
On Mon, Apr 26, 2010 at 9:31 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>
>> On Mon, Apr 26, 2010 at 9:17 AM, R.I.Pienaar wrote:
>> >
>> > - "Douglas Garstang" wrote:
>> >
>> >> I wasn't able to get this to run for only CentOS. I tried a few
>> >> different things in the sit
> The first poster said he would include os::centos in his module. What
> happens if the module might be running on either CentOS or Ubuntu? I
> don't think 'include os::centos' will work so great on an Ubuntu
> system. How do you make it dynamic?
>
By using the $operatingsystem variable in the in
- "Douglas Garstang" wrote:
> On Mon, Apr 26, 2010 at 9:17 AM, R.I.Pienaar wrote:
> >
> > - "Douglas Garstang" wrote:
> >
> >> I wasn't able to get this to run for only CentOS. I tried a few
> >> different things in the site.pp. I wish I could put a case
> statement
> >
> > site.pp is
On Mon, Apr 26, 2010 at 9:17 AM, R.I.Pienaar wrote:
>
> - "Douglas Garstang" wrote:
>
>> I wasn't able to get this to run for only CentOS. I tried a few
>> different things in the site.pp. I wish I could put a case statement
>
> site.pp is a special file, it doesn't get evaluated on every run
- "Douglas Garstang" wrote:
> I wasn't able to get this to run for only CentOS. I tried a few
> different things in the site.pp. I wish I could put a case statement
site.pp is a special file, it doesn't get evaluated on every run the same way
that classes would get.
So variables like $ope
On Mon, Apr 26, 2010 at 8:58 AM, Julian Simpson wrote:
>
>> I wasn't able to get this to run for only CentOS. I tried a few
>> different things in the site.pp. I wish I could put a case statement
>> inside the exec, but puppet doesn't like that. So, below is what I had
>> originally... how can I g
> I wasn't able to get this to run for only CentOS. I tried a few
> different things in the site.pp. I wish I could put a case statement
> inside the exec, but puppet doesn't like that. So, below is what I had
> originally... how can I get the exec["yum-clean-all"] to only run for
> CentOS and not
OK. Actually it worked when I added:
$hibernate_connection_dialect=$templates_eval::providevars::hibernate_connection_dialect
This solves the base problem but at the same time creates another one: I do not
have to include variables from only one class but depending one some
environment settings
We've been pretty much a homogenous CentOS environment until recently.
Actually, we've had a mixture of CentOS, Ubuntu and Debian because a
previous admin thought this would be 'fun'. G. Anyway, I tried to
add an Ubuntu system for the first time. My site.pp file has a 'yum
clean all' dependency
Hi Gabriel,
Please post away, the list is very friendly to newbs, and you should find your
question answered, no matter what your level of puppet understanding is. We've
all been there at some point!
The IRC channel is also a great resource, there's typically several folk on
there willing to h
Dear Guys (and girls and autobots),
I look at the issues that some people have on this list, and I am
genuinely embarrassed to post my issues! I'm only trying to write some
simple recipies, that do things like install basic software and such,
but some of the code snippets posted, do not seem fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all
In one of those "should have been doing better things with my time"
moments I got frustrated with creating HTTP authentication files
with htpasswd and htdigest. So I created a Puppet type to manage
them. You can find the code (including tests!
On 26 Apr 2010, at 12:24, Bernd Adamowicz wrote:
> Hi all,
>
> given these two classes inside the file
> '/etc/puppet/modules/templates_eval/manifests/init.pp':
>
> 53 class templates_eval::providevars {
> 54
> 55
> $hibernate_connection_dialect="org.hibernate.dialect.Oracle1
On Mon, Apr 26, 2010 at 4:24 AM, Bernd Adamowicz <
bernd.adamow...@esailors.de> wrote:
> Hi all,
>
> given these two classes inside the file
> '/etc/puppet/modules/templates_eval/manifests/init.pp':
>
> 53 class templates_eval::providevars {
> 54
> 55
> $hibernate_connection_dialect="o
On 2010-04-26 13:08, Yann wrote:
It seems my puppet is running with an incorrect locale:
LANG=C
[...]
LC_MESSAGES=C
[...]
LC_ALL=C
r...@venice:/tmp# /usr/bin/vmbuilder kvm ubuntu
2010-04-26 11:58:14,501 INFO: Cleaning up
locale-gen does not recognize your locale 'C'
"C" is a very much va
Yann writes:
> Hello Patrick, thank you very much for your help. I tested everything you
> said without much success. I ended up replacing my command by an "env" and
> reproducing the puppet's shell environment variable in my shell to see if
> that could have an impact. It seems my puppet is run
Hi all,
given these two classes inside the file
'/etc/puppet/modules/templates_eval/manifests/init.pp':
53 class templates_eval::providevars {
54
55
$hibernate_connection_dialect="org.hibernate.dialect.Oracle10gDialect"
56 }
57
58 class templates_eval::testva
Hello Patrick, thank you very much for your help. I tested everything
you said without much success. I ended up replacing my command by an
"env" and reproducing the puppet's shell environment variable in my
shell to see if that could have an impact.
It seems my puppet is running with an incorrect l
On Apr 25, 2010, at 11:32 AM, Yann wrote:
> Hello, I am trying to create a VM using puppet and vmbuilder. I've got
> the following declaration (now very simplified):
>
> define virtual_machine ($ip) {
>exec {"create_vm_${name}":
>command => "/usr/bin/vmbuilder kvm ubuntu -d CNDR -v -
58 matches
Mail list logo
