Le mercredi 05 août 2009 à 22:53 -0700, robbyt a écrit :
> Hello All!
>
> I would like to automatically add a header to all files/templates that
> puppet manages on my servers. Something like "#if you break, my puppet
> will fix it!!"
>
> Is this possible?
Probably by creating a custom type that
In 0.24.8 the only thing that file is trying to do is include active
record (at least so it seems from my limited understanding of ruby and
from the comments). It was a guess that it was related :">. I was
outlining the bug because it took me a few hours of head scratching
before I figured out
On Thu, Aug 6, 2009 at 1:53 AM, robbyt wrote:
>
> Hello All!
>
> I would like to automatically add a header to all files/templates that
> puppet manages on my servers. Something like "#if you break, my puppet
> will fix it!!"
>
> Is this possible?
Not sure if this is the best way, but you could s
Hi all,
I'm running into some weird problems with a hostname.
We have a host with a hostname "mailpop.server.net", and it has NIS
configured with the NIS domainname "server.nl".
If i clear the nis domainname, and run puppet, it will create a
certificate request for mailpop.server.net. After con
templates can accept a multiple list of erb files, therefor you could easly
create a define that always include another template(header)
for example (its up to you to test if it works ;))
define mytemplate($template) {
file {$name:
content => template("my header file",$template),
}
}
and
it depends on the version of facter that you have, older version of facter
just used the output from domainname.
newer try first the dnsdomainname and fallback to the domainname.
to be safe, use the cert option in your puppet.conf
Ohad
On Thu, Aug 6, 2009 at 9:50 PM, Kai wrote:
>
> Hi all,
>
>
Hi Ohad,
On Aug 6, 3:52 pm, Ohad Levy wrote:
> it depends on the version of facter that you have, older version of facter
> just used the output from domainname.
> newer try first the dnsdomainname and fallback to the domainname.
>
As far as I know the command 'domainname' doesn't ever relate t
I'm afraid it does. :(
On Aug 6, 4:24 pm, Kai wrote:
> > to be safe, use the cert option in your puppet.conf
>
> That will be interesting: that file is supplied by puppet. Will the
> hostname in puppet reflect the real hostname, or will it again
> formulate its own by putting the NIS domain in i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kai wrote:
> Hi Ohad,
>
> On Aug 6, 3:52 pm, Ohad Levy wrote:
>> it depends on the version of facter that you have, older version of facter
>> just used the output from domainname.
>> newer try first the dnsdomainname and fallback to the domainname.
So what's LISA like for config management talks? I've seen a few
papers that came out of it that I've found less than useful, but am
interested in hearing whether people think it is worthwhile to
attend
--
Nigel Kersten
nig...@google.com
System Administrator
Google, Inc.
--~--~-~--~
After some digging, it turns out there's some weird incompatibility
between ActiveRecord 2.3.3 and one of the postgres drivers. I downgraded
to ActiveRecord 2.3.2 and passed this hurdle.
seph
seph writes:
> I manually installed a newer ActiveRecord and ActiveSupport on my
> puppetmaster, and t
I spent a bit longer poking at this. I think I found 2 closely related
bugs. Both are listed on #2508.
The first, is that lib/puppet/defaults.rb incorrectly states the
requirement as being for 2.3. This should be something else. (probably
2.1)
The second is that the mechanism puppet/feature/rail
Continuing in my 0.25.0rc1 saga, I'm now running into a problem with
module custom types.
I use the iptables module, which creates an iptables.rb module. In
0.24.8 this all worked fine. But, since upgrading my puppetmaster, it
fails on both 0.24.8 and 0.25.0rc1 clients. puppetmaster complains tha
LISA is very much hit and miss.
You can meet some great contacts and get some excellent insight into
what's going on in the larger SA community. But, you can also waste a
bunch of time with people that are so ingrained in their outmoded
ideas that you feel like you wasted your time completely.
I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
5.2. I have two nodes, one x86_64 and one ppc64, that have the client
running and they are checking in regularly as expected. I have a
minimal site.pp file which defines the owner, group and permissions on
several files. Changes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
seph wrote:
> Continuing in my 0.25.0rc1 saga, I'm now running into a problem with
> module custom types.
>
> I use the iptables module, which creates an iptables.rb module. In
> 0.24.8 this all worked fine. But, since upgrading my puppetmaster, it
>
Hi all
I've moved the UPGRADE document from the wiki to a more Release Notes
style (UPGRADE was a bit misleading):
http://reductivelabs.com/trac/puppet/wiki/ReleaseNotes
Hopefully this will help people understand what's new and changed in
releases.
Comments and feedback welcomed.
Regards
Jame
James Turnbull writes:
>> Does anyone module custom types working in 0.25?
>
> I do. Can you provide some stack traces and your configuration?
I'd rather not tar my entire configuration, so I'll try describing
it. I'm sorry if I miss an important part.
I'm basically using the iptables module
Hello there
I'm having a problem (again). At my site we are maintaining RHEL,
CentOS and Solaris hosts, with in the future possibly some FreeBSD
also being added into the mix. To this end instead of constantly
branching whenever running a command on the console (or remembering
where it is located
Hi,
I trying to convert a basic install of my puppetmasterd from WEBrick
to Phusion. Here's what I did and here's what's not working anymore.
You help is greatly appreciated.
---
Thanks,
Allan Marcus
505-667-5666
Starting with Mac OS X server 10.5.7 I install puppet and facter. I
create
Allan, when I got it running on OS X Server, I *only* installed
Passenger from source, not from gem at all.
On Thu, Aug 6, 2009 at 4:52 PM, Allan Marcus wrote:
>
> Hi,
>
> I trying to convert a basic install of my puppetmasterd from WEBrick
> to Phusion. Here's what I did and here's what's not w
I may have answer my own question about the permissions. On my
production server I see the following, so I think I'm ok.
drwxr-x--- 2 _puppet _puppet 68 Jul 10 08:34 bucket
drwxr-x--- 2 root wheel 68 Jul 10 08:34 client_yaml
drwxr-x--- 2 root wheel 68 Jul 10 08:34 clien
So, are you using the same versions?
Rails: 2.0.5
Passenger: 2.2.2
Rack: 0.4.0
---
Thanks,
Allan Marcus
505-667-5666
On Aug 6, 2009, at 5:55 PM, Nigel Kersten wrote:
>
> Allan, when I got it running on OS X Server, I *only* installed
> Passenger from source, not from gem at all.
>
>
> On Th
Hi there,
I have a small isolated group of servers. I don't want to set up DNS
infrastructure for this.
I have an /etc/hosts file that looks like:
127.0.0.1 localhost.localdomain localhost
192.168.50.70 tec-puppet.tec.cwa.co.nztec-puppet
I can ping tec-puppet fine:
r...@tec
Steve Wray wrote:
> Hi there,
>
> I have a small isolated group of servers. I don't want to set up DNS
> infrastructure for this.
>
> I have an /etc/hosts file that looks like:
>
>
> 127.0.0.1 localhost.localdomain localhost
> 192.168.50.70 tec-puppet.tec.cwa.co.nztec-puppet
>
OH! I'm pretty new at this and I think I know the answer :-)
I don't think puppetd reads /etc/sysconfig/puppet (speaking redhat), I think
the /etc/init.d/puppet script is what really reads the confiig file.
Change hosts to:
192.168.50.70 tec-puppet.tec.cwa.co.nztec-puppet puppet
The "
cnjohnson wrote:
> I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
> 5.2. I have two nodes, one x86_64 and one ppc64, that have the client
> running and they are checking in regularly as expected. I have a
> minimal site.pp file which defines the owner, group and permissions
chakkerz wrote:
> Hello there
>
> I'm having a problem (again). At my site we are maintaining RHEL,
> CentOS and Solaris hosts, with in the future possibly some FreeBSD
> also being added into the mix. To this end instead of constantly
> branching whenever running a command on the console (or rem
David Schmitt wrote:
> chakkerz wrote:
>> Hello there
>>
>> I'm having a problem (again). At my site we are maintaining RHEL,
>> CentOS and Solaris hosts, with in the future possibly some FreeBSD
>> also being added into the mix. To this end instead of constantly
>> branching whenever running a co
29 matches
Mail list logo
