[Puppet Users] Re: Planet Puppet is born!

On 31/07/09 23:55, Larry Ludwig wrote:
> Thanks Brice! I
> 
> Did you add the Reductive Labs corporate feeds?

I just did it 
For the other people, I'm reluctant to add their feeds without their 
prior consent.

And I still need someone who masterize CSSfu to skin it. If you're this 
kind of people, please speak-up!

Thanks,
--

-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Puppet Users] SysV rc scripts vs. runit

Hi,

I'm looking at writing some template/classes that run services under
runit, rather then with SysV rc scripts (ie. in /etc/init.d).

It seems pretty straight-forward, but I'm running into an issue trying
to ensure that the service is up and started from the runit service but
not from the rc service.

Let me use an example...

The CentOS apache package is named "httpd" and normally installs a
script named "httpd" to /etc/init.d that is used to manage the service.
This script is symlinked into various /etc/rcn.d/ directories by the
chkconfig mechanism.

runit uses run scripts in /etc/sv/{service name}/ to manage the services.

So, I want to ensure that the rc service is stopped, and configured not
to start on boot, and that the runit service is started & configured to
start on boot.

First problem: it's not possible to have two services with the same
name. ie. given the following service to manage the rc service:

        service { "httpd":
                enable     => "false",
                ensure     => "stopped",
                hasrestart => "true",

[Puppet Users] Invalid parameter provider error on debian

Hi all,
  I am suddenly getting an "Invalid parameter provider" when puppet
runs on a debian box that has been working fine.    puppetd output is:

info: Retrieving plugins
err: /File[/var/lib/puppet/lib]: Failed to generate additional
resources during transaction: None of the provided sources exist
err: /File[/var/lib/puppet/lib]: Failed to retrieve current state of
resource: No specified source was found from puppet://puppet.simupt.com/plugins
err: Could not create sbcadmin: Invalid parameter provider
err: Could not create sbcweb: Invalid parameter provider
warning: Could not load cached catalog: Invalid parameter provider
warning: Configuration could not be instantiated: Invalid parameter
provider

  I'm running Debian Lenny using backports for puppet.

$ dpkg -l puppet
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-
installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name
Version                           Description
+++-=================================-
=================================-
==================================================================================
ii  puppet

[Puppet Users] Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection reset by peer>

Hello there

I'm having this error:
Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection
reset by peer>

From what i can tell, eventually the master decides it has had enough
and freezes. I've got about 25 hosts checking in to it, but restarting
the master daemon appears to be only a partial solution with the
clients occasionally not being able to then re-connect...

I'm running a puppet daemon on the clients, rather than through cron.

Also, i gather this might be an issue with ruby? Google doesn't seem
to find anything in this group, but mirrored mailing lists??? (i'm
rather confused at this point).

I'm mostly concerned about Red Hat issues, Solaris craters as well,
but i only have one Solaris node, so it's a lesser evil.

Master and clients in question are RHEL 5.3, and packages are from
RHEL and EPEL. Version's are:
[root <at> tangelo cron.d]# rpm -qa | grep puppet
puppet-server-0.24.8-1.el5.1
puppet-0.24.8-1.el5.1
[root <at> tangelo cron.d]# rpm -q ruby
ruby-1.8.5-5.el5_3.7
[root <at> tangelo cron.d]# rpm -q facter
facter-1.5.5-1.el5

[Puppet Users] Re: Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection reset by peer>

[Puppet Users] Re: Could not call fileserver.describe: #<Errno:: ECONNRESET: Connection reset by peer>

Good Call, i've switched to mongrel, we'll see how that goes.

Cheers
chakkerz

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Puppet Users] Re: Augeas and grub.conf

Chad Huneycutt wrote:
> +1 for that.  I did the same thing last week.  I ended up editing the
> grub.conf lens.  If there is a way to override the 'incl' directives
> or point augeas at a specific file and tell it to use a specific lens,
> I'd like to hear it as well.

