thr3ads.net - Puppet users - [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients [Mar 2010]

If this information is useful, please help other people find it:
Share via:

cnjohnson

2010-Mar-30 19:50 UTC

[Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

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" the motd on the client remains
stubbornly unchanged.

The only error message appears on the server:

(Module custom(/etc/puppet/modules/custom)) using the deprecated
''plugins'' directory for ruby extensions; please move to
''lib''

I''ll track that one down, but it shouldn''t prevent the rest of
the
modules from being executed on the client, should it? I am again at
a loss.

Again, any insights would be most welcome.

Cheers--

Charles

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Asif Iqbal

2010-Mar-30 20:23 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Tue, Mar 30, 2010 at 3:50 PM, cnjohnson <gm.johns276@gmail.com>
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 swimmingly. Now, even though the
> client and server "communicate" the motd on the client remains
> stubbornly unchanged.
>
> The only error message appears on the server:
>
> (Module custom(/etc/puppet/modules/custom)) using the deprecated
> ''plugins'' directory for ruby extensions; please move to
''lib''
>
> I''ll track that one down, but it shouldn''t prevent the
rest of the
> modules from being executed on the client, should it? I am again at
> a loss.
you probably want post some debug output to get more help.

Also I pull''d this
http://github.com/reductivelabs/puppet/tree/master/ext/rack
and used this to fix my passenger issue.

Is your puppetmasterd running as user puppet ?

>
> Again, any insights would be most welcome.
>
> Cheers--
>
> Charles
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-30 20:36 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Tue, Mar 30, 2010 at 3:23 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> On Tue, Mar 30, 2010 at 3:50 PM, cnjohnson <gm.johns276@gmail.com>
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 swimmingly. Now, even though the
> > client and server "communicate" the motd on the client
remains
> > stubbornly unchanged.
> >
> > The only error message appears on the server:
> >
> > (Module custom(/etc/puppet/modules/custom)) using the deprecated
> > ''plugins'' directory for ruby extensions; please move
to ''lib''
> >
> > I''ll track that one down, but it shouldn''t prevent
the rest of the
> > modules from being executed on the client, should it? I am again at
> > a loss.
>
> you probably want post some debug output to get more help.
>
> Also I pull''d this
> http://github.com/reductivelabs/puppet/tree/master/ext/rack
> and used this to fix my passenger issue.
>
> Is your puppetmasterd running as user puppet ?
>
>
> >
> > Again, any insights would be most welcome.
> >
> > Cheers--
> >
> > Charles
> >
> > --
> > 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@googlegroups.com.
> > To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> > For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
> >
> >
>
> Yes, puppetmasterd is running as puppet. As far as I can tell, apache,passenger and puppet all seem to be running fine. I get no error messages of
any kind. I''ll try running puppetd --debug on the client to see what I
get.... and I get this:

/usr/bin/ruby /usr/local/bin/puppetd --debug --no-daemon
debug: Creating default schedules
debug: Failed to load library ''shadow'' for feature
''libshadow''
debug: Failed to load library ''ldap'' for feature
''ldap''
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/etc/puppet/ssl]:
Autorequiring File[/etc/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/private]:
Autorequiring File[/etc/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/puppet/log]:
Autorequiring File[/var/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/csr_vmps01.vampire.pem]:
Autorequiring File[/etc/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs/ca.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs/vmps01.vampire.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/puppet/state/classes.txt]:
Autorequiring File[/var/puppet/state]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/var/puppet/state/state.yaml]:
Autorequiring File[/var/puppet/state]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[puppetd]/File[/etc/puppet/puppet.conf]:
Autorequiring File[/etc/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/puppet/lib]:
Autorequiring File[/var/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/puppet/run]:
Autorequiring File[/var/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/private_keys]:
Autorequiring File[/etc/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/public_keys]:
Autorequiring File[/etc/puppet/ssl]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/puppet/state]:
Autorequiring File[/var/puppet]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/private_keys/vmps01.vampire.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/public_keys/vmps01.vampire.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug:
/Settings[/etc/puppet/puppet.conf]/Settings[ssl]/File[/etc/puppet/ssl/certs]:
Autorequiring File[/etc/puppet/ssl]
debug: Finishing transaction 23587145743860 with 0 changes
notice: Starting Puppet client version 0.24.8
debug: Loaded state in 0.00 seconds
debug: Puppet::Network::Client::File: defining fileserver.describe
debug: Puppet::Network::Client::File: defining fileserver.list
debug: Puppet::Network::Client::File: defining fileserver.retrieve
info: Retrieving plugins
debug: Calling fileserver.list
debug: /File[/var/puppet/lib]/checksum: Initializing checksum hash
debug: /File[/var/puppet/lib]: Creating checksum {mtime}Thu Aug 20 14:00:01
-0500 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/puppet/lib/facter]/checksum: Initializing checksum hash
debug: /File[/var/puppet/lib/facter]: Creating checksum {mtime}Fri Sep 04
11:57:31 -0500 2009
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/puppet/lib/facter/myrinet.rb]/checksum: Initializing
checksum hash
debug: /File[/var/puppet/lib/facter/myrinet.rb]: Creating checksum
{md5}0b1457fbf1c76498428fd6ae9bf3462b
debug: Calling fileserver.describe
debug: Calling fileserver.list
debug: /File[/var/puppet/lib/facter/powerprocessorcount.rb]/checksum:
Initializing checksum hash
debug: /File[/var/puppet/lib/facter/powerprocessorcount.rb]: Creating
checksum {md5}428d7663347637bbcfedc1395069b71a
debug: Calling fileserver.describe
debug: Finishing transaction 23587145750900 with 0 changes
debug: Retrieved facts in 1.32 seconds
debug: Retrieving catalog
debug: Calling puppetmaster.getconfig
debug: Retrieved catalog in 0.16 seconds
info: No classes to store
debug: Creating default schedules
debug: Finishing transaction 23456251632420 with 0 changes
info: Caching catalog at /var/puppet/state/localconfig.yaml
notice: Starting catalog run
debug: Loaded state in 0.08 seconds
debug: Finishing transaction 23456253520060 with 0 changes
debug: Storing state
debug: Stored state in 0.03 seconds
notice: Finished catalog run in 0.13 seconds

