[Puppet Users] Need a second set of eyes... cannot find a class..

2011-11-12 Thread Peter Berghold
In one of my modules I have the following :

postfix/
   manifests/
  conf.pp
  conf/access-all.pp
(as well as the obligatory init.pp and a few others)

and the access-all.pp file contains:

class postfix::conf::access-all inherits postfix::conf {
$hosts = $all_hosts
$domains = $all_domains
$ips = $all_ips

@file {
postfix-access-file:
path => "/etc/postfix/access",
owner => root, group => root, mode => 0644,
content => template("postfix/templates/access.erb"),
notify => Exec[ hash-access]
}
exec {
hash-access:
path=>"/usr/bin:/usr/sbin:/usr/local/bin:/bin:/sbin",
cwd => "/etc/postfix",
command => "postmap access"
}
realize File[postfix-access-file]

}


and yet when I run puppetd on my configured host:

err: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find class postfix::conf::access-all for
chicweb0.chi.sharkrivertech.com at
/etc/puppet/manifests/nodes/chicweb0.pp:2 on node
chicweb0.chi.sharkrivertech.com

Can anybody spot anything I'm fat fingering?


-- 
Peter L. Berghold
Owner, Shark River Technical Solutions LLC

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



Re: [Puppet Users] Incorrect "architecture" fact value during catalog run

2011-11-12 Thread Adrien Thebo
Could you get the versions of facter in
/usr/lib/ruby/vendor_ruby/facter.rb and
/usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they differ?