You can use the load_path property to point to a different set of lenses 
from the default. This maps to the LOADPATH parameter on augeas open 
[1]. If you have issues with this, please let me know.

-- bk

[1] http://www.augeas.net/docs/api.html

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Puppet Users] Re: Augeas and grub.conf

Trevor Hemsley wrote:
> Having just spent about 2 hours trying to work out how to add a
> 
> password --md5 $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1
> 
> line to my grub.conf I thought it would be worth sharing how I finally
> got it to work.
> 
>         augeas {"/boot/grub/grub.conf":
>                 context => "/files/boot/grub/grub.conf",
>                 changes => [ "set timeout 15",
>                                 'set password/md5 null',
>                                 'set password
> $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1'
>                         ]
>                 }
> 
> Also the grub lens only works if /boot/grub/grub.conf resides on the
> same file system as /etc otherwise augtool craps out with an error about
> being unable to save a cross file system link. Short of editing the lens
> file, I'm not sure how to solve that one. If anyone knows how to fix
> that without the edit then that would be great :)
> 
Can you post this over on the augeas list[1]? Thanks!

[1] http://www.augeas.net/developers.html

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Puppet Users] Re: Augeas and grub.conf

Well, I just dropped the lenses in /usr/share/augeas/lenses, which I
assume is on the load path higher than /usr/share/augeas/lenses/dist,
where all of the other lenses are.  But should I have to do that?
Maybe we can pick up the discussion on the augeas list.

- Chad

On Mon, Aug 3, 2009 at 8:57 AM, Bryan Kearney<bkearney <at> redhat.com> wrote:
>
> Chad Huneycutt wrote:
>> +1 for that.  I did the same thing last week.  I ended up editing the
>> grub.conf lens.  If there is a way to override the 'incl' directives
>> or point augeas at a specific file and tell it to use a specific lens,
>> I'd like to hear it as well.
>
> You can use the load_path property to point to a different set of lenses
> from the default. This maps to the LOADPATH parameter on augeas open
> [1]. If you have issues with this, please let me know.
>
> -- bk
>
>
> [1] http://www.augeas.net/docs/api.html
>
> >
>

--

-- 
Chad M. Huneycutt

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Puppet Users] Re: Augeas and grub.conf

There was a bug in the previous incarnation anyway.

        augeas {"/boot/grub/grub.conf":
                context => "/files/boot/grub/grub.conf",
                changes => [ "set timeout 15",
                                'rm password',
                                'ins password after timeout',
                                'set password/md5 null',
                                'set password
$1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1'
                        ]
                }

It seems that grub helpfully ignores the password line if it appears
after the image lines :(

Bryan Kearney wrote:
> Trevor Hemsley wrote:
>   
>> Having just spent about 2 hours trying to work out how to add a
>>
>> password --md5 $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1
>>
>> line to my grub.conf I thought it would be worth sharing how I finally
>> got it to work.
>>
>>         augeas {"/boot/grub/grub.conf":
>>                 context => "/files/boot/grub/grub.conf",
>>                 changes => [ "set timeout 15",
>>                                 'set password/md5 null',
>>                                 'set password
>> $1$Qejy8/$.qFUuDeYL.cuSDpN1ZD.S1'
>>                         ]
>>                 }
>>
>> Also the grub lens only works if /boot/grub/grub.conf resides on the
>> same file system as /etc otherwise augtool craps out with an error about
>> being unable to save a cross file system link. Short of editing the lens
>> file, I'm not sure how to solve that one. If anyone knows how to fix
>> that without the edit then that would be great :)
>>
>>     
> Can you post this over on the augeas list[1]? Thanks!
>   
Done

-- 

Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* Brighton, UK   

OFFICE 	+44 (0) 1273 666 350
FAX 	+44 (0) 1273 666 351

.................................................
www.calypso.com

This electronic-mail might contain confidential information intended
only for the use by the entity named. If the reader of this message is
not the intended recipient, the reader is hereby notified that any
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users <at> googlegroups.com
To unsubscribe from this group, send email to puppet-users+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---