I am intrigued  by the "info: No classes to store" It is almost as if
the
server doesn''t recognize the imports of the site.pp.

Cheers--

Charles

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-30 20:47 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

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 "nodes"

I have changed *nothing* except the server moving from 0.24.8 to 0.25.4. Do
I have to delete all the puppet directories on all the clients? (Ugh!)

Mystified.

Cheers--

~Charles~

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Daniel Pittman

2010-Mar-31 00:58 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Charles Johnson <gm.johns276@gmail.com> 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 anywhere?
Your debug output says no, because nothing mentions motd at all...

The way to use modules is, roughly:

manifests/nodes.pp:
node "example.com" { include motd }

modules/motd/manifests/init.pp:
class motd {
    file { "/etc/motd": content => "You ran my example?"
}
}

The ''include'' part is the key; modules don''t just do
things without being
asked.
> I have changed *nothing* except the server moving from 0.24.8 to 0.25.4. Do
> I have to delete all the puppet directories on all the clients? (Ugh!)
No.  This just works(tm), aside from the need to change the file paths to
reflect the new "files in modules" path vs the old "files in
modules" path.

        Daniel

At least, not on my 50-odd nodes it didn''t.
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-31 01:57 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Tue, Mar 30, 2010 at 7:58 PM, Daniel Pittman <daniel@rimspace.net>
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), aside from the need to change the file paths to
> reflect the new "files in modules" path vs the old "files in
modules" path.
>
>        Daniel
>
> At least, not on my 50-odd nodes it didn''t.
> --
> ✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155
> 707
>               ♽ made with 100 percent post-consumer electrons
>
> --
>
> Yes, there is a complete class that manages MOTD. Here is site.pp:
# site.pp

import "modules"
import "templates"
import "nodes"

file { "/etc/passwd":
    owner => "root",
    group => "root",
    mode => 644,
}

file { "/tmp/test":
    owner => "johns276",
    group => "accre",
    mode => 755,
    ensure => present,
}

Here is modules:

import "sudo"
import "motd"
import "group"
import "envvars"
import "rclocal"
import "selinux"
import "hosts"
import "rhosts"
import "autofs"
import "ntp"
import "torque"
import "nrpe"
import "yum"
import "nagios-plugins"
import "puppetconf"
import "static"
import "syslog"
import "epilogue"

and there is an init.pp in modules/motd/manifests/ which includes the class
needed to supply motd to the appropriate nodes. The motd files are in
motd/files/