On Fri, Nov 11, 2011 at 11:01 PM, Alexander Azarov  wrote:
> No problems, I've isolated the part of manifest that depends on
> "architecture", so everything works through a hack right now.
>
> # find / -name architecture.rb
> /usr/lib/ruby/vendor_ruby/facter/architecture.rb
> /var/lib/vservers/worker/usr/lib/ruby/1.8/facter/architecture.rb
> /var/lib/vservers/mongo/usr/lib/ruby/1.8/facter/architecture.rb
>
>
> On Friday, November 11, 2011 11:07:42 PM UTC+4, Adrien Thebo wrote:
>>
>> Sorry for the slow response on this, it's been a chaotic few days. I'm
>> still very baffled by this. Could you do something like `find / -name
>> 'architecture.rb'` to see if there's any way there could be another
>> fact definition for this? Although at this point I'm starting to
>> suspect bogons.
>>
>> On Fri, Nov 4, 2011 at 1:53 PM, Alexander Azarov  wrote:
>> > Yes, I had an idea I have different versions and simply searched the
>> > system
>> > for different RubyGems installations.. for no result. I have the only
>> > one.
>> >
>> > Here it is the output you requested:
>> >
>> > r3:/var/log# facter --puppet | grep '\(archit\|facterv\|operatings\)'
>> > architecture => amd64
>> > facterversion => 1.6.2
>> > operatingsystem => Debian
>> > operatingsystemrelease => 6.0.3
>> >
>> >
>> >
>> > r3:/var/log# facter | grep '\(archit\|facterv\|operatings\)'
>> > architecture => amd64
>> > facterversion => 1.6.2
>> > operatingsystem => Debian
>> > operatingsystemrelease => 6.0.3
>> >
>> >
>> > r3:/var/log# puppet agent --test
>> > ...
>> > notice: operatingsystem: Debian facterversion: 1.6.2 architecture:
>> > x86_64
>> > notice: /Stage[main]/Nginx/Notify[operatingsystem: Debian facterversion:
>> > 1.6.2 architecture: x86_64]/message: defined 'message' as
>> > 'operatingsystem:
>> > Debian facterversion: 1.6.2 architecture: x86_64'
>> >
>> >
>> > On Friday, November 4, 2011 11:34:19 PM UTC+4, Adrien Thebo wrote:
>> >>
>> >> Okay, that's seriously weird. The only thing that comes to mind is
>> >> that running facter on the command line is using one version of
>> >> facter, and puppet's using another. Could you post the output of
>> >> facter and puppet with the architecture, operatingsystem, and
>> >> facterversion facts?
>> >>
>> >> On Thu, Nov 3, 2011 at 10:25 PM, Alexander Azarov 
>> >> wrote:
>> >> >
>> >> >
>> >> > On Thursday, November 3, 2011 8:27:01 PM UTC+4, Adrien Thebo wrote:
>> >> >>
>> >> >> Could you post the operatingsystem fact alongside the architecture
>> >> >> fact for facter by itself, and then the facts as presented by
>> >> >> puppet?
>> >> >
>> >> > r3:/var/log# facter | grep -e '\(operatingsys\|architec\)'
>> >> > architecture => amd64
>> >> > operatingsystem => Debian
>> >> > operatingsystemrelease => 6.0.3
>> >> >
>> >> > r3:/var/log# puppet agent --test
>> >> > 
>> >> > notice: operatingsystem='Debian' architecture='x86_64'
>> >> > notice: /Stage[main]/Nginx/Notify[operatingsystem='Debian'
>> >> > architecture='x86_64']/message: defined 'message' as
>> >> > 'operatingsystem='Debian' architecture='x86_64''
>> >> >
>> >> >
>> >> >>
>> >> >> On Mon, Oct 31, 2011 at 11:33 AM, Alexander Azarov
>> >> >> 
>> >> >> wrote:
>> >> >> > The simplest default, that is WEBrick I guess.
>> >> >> >
>> >> >> > On Monday, October 31, 2011 10:28:12 PM UTC+4, Adrien Thebo wrote:
>> >> >> >>
>> >> >> >> Just as a curiosity, what web server are you using for your
>> >> >> >> puppet
>> >> >> >> master?
>> >> >> >>
>> >> >> >> On Mon, Oct 31, 2011 at 10:55 AM, Alexander Azarov
>> >> >> >> 
>> >> >> >> wrote:
>> >> >> >> > This is Debian 6.0.3
>> >> >> >> >
>> >> >> >> > On Monday, October 31, 2011 8:43:50 PM UTC+4, Adrien Thebo
>> >> >> >> > wrote:
>> >> >> >> >>
>> >> >> >> >> What operating system is this? I'm looking at the
>> >> >> >> >> documentation
>> >> >> >> >> for
>> >> >> >> >> the architecture fact, and theres this:
>> >> >> >> >>
>> >> >> >> >> # Resolution:
>> >> >> >> >> #   On OpenBSD, Linux and Debian's kfreebsd, use the
>> >> >> >> >> hardwaremodel
>> >> >> >> >> fact.
>> >> >> >> >> #   Gentoo and Debian call "x86_86" "amd64".
>> >> >> >> >> #   Gentoo also calls "i386" "x86".
>> >> >> >> >>
>> >> >> >> >> On Mon, Oct 31, 2011 at 9:25 AM, Alexander Azarov
>> >> >> >> >> 
>> >> >> >> >> wrote:
>> >> >> >> >> > Hi all,
>> >> >> >> >> >
>> >> >> >> >> > Can you help me diagnose a problem please?
>> >> >> >> >> >
>> >> >> >> >> > I have Facter 1.6.2 and Puppet 2.7.6 installed and what
>> >> >> >> >> > happens
>> >> >> >> >> > is
>> >> >> >> >> > that
>> >> >> >> >> > I
>> >> >> >> >> > rely on "architecture" fact in my manifests and this fact
>> >> >> >> >> > looks
>> >> >> >> >> > correct
>> >> >> >> >> > when
>> >> >> >> >> > I run Facter and it is set to incorrect value during catalog
>> >> >> >> >> > run:
>> >> >> >> >> >
>> >> >> >> >> > r4:/var/log# facter 

Re: [Puppet Users] Incorrect "architecture" fact value during catalog run

2011-11-12 Thread R.I.Pienaar


- Original Message -
> Could you get the versions of facter in
> /usr/lib/ruby/vendor_ruby/facter.rb and
> /usr/lib/vservers/*/usr/lib/ruby/1.8/facter.rb and see if they
> differ?


Not been following this thread but this kind of wrong facts was
previously observed under heavily loaded webrick based installs.

What web server are you using?

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