On Thu, Apr 1, 2010 at 7:07 PM, Daniel Pittman wrote:
> Charles Johnson writes:
>
>> Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
>> lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
>> RESOLVED about my discovery.
>
> Wow. Thanks so much for fin
Charles Johnson writes:
> Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
> lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
> RESOLVED about my discovery.
Wow. Thanks so much for finding that! That sort of silent failure can drive
someone mad, a
Daniel, I resolved the issue. One of my classes had duplicate 'ensure => '
lines. This was OK with 0.24.8, but 0.25.4 silently fails. I posted a
RESOLVED about my discovery.
I appreciate your help.
Cheers--
Charles
On Thu, Apr 1, 2010 at 2:38 AM, Daniel Pittman wrote:
> Charles Johnson write
Charles Johnson writes:
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman wrote:
>
>> [...]
>>
>> Your client logs *still* show that there is no MOTD stuff being touched at
>> all; try this on the client that should manage MOTD and see what is output:
>>
>> puppetd --test --debug 2>&1 | grep
Thanks! I will be trying that, or going back to 0.24.8 :)
On Wed, Mar 31, 2010 at 10:33 AM, Nigel Kersten wrote:
> On Wed, Mar 31, 2010 at 8:29 AM, Charles Johnson
> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten
> wrote:
> >>
> >> Which examples?
> >> I've always qualified
On Wed, Mar 31, 2010 at 8:29 AM, Charles Johnson wrote:
>
>
> On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten wrote:
>>
>> Which examples?
>> I've always qualified the full class name, in 0.24 and 0.25. I didn't
>> realize you could do what you've done above.
>>
>> It seems undesirable, ie:
>>
>>
On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten wrote:
> Which examples?
>
> I've always qualified the full class name, in 0.24 and 0.25. I didn't
> realize you could do what you've done above.
>
> It seems undesirable, ie:
>
> class foo {
> ...
> }
>
> class eggs {
> include foo
> }
>
> class
On Wed, Mar 31, 2010 at 7:41 AM, Charles Johnson wrote:
>
>
> On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten wrote:
>>
>> > /etc/puppet/modules/motd/manifests/init.pp looks like this
>> > class motd {
>> > include prodcomputenode
>> > include prodgateway
>>
>> shouldn't this be
>>
>> incl
On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten wrote:
>
> > /etc/puppet/modules/motd/manifests/init.pp looks like this
> > class motd {
> > include prodcomputenode
> > include prodgateway
>
> shouldn't this be
>
> include motd::prodgateway ?
>
> > include testcomputenode
> > inclu
On Wed, Mar 31, 2010 at 6:02 AM, Charles Johnson wrote:
>
>
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman wrote:
>>
>> [...]
>> Your client logs *still* show that there is no MOTD stuff being touched at
>> all; try this on the client that should manage MOTD and see what is
>> output:
>>
>>
On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman wrote:
> [...]
>
> Your client logs *still* show that there is no MOTD stuff being touched at
> all; try this on the client that should manage MOTD and see what is output:
>
>puppetd --test --debug 2>&1 | grep -i motd
>
> I suspect the answer wi
Charles Johnson writes:
> On Tue, Mar 30, 2010 at 7:58 PM, Daniel Pittman wrote:
>
>> > > import "modules" > import "templates" > import "nodes"
>>
>> Er, did you include the class that manages the MOTD file anywhere? Your
>> debug output says no, because nothing mentions motd at all...
[...]
On Tue, Mar 30, 2010 at 7:58 PM, Daniel Pittman wrote:
>
> >
> > import "modules"
> > import "templates"
> > import "nodes"
>
> Er, did you include the class that manages the MOTD file anywhere?
> Your debug output says no, because nothing mentions motd at all...
>
>
> No. This just works(tm), a
Charles Johnson writes:
> I have verified that if I add this to site.pp
[...]
> The file is indeed created as requested.
>
> The imports, however, do not seem to be effective:
>
> import "modules"
> import "templates"
> import "nodes"
Er, did you include the class that manages the MOTD file an
I have verified that if I add this to site.pp
file { "/tmp/test":
owner => "johns276",
group => "accre",
mode => 755,
ensure => present,
}
The file is indeed created as requested.
The imports, however, do not seem to be effective:
import "modules"
import "templates"
import "node
On Tue, Mar 30, 2010 at 3:23 PM, Asif Iqbal wrote:
> On Tue, Mar 30, 2010 at 3:50 PM, cnjohnson wrote:
> > Today has not been a good day! :)
> >
> > I made a small change in /modules/motd/files to see if it would be
> > propagated to 1 client (of ~850) I am testing with.
> >
> > Previously my pu
On Tue, Mar 30, 2010 at 3:50 PM, cnjohnson wrote:
> Today has not been a good day! :)
>
> I made a small change in /modules/motd/files to see if it would be
> propagated to 1 client (of ~850) I am testing with.
>
> Previously my puppetmasterd and clients were both at 0.24.8.
> Everything worked sw
Today has not been a good day! :)
I made a small change in /modules/motd/files to see if it would be
propagated to 1 client (of ~850) I am testing with.
Previously my puppetmasterd and clients were both at 0.24.8.
Everything worked swimmingly. Now, even though the
client and server "communicate"
On Tue, Mar 30, 2010 at 11:41 AM, Charles Johnson wrote:
> I apologize. I did read the stuff, and as soon as folk posted I hit myself!
hah. :) No apology necessary, I was just pointing it out as lots of
people are working from packaged puppet for their platform that
doesn't necessarily include th
I apologize. I did read the stuff, and as soon as folk posted I hit myself!
Sorry all.
Cheers--
Charles
On Tue, Mar 30, 2010 at 1:36 PM, Nigel Kersten wrote:
> It's worth reading the ext/rack stuff on how to set up passenger.
>
> You don't necessarily need to use the example manifests there to
It's worth reading the ext/rack stuff on how to set up passenger.
You don't necessarily need to use the example manifests there to set
up Passenger, but we should all be capable of reading puppet manifests
to work out what actually needs to be done.
http://github.com/reductivelabs/puppet/tree/0.2
I had the same error, i just changed the permissions of the config.ru file.
It has to be owned by the user puppet
2010/3/30 cnjohnson
> If I run puppetmasterd alone I can connect to an 0.24.x client.
> However, if I use passenger (2.2.11) and apache I get the following
> error in my apache error
Check the ownership on /etc/puppet/rack/config.ru. Should belong to
puppet. The UID/GID under which puppetmasterd will run is determined
by looking at config.ru
Hope this helps
On Tue, Mar 30, 2010 at 8:21 PM, cnjohnson wrote:
> If I run puppetmasterd alone I can connect to an 0.24.x client.
> H
If I run puppetmasterd alone I can connect to an 0.24.x client.
However, if I use passenger (2.2.11) and apache I get the following
error in my apache error_log:
Could not prepare for execution: Got 1 failure(s) while initializing:
change from absent to file failed: Could not set file on ensure:
P
24 matches
Mail list logo