Like I said, all I have done is change the server from 0.24 to 0.25. File
locations on both server and clients is unchanged. So, I have done
something, but I am not sure what.

Cheers--

Charles

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Daniel Pittman

2010-Mar-31 02:46 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Charles Johnson <gm.johns276@gmail.com> writes:> On Tue, Mar 30, 2010 at 7:58 PM, Daniel Pittman <daniel@rimspace.net>
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...
[...]
> Yes, there is a complete class that manages MOTD. Here is site.pp:
That doesn''t show anything *including* the class that MOTD is managed
from,
but I take your word for it that you actually do that.  (I can see you
*import* it, which is somewhat different. :)

[...]
> Like I said, all I have done is change the server from 0.24 to 0.25. File
> locations on both server and clients is unchanged. So, I have done
> something, but I am not sure what.
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 will be "nothing is output".

If you post those results, and the content of your MOTD class (or a pointer to
your entire set of manifests) we should be better able to help narrow this
down...

        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-31 13:02 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman <daniel@rimspace.net>
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 will be "nothing is output".
>
> If you post those results, and the content of your MOTD class (or a pointer
> to
> your entire set of manifests) we should be better able to help narrow this
> down...
>
>I do appreciate your help.

OK, right, nothing is output on the client from puppetd --test --debug
2>&1
| grep -i motd

/etc/puppet/manifests/site.pp contains this at the top line:  import
"modules"
/etc/puppet/manifests/modules.pp contains this line at the top: import
"motd"
/etc/puppet/modules/motd/manifests/init.pp looks like this

class motd {

    include prodcomputenode
    include prodgateway
    include testcomputenode
    include testgateway
}

/etc/puppet/modules/motd/manifests/prodgateway looks like this

class motd::prodgateway {

    file { "/etc/motd":
        owner   => "root",
        group   => "root",
        mode    => 644,
        source => $architecture ? {
            x86_64  => "puppet:///motd/motd_x86prodgw",
            default => "puppet:///motd/motd_x86prodgw",
        },
    }
}

and, of course /etc/puppet/modules/motd/files contains the file
motd_x86prodgw which has the message of the day.

On the client facter returns --among other things-- architecture => x86_64

/etc/puppet/fileserver.conf contains these lines:

[motd]
path /etc/puppet/modules/motd/files
allow *.vampire

On the server puppetca --list --all returns

+ vmps07.vampire

which is my test client and is defined as a gateway box in the
/etc/puppet/manifests/nodes.pp file: node ''vmps07.vampire''
inherits
x86prodgateway {}

x86prodgateway is defined in  /etc/puppet/manifests/templates.pp

node x86prodgateway inherits basenode {
include motd::prodgateway
include rclocal::prodgateway
include rhosts::prodcluster
include hosts::prodhosts
include torque::prodcluster
include syslog
 file { "/usr/lib64/libg2c.so":
ensure => link,
                target => "/usr/lib64/libg2c.so.0.0.0",
}
 file { "/usr/lib64/libgfortran.so":
ensure => link,
                target => "/usr/lib64/libgfortran.so.1.0.0",
}
}

basenode is defined like so:

node basenode {
  include sudo
  include envvars
  include selinux
  include autofs
  include ntp
  include puppetconf
  include static
  include torque::common
  include bash
}

node default inherits basenode {}

Thanks again.

Cheers--

Charles

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2010-Mar-31 14:16 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Wed, Mar 31, 2010 at 6:02 AM, Charles Johnson <gm.johns276@gmail.com>
wrote:>
>
> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman <daniel@rimspace.net>
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 will be "nothing is output".
>>
>> If you post those results, and the content of your MOTD class (or a
>> pointer to
>> your entire set of manifests) we should be better able to help narrow
this
>> down...
>>
>
> I do appreciate your help.
>
> OK, right, nothing is output on the client from puppetd --test --debug
2>&1
> | grep -i motd
> /etc/puppet/manifests/site.pp contains this at the top line:  import
> "modules"
> /etc/puppet/manifests/modules.pp contains this line at the top: import
> "motd"
> /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
>     include testgateway
> }
> /etc/puppet/modules/motd/manifests/prodgateway looks like this
> class motd::prodgateway {
>     file { "/etc/motd":
>         owner   => "root",
>         group   => "root",
>         mode    => 644,
>         source => $architecture ? {
>             x86_64  => "puppet:///motd/motd_x86prodgw",
>             default => "puppet:///motd/motd_x86prodgw",
>         },
>     }
> }
> and, of course /etc/puppet/modules/motd/files contains the file
> motd_x86prodgw which has the message of the day.
> On the client facter returns --among other things-- architecture =>
x86_64
> /etc/puppet/fileserver.conf contains these lines:
> [motd]
> path /etc/puppet/modules/motd/files
> allow *.vampire
> On the server puppetca --list --all returns
> + vmps07.vampire
> which is my test client and is defined as a gateway box in the
> /etc/puppet/manifests/nodes.pp file: node
''vmps07.vampire'' inherits
> x86prodgateway {}
> x86prodgateway is defined in  /etc/puppet/manifests/templates.pp
> node x86prodgateway inherits basenode {
> include motd::prodgateway
> include rclocal::prodgateway
> include rhosts::prodcluster
> include hosts::prodhosts
> include torque::prodcluster
> include syslog
> file { "/usr/lib64/libg2c.so":
> ensure => link,
>                 target => "/usr/lib64/libg2c.so.0.0.0",
> }
> file { "/usr/lib64/libgfortran.so":
> ensure => link,
>                 target => "/usr/lib64/libgfortran.so.1.0.0",
> }
> }
> basenode is defined like so:
> node basenode {
>   include sudo
>   include envvars
>   include selinux
>   include autofs
>   include ntp
>   include puppetconf
>   include static
>   include torque::common
>   include bash
> }
> node default inherits basenode {}
> Thanks again.
> Cheers--
> Charles
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>


-- 
nigel

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-31 14:41 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten <nigelk@google.com> 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
> >     include testgateway
> > }
> > /etc/puppet/modules/motd/manifests/prodgateway looks like this
> > class motd::prodgateway {
> >     file { "/etc/motd":
> >         owner   => "root",
> >         group   => "root",
> >         mode    => 644,
> >         source => $architecture ? {
> >             x86_64  => "puppet:///motd/motd_x86prodgw",
> >             default => "puppet:///motd/motd_x86prodgw",
> >         },
> >     }
> > }
>
I wouldn''t have thought so, since this worked perfectly fine in 0.24.8
and
is taken from examples at reductivelabs.

Cheers--

Charles

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2010-Mar-31 15:02 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Wed, Mar 31, 2010 at 7:41 AM, Charles Johnson <gm.johns276@gmail.com>
wrote:>
>
> On Wed, Mar 31, 2010 at 9:16 AM, Nigel Kersten <nigelk@google.com>
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
>> >     include testgateway
>> > }
>> > /etc/puppet/modules/motd/manifests/prodgateway looks like this
>> > class motd::prodgateway {
>> >     file { "/etc/motd":
>> >         owner   => "root",
>> >         group   => "root",
>> >         mode    => 644,
>> >         source => $architecture ? {
>> >             x86_64  =>
"puppet:///motd/motd_x86prodgw",
>> >             default =>
"puppet:///motd/motd_x86prodgw",
>> >         },
>> >     }
>> > }
>
> I wouldn''t have thought so, since this worked perfectly fine in
0.24.8 and
> is taken from examples at reductivelabs.
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 eggs::foo {
...
}


> Cheers--
> Charles
>
>
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>


-- 
nigel

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-31 15:29 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten <nigelk@google.com> 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 eggs::foo {
> ...
> }
>
> Thank you, Nigel, for your patience!
I can try changing that, but it still does not explain why all the other
modules --there are dozens-- most of which are quite simple and do not have
this involved syntax are not run on the client.

There is something very simple, like a missing path or some such. I have run
puppetmasterd --debug --no-daemon and on the client puppetd --debug --test

I would be willing to post output if it might help.

~Charles~

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2010-Mar-31 15:33 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Wed, Mar 31, 2010 at 8:29 AM, Charles Johnson <gm.johns276@gmail.com>
wrote:>
>
> On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten <nigelk@google.com>
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 eggs::foo {
>> ...
>> }
>>
> Thank you, Nigel, for your patience!
> I can try changing that, but it still does not explain why all the other
> modules --there are dozens-- most of which are quite simple and do not have
> this involved syntax are not run on the client.
> There is something very simple, like a missing path or some such. I have
run
> puppetmasterd --debug --no-daemon and on the client puppetd --debug --test
> I would be willing to post output if it might help.
Not that I''m volunteering right now as I have a bunch of reports to
write :) but this sounds like IRC might be a better vehicle for
debugging? There are usually a couple of people around with some spare
cycles to help.

#puppet on freenode.

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Mar-31 15:53 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Thanks! I will be trying that, or going back to 0.24.8 :)

On Wed, Mar 31, 2010 at 10:33 AM, Nigel Kersten <nigelk@google.com> wrote:
> On Wed, Mar 31, 2010 at 8:29 AM, Charles Johnson
<gm.johns276@gmail.com>
> wrote:
> >
> >
> > On Wed, Mar 31, 2010 at 10:02 AM, Nigel Kersten
<nigelk@google.com>
> 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 eggs::foo {
> >> ...
> >> }
> >>
> > Thank you, Nigel, for your patience!
> > I can try changing that, but it still does not explain why all the
other
> > modules --there are dozens-- most of which are quite simple and do not
> have
> > this involved syntax are not run on the client.
> > There is something very simple, like a missing path or some such. I
have
> run
> > puppetmasterd --debug --no-daemon and on the client puppetd --debug
> --test
> > I would be willing to post output if it might help.
>
> Not that I''m volunteering right now as I have a bunch of reports
to
> write :) but this sounds like IRC might be a better vehicle for
> debugging? There are usually a couple of people around with some spare
> cycles to help.
>
> #puppet on freenode.
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Daniel Pittman

2010-Apr-01 07:38 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Charles Johnson <gm.johns276@gmail.com> writes:> On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman <daniel@rimspace.net>
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 will be "nothing is output".
>> 
>> If you post those results, and the content of your MOTD class (or a
pointer
>> to your entire set of manifests) we should be better able to help
narrow
>> this down...
>> 
>
> I do appreciate your help.
>  
> OK, right, nothing is output on the client from puppetd --test --debug
2>&1 | grep -i
> motd
>
> /etc/puppet/manifests/site.pp contains this at the top line:  import
"modules"
> /etc/puppet/manifests/modules.pp contains this line at the top: import
"motd"
> /etc/puppet/modules/motd/manifests/init.pp looks like this
Darn.  I don''t know. :(  It all looks right to me.  At this point I
would be
reduced to guessing, or tracing through the code.  Sorry.

        Daniel

-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Charles Johnson

2010-Apr-01 14:27 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

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 <daniel@rimspace.net>
wrote:
> Charles Johnson <gm.johns276@gmail.com> writes:
> > On Tue, Mar 30, 2010 at 9:46 PM, Daniel Pittman
<daniel@rimspace.net>
> 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 will be "nothing is output".
> >>
> >> If you post those results, and the content of your MOTD class (or
a
> pointer
> >> to your entire set of manifests) we should be better able to help
narrow
> >> this down...
> >>
> >
> > I do appreciate your help.
> >
> > OK, right, nothing is output on the client from puppetd --test --debug
> 2>&1 | grep -i
> > motd
> >
> > /etc/puppet/manifests/site.pp contains this at the top line:  import
> "modules"
> > /etc/puppet/manifests/modules.pp contains this line at the top: import
> "motd"
> > /etc/puppet/modules/motd/manifests/init.pp looks like this
>
> Darn.  I don''t know. :(  It all looks right to me.  At this point
I would
> be
> reduced to guessing, or tracing through the code.  Sorry.
>
>        Daniel
>
> --
> ✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155
> 707
>               ♽ made with 100 percent post-consumer electrons
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Daniel Pittman

2010-Apr-02 02:07 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Charles Johnson <gm.johns276@gmail.com> 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, and now I know to go looking if I run into the same sort of
thing.
> I appreciate your help.
No worries. :)
        Daniel

-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Nigel Kersten

2010-Apr-02 02:11 UTC

head link

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

On Thu, Apr 1, 2010 at 7:07 PM, Daniel Pittman <daniel@rimspace.net>
wrote:> Charles Johnson <gm.johns276@gmail.com> 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, and now I know to go looking if I run into the same sort of
> thing.
You should bug report this.

Does --parseonly pick up this error?


>
>> I appreciate your help.
>
> No worries. :)
>        Daniel
>
> --
> ✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155
707
>               ♽ made with 100 percent post-consumer electrons
>
> --
> 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@googlegroups.com.
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
nigel

-- 
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@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Puppet users - Mar 2010 - puppet 0.25.4 & passenger with 0.24.8 clients

[Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients

Re: [Puppet Users] puppet 0.25.4 & passenger with 0.24.8 clients