john.pyeatt@singlewire.com
2013-Dec-06 19:12 UTC
[Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet master --configprint modulepath and I in fact see /etc/puppet/modules:/opt/our-repo/puppetmaster/modules But when I restart puppetmasterd I get the following errors. 2013-12-06 19:05:09 +0000 Puppet (err): Could not find class newapp for ip-10-0-22-5 on node ip-10-0-22-5 On the clients I get the message Puppet (err): Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class newapp for ip-10-0-22-5 on node ip-10-0-22-5 If I move my newapp module to /etc/puppet/modules it works fine. So I think the module itself isn''t the problem. I''ve also tried moving the modulepath= to the [master] stanza but things still don''t work. *Can anyone tell me the incantation I need to make puppetmasterd recognize my /opt/our-repo/puppetmaster/modules directory*? Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/f59f9ac3-ff1b-4411-92a4-59aacb685522%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-10 13:02 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Hi, the approach looks fine. Can you share the complete path to the newapp class when it''s not working? Beware that the puppet master process drops its privileges after basic initialization. You may have to make sure that the puppet user (or whichever is being used) can access your alternate modules tree. HTH, Felix On 12/06/2013 08:12 PM, john.pyeatt@singlewire.com wrote:> > _Can anyone tell me the incantation I need to make puppetmasterd > recognize my /opt/our-repo/puppetmaster/modules directory_?-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A710DB.2060500%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-10 15:08 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
My puppetmaster is running as the user puppet. I logged into the system as puppet and was able to access the directory /opt/our-repo/puppetmaster/modules. I did a chown -R puppet:puppet /opt/our-repo/puppetmaster just to make certain and it still is unrecognised. Just get the message in the puppet client log. 2013-12-10 14:57:51 +0000 Puppet (err): Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class ec2metadata for ip-10-0-22-220 on node ip-10-0-22-220 On Tue, Dec 10, 2013 at 7:02 AM, Felix Frank < felix.frank@alumni.tu-berlin.de> wrote:> Hi, > > the approach looks fine. Can you share the complete path to the newapp > class when it''s not working? > > Beware that the puppet master process drops its privileges after basic > initialization. You may have to make sure that the puppet user (or > whichever is being used) can access your alternate modules tree. > > HTH, > Felix > > On 12/06/2013 08:12 PM, john.pyeatt@singlewire.com wrote: > > > > _Can anyone tell me the incantation I need to make puppetmasterd > > recognize my /opt/our-repo/puppetmaster/modules directory_? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A710DB.2060500%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. >-- John Pyeatt Singlewire Software, LLC www.singlewire.com ------------------ 608.661.1184 john.pyeatt@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLmkA4z15bgKC3TpdmDzwCqrLGDJPPH8QdfikjofKSOrWw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-10 15:14 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
On 12/10/2013 04:08 PM, John Pyeatt wrote:> My puppetmaster is running as the user puppet. I logged into the system > as puppet and was able to access the directory > /opt/our-repo/puppetmaster/modules. I did a chown -R puppet:puppet > /opt/our-repo/puppetmaster just to make certain and it still is > unrecognised. Just get the message in the puppet client log. > > 2013-12-10 14:57:51 +0000 Puppet (err): Could not retrieve catalog from > remote server: Error 400 on SERVER: Could not find class ec2metadata for > ip-10-0-22-220 on node ip-10-0-22-220OK, so what''s the full path to the manifest file that defines the class ec2metadata? Can you share your full puppet.conf? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A72FD0.3060208%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-10 15:37 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Full puppet.conf
[main]
pluginsync = true
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
modulepath = /etc/puppet/modules:/opt/ourrepo/puppetmaster/modules
ssldir = $vardir/ssl
Full path to the ec2metadata manifest is
/opt/ourrepo/puppetmaster/modules/ec2metadata/manifests/init.pp
On Tue, Dec 10, 2013 at 9:14 AM, Felix Frank <
felix.frank@alumni.tu-berlin.de> wrote:
> On 12/10/2013 04:08 PM, John Pyeatt wrote:
> > My puppetmaster is running as the user puppet. I logged into the
system
> > as puppet and was able to access the directory
> > /opt/our-repo/puppetmaster/modules. I did a chown -R puppet:puppet
> > /opt/our-repo/puppetmaster just to make certain and it still is
> > unrecognised. Just get the message in the puppet client log.
> >
> > 2013-12-10 14:57:51 +0000 Puppet (err): Could not retrieve catalog
from
> > remote server: Error 400 on SERVER: Could not find class ec2metadata
for
> > ip-10-0-22-220 on node ip-10-0-22-220
>
> OK, so what''s the full path to the manifest file that defines the
class
> ec2metadata? Can you share your full puppet.conf?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/puppet-users/52A72FD0.3060208%40alumni.tu-berlin.de
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
------------------
608.661.1184
john.pyeatt@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTLm2hzNLLQ5bwQ226OUiejQoN3%3Dc8LD%3DCCJ9HxKhwotm7g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-10 16:00 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Okay, looks fine so far. Next, can you share the output of puppet apply -dv -e ''include ec2metadata'' Thanks in advance! On 12/10/2013 04:37 PM, John Pyeatt wrote:> Full puppet.conf > > [main] > pluginsync = true > vardir = /var/lib/puppet > logdir = /var/log/puppet > rundir = /var/run/puppet > modulepath = /etc/puppet/modules:/opt/ourrepo/puppetmaster/modules > ssldir = $vardir/ssl > > Full path to the ec2metadata manifest is > /opt/ourrepo/puppetmaster/modules/ec2metadata/manifests/init.pp-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A73A87.2090605%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-10 16:15 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
I assume you wanted me to run this on the puppetmaster correct? It looks
like it is being found
Here is the output
[root@puppetmaster modules]# puppet apply -dv -e "include ec2metadata"
Info: Loading facts in
/etc/puppet/modules/stdlib/lib/facter/puppet_vardir.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/root_home.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/pe_version.rb
Info: Loading facts in /etc/puppet/modules/stdlib/lib/facter/facter_dot_d.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/subnetid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/vpcid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/azname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/instanceid.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/mac.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/vpcname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/instancetype.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/localipv4.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/regionname.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/accesskey.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/ec2_instance_server_type.rb
Info: Loading facts in
/opt/singlewire/ourrepo/modules/ec2metadata/lib/facter/secretkey.rb
Debug: importing
''/opt/singlewire/ourrepo/modules/ec2metadata/manifests/init.pp''
in
environment production
Debug: Automatically imported ec2metadata from ec2metadata into production
Debug: importing
''/opt/singlewire/ourrepo/modules/ec2metadata/manifests/init.pp''
in
environment production
Debug: Automatically imported ec2metadata from ec2metadata into production
Notice: Compiled catalog for puppetmaster.pyeatt.singlewire.com in
environment production in 0.06 seconds
Debug: Creating default schedules
Debug: Failed to load library ''selinux'' for feature
''selinux''
Debug: Using settings: adding file resource ''confdir'':
''File[/etc/puppet]{:path=>"/etc/puppet",
:ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
Debug: Using settings: adding file resource ''vardir'':
''File[/var/lib/puppet]{:path=>"/var/lib/puppet",
:ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
Debug: Failed to load library ''shadow'' for feature
''libshadow''
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/subnetid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/vpcid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/azname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/instanceid.rb
Info: Loading facts in /opt/ourrepo/modules/ec2metadata/lib/facter/mac.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/vpcname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/instancetype.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/localipv4.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/regionname.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/accesskey.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/ec2_instance_server_type.rb
Info: Loading facts in
/opt/ourrepo/modules/ec2metadata/lib/facter/secretkey.rb
Debug: Loaded state in 0.01 seconds
Info: Applying configuration version ''1386691733''
Debug: Finishing transaction 25450780
Debug: Storing state
Debug: Stored state in 0.01 seconds
Notice: Finished catalog run in 0.10 seconds
Debug: Using settings: adding file resource ''rrddir'':
''File[/var/lib/puppet/rrd]{:path=>"/var/lib/puppet/rrd",
:mode=>"750",
:owner=>"puppet", :group=>"puppet",
:ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false}''
Debug: Finishing transaction 25348500
On Tue, Dec 10, 2013 at 10:00 AM, Felix Frank <
felix.frank@alumni.tu-berlin.de> wrote:
> Okay, looks fine so far.
>
> Next, can you share the output of
>
> puppet apply -dv -e ''include ec2metadata''
>
> Thanks in advance!
>
> On 12/10/2013 04:37 PM, John Pyeatt wrote:
> > Full puppet.conf
> >
> > [main]
> > pluginsync = true
> > vardir = /var/lib/puppet
> > logdir = /var/log/puppet
> > rundir = /var/run/puppet
> > modulepath = /etc/puppet/modules:/opt/ourrepo/puppetmaster/modules
> > ssldir = $vardir/ssl
> >
> > Full path to the ec2metadata manifest is
> > /opt/ourrepo/puppetmaster/modules/ec2metadata/manifests/init.pp
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/puppet-users/52A73A87.2090605%40alumni.tu-berlin.de
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
------------------
608.661.1184
john.pyeatt@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTLk2GSzskOj6rok%3D%2BaTXuAZb7zZn_GCmNVaVRkA6VAY%3D1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-10 16:23 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Hmm, indeed. Do run as user puppet to see if that''s different. Otherwise, looks like you will need to stop the puppetmaster daemon (or apache if using passenger) and launch a debug version of the master with webrick puppet master --no-daemonize -dv Then have an agent check in and watch the master output for clues. HTH, Felix On 12/10/2013 05:15 PM, John Pyeatt wrote:> I assume you wanted me to run this on the puppetmaster correct? It looks > like it is being found-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A74015.3010108%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-10 16:30 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
OK, I''ll give your suggestions a shot. I''ve got meeting the rest of the day... lucky me. Thanks for all of the help. It is greatly appreciated. On Tue, Dec 10, 2013 at 10:23 AM, Felix Frank < felix.frank@alumni.tu-berlin.de> wrote:> Hmm, indeed. Do run as user puppet to see if that''s different. > > Otherwise, looks like you will need to stop the puppetmaster daemon (or > apache if using passenger) and launch a debug version of the master with > webrick > > puppet master --no-daemonize -dv > > Then have an agent check in and watch the master output for clues. > > HTH, > Felix > > On 12/10/2013 05:15 PM, John Pyeatt wrote: > > I assume you wanted me to run this on the puppetmaster correct? It looks > > like it is being found > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A74015.3010108%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. >-- John Pyeatt Singlewire Software, LLC www.singlewire.com ------------------ 608.661.1184 john.pyeatt@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLnzLH8FwiP4pu9ZZFMwx2-PYs2cFHZ3YD%3DGjTrq1cKZXg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-11 20:59 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
I''m still seeing the issue where modulepath isn''t being
recognized as
documented.
I tried running the following:
/usr/sbin/puppetmasterd --logdest /tmp/masterd.log --verbose --debug
--no-daemonize
The masterd.log file contains a bunch of stuff, but nothing that prints the
modulepath. I''ve marked the last interesting component in red.
I''m not exactly certain why the message below is printing three times.
*2013-12-11 20:28:35 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34*
Could it be because my puppet.conf has a [production], [test] and
[development] environment with a modulepath= for each one?
when I run puppet agent --environment test --configprint modulepath
I get the answer I would hope for and the directory is there. *Is it
possible that the master is running through a different code path and
getting the wrong result?*
*I am NOT a ruby guy. Is there somewhere in the puppet code where I can
output the modulepath value as it is represented in the running
application?*
The daemon is running as the user puppet, but I don''t see how it could
be a
permissions issue.
Again, any suggestions would be appreciated.
2013-12-11 20:28:09 +0000 Puppet (debug): Failed to load library
''selinux''
for feature ''selinux''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''confdir'':
''File[/etc/puppet]{:path=>"/etc/puppet",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''vardir'':
''File[/var/lib/puppet]{:path=>"/var/lib/puppet",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Failed to load library
''shadow''
for feature ''libshadow''
2013-12-11 20:28:09 +0000 Puppet (debug): Puppet::Type::User::ProviderPw:
file pw does not exist
2013-12-11 20:28:09 +0000 Puppet (debug):
Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dsimport does
not exist
2013-12-11 20:28:09 +0000 Puppet (debug):
Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist
2013-12-11 20:28:09 +0000 Puppet (debug): Failed to load library
''ldap'' for
feature ''ldap''
2013-12-11 20:28:09 +0000 Puppet (debug): Puppet::Type::User::ProviderLdap:
feature ldap is missing
2013-12-11 20:28:09 +0000 Puppet (debug): Puppet::Type::Group::ProviderPw:
file pw does not exist
2013-12-11 20:28:09 +0000 Puppet (debug):
Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not
exist
2013-12-11 20:28:09 +0000 Puppet (debug): Failed to load library
''ldap'' for
feature ''ldap''
2013-12-11 20:28:09 +0000 Puppet (debug):
Puppet::Type::Group::ProviderLdap: feature ldap is missing
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''logdir'':
''File[/var/lib/puppet/log]{:path=>"/var/lib/puppet/log",
:mode=>"750", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''statedir'':
''File[/var/lib/puppet/state]{:path=>"/var/lib/puppet/state",
:mode=>"1755",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''rundir'':
''File[/var/lib/puppet/run]{:path=>"/var/lib/puppet/run",
:mode=>"755", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''libdir'':
''File[/var/lib/puppet/lib]{:path=>"/var/lib/puppet/lib",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''certdir'':
''File[/etc/puppet/ssl/certs]{:path=>"/etc/puppet/ssl/certs",
:owner=>"puppet", :ensure=>:directory, :loglevel=>:debug,
:links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''ssldir'':
''File[/etc/puppet/ssl]{:path=>"/etc/puppet/ssl",
:mode=>"771", :owner=>"puppet",
:ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''publickeydir'':
''File[/etc/puppet/ssl/public_keys]{:path=>"/etc/puppet/ssl/public_keys",
:owner=>"puppet", :ensure=>:directory, :loglevel=>:debug,
:links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''localcacert'':
''File[/etc/puppet/ssl/certs/ca.pem]{:path=>"/etc/puppet/ssl/certs/ca.pem",
:mode=>"644", :owner=>"puppet", :ensure=>:file,
:loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''hostcrl'':
''File[/etc/puppet/ssl/crl.pem]{:path=>"/etc/puppet/ssl/crl.pem",
:mode=>"644", :owner=>"puppet", :ensure=>:file,
:loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''manifestdir'':
''File[/etc/puppet/manifests]{:path=>"/etc/puppet/manifests",
:ensure=>:directory, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''manifest'':
''File[/etc/puppet/manifests/site.pp]{:path=>"/etc/puppet/manifests/site.pp",
:ensure=>:file, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''masterhttplog'':
''File[/var/lib/puppet/log/masterhttp.log]{:path=>"/var/lib/puppet/log/masterhttp.log",
:mode=>"660", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''bucketdir'':
''File[/var/lib/puppet/bucket]{:path=>"/var/lib/puppet/bucket",
:mode=>"750", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''rest_authconfig'':
''File[/etc/puppet/auth.conf]{:path=>"/etc/puppet/auth.conf",
:ensure=>:file, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''yamldir'':
''File[/var/lib/puppet/yaml]{:path=>"/var/lib/puppet/yaml",
:mode=>"750",
:owner=>"puppet", :group=>"puppet",
:ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''server_datadir'':
''File[/var/lib/puppet/server_data]{:path=>"/var/lib/puppet/server_data",
:mode=>"750", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''reportdir'':
''File[/var/lib/puppet/reports]{:path=>"/var/lib/puppet/reports",
:mode=>"750", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''fileserverconfig'':
''File[/etc/puppet/fileserver.conf]{:path=>"/etc/puppet/fileserver.conf",
:ensure=>:file, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:09 +0000 Puppet (debug): Using settings: adding file
resource ''rrddir'':
''File[/var/lib/puppet/rrd]{:path=>"/var/lib/puppet/rrd",
:mode=>"750", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/log] (debug): Autorequiring
File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/state] (debug):
Autorequiring File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/run] (debug): Autorequiring
File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/lib] (debug): Autorequiring
File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/certs] (debug):
Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl] (debug): Autorequiring
File[/etc/puppet]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/public_keys] (debug):
Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/certificate_requests]
(debug): Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/private_keys] (debug):
Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/private] (debug):
Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000
/File[/etc/puppet/ssl/certs/puppetmaster.pyeatt.singlewire.com.pem]
(debug): Autorequiring File[/etc/puppet/ssl/certs]
2013-12-11 20:28:09 +0000
/File[/etc/puppet/ssl/private_keys/puppetmaster.pyeatt.singlewire.com.pem]
(debug): Autorequiring File[/etc/puppet/ssl/private_keys]
2013-12-11 20:28:09 +0000
/File[/etc/puppet/ssl/public_keys/puppetmaster.pyeatt.singlewire.com.pem]
(debug): Autorequiring File[/etc/puppet/ssl/public_keys]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/certs/ca.pem] (debug):
Autorequiring File[/etc/puppet/ssl/certs]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/ssl/crl.pem] (debug):
Autorequiring File[/etc/puppet/ssl]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/manifests] (debug):
Autorequiring File[/etc/puppet]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/manifests/site.pp] (debug):
Autorequiring File[/etc/puppet/manifests]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/log/masterhttp.log]
(debug): Autorequiring File[/var/lib/puppet/log]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/bucket] (debug):
Autorequiring File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/auth.conf] (debug):
Autorequiring File[/etc/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/yaml] (debug):
Autorequiring File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/server_data] (debug):
Autorequiring File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/reports] (debug):
Autorequiring File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 /File[/etc/puppet/fileserver.conf] (debug):
Autorequiring File[/etc/puppet]
2013-12-11 20:28:09 +0000 /File[/var/lib/puppet/rrd] (debug): Autorequiring
File[/var/lib/puppet]
2013-12-11 20:28:09 +0000 Puppet (debug): Finishing transaction 19101440
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''cadir'':
''File[/etc/puppet/ssl/ca]{:path=>"/etc/puppet/ssl/ca",
:mode=>"770", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''cacert'':
''File[/etc/puppet/ssl/ca/ca_crt.pem]{:path=>"/etc/puppet/ssl/ca/ca_crt.pem",
:mode=>"660", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''cakey'':
''File[/etc/puppet/ssl/ca/ca_key.pem]{:path=>"/etc/puppet/ssl/ca/ca_key.pem",
:mode=>"660", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''capub'':
''File[/etc/puppet/ssl/ca/ca_pub.pem]{:path=>"/etc/puppet/ssl/ca/ca_pub.pem",
:owner=>"puppet", :group=>"puppet", :ensure=>:file,
:loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''cacrl'':
''File[/etc/puppet/ssl/ca/ca_crl.pem]{:path=>"/etc/puppet/ssl/ca/ca_crl.pem",
:mode=>"664", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''caprivatedir'':
''File[/etc/puppet/ssl/ca/private]{:path=>"/etc/puppet/ssl/ca/private",
:mode=>"770", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''csrdir'':
''File[/etc/puppet/ssl/ca/requests]{:path=>"/etc/puppet/ssl/ca/requests",
:owner=>"puppet", :group=>"puppet",
:ensure=>:directory, :loglevel=>:debug,
:links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''signeddir'':
''File[/etc/puppet/ssl/ca/signed]{:path=>"/etc/puppet/ssl/ca/signed",
:mode=>"770", :owner=>"puppet",
:group=>"puppet", :ensure=>:directory,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''capass'':
''File[/etc/puppet/ssl/ca/private/ca.pass]{:path=>"/etc/puppet/ssl/ca/private/ca.pass",
:mode=>"660", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''serial'':
''File[/etc/puppet/ssl/ca/serial]{:path=>"/etc/puppet/ssl/ca/serial",
:mode=>"644", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''cert_inventory'':
''File[/etc/puppet/ssl/ca/inventory.txt]{:path=>"/etc/puppet/ssl/ca/inventory.txt",
:mode=>"644", :owner=>"puppet",
:group=>"puppet", :ensure=>:file,
:loglevel=>:debug, :links=>:follow, :backup=>false}''
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/ca_crt.pem] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/ca_key.pem] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/ca_pub.pem] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/ca_crl.pem] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/private] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/requests] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/signed] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/private/ca.pass]
(debug): Autorequiring File[/etc/puppet/ssl/ca/private]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/serial] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 /File[/etc/puppet/ssl/ca/inventory.txt] (debug):
Autorequiring File[/etc/puppet/ssl/ca]
2013-12-11 20:28:10 +0000 Puppet (debug): Finishing transaction 15898720
2013-12-11 20:28:10 +0000 Puppet (debug): Using cached certificate for ca
2013-12-11 20:28:10 +0000 Puppet (debug): Using cached certificate for ca
2013-12-11 20:28:10 +0000 Puppet (debug): Using cached certificate for
puppetmaster.pyeatt.singlewire.com
2013-12-11 20:28:10 +0000 Puppet (debug): Using settings: adding file
resource ''config'':
''File[/etc/puppet/puppet.conf]{:path=>"/etc/puppet/puppet.conf",
:ensure=>:file, :loglevel=>:debug, :links=>:follow,
:backup=>false}''
2013-12-11 20:28:10 +0000 Puppet (debug): Finishing transaction 20193480
2013-12-11 20:28:10 +0000 Puppet (debug): Closing streams for daemon mode
2013-12-11 20:28:10 +0000 Puppet (notice): Reopening log files
2013-12-11 20:28:10 +0000 Puppet (debug): Finished closing streams for
daemon mode
2013-12-11 20:28:10 +0000 Puppet (notice): Starting Puppet master version
3.3.2
2013-12-11 20:28:33 +0000 access[^/catalog/([^/]+)$] (info): allowing
''method'' find
2013-12-11 20:28:33 +0000 access[^/catalog/([^/]+)$] (info): allowing $1
access
2013-12-11 20:28:33 +0000 access[^/node/([^/]+)$] (info): allowing
''method''
find
2013-12-11 20:28:33 +0000 access[^/node/([^/]+)$] (info): allowing $1 access
2013-12-11 20:28:33 +0000 access[/certificate_revocation_list/ca] (info):
allowing ''method'' find
2013-12-11 20:28:33 +0000 access[/certificate_revocation_list/ca] (info):
allowing * access
2013-12-11 20:28:33 +0000 access[^/report/([^/]+)$] (info): allowing
''method'' save
2013-12-11 20:28:33 +0000 access[^/report/([^/]+)$] (info): allowing $1
access
2013-12-11 20:28:33 +0000 access[/file] (info): allowing * access
2013-12-11 20:28:33 +0000 access[/certificate/ca] (info): adding
authentication any
2013-12-11 20:28:33 +0000 access[/certificate/ca] (info): allowing
''method''
find
2013-12-11 20:28:33 +0000 access[/certificate/ca] (info): allowing * access
2013-12-11 20:28:33 +0000 access[/certificate/] (info): adding
authentication any
2013-12-11 20:28:33 +0000 access[/certificate/] (info): allowing
''method''
find
2013-12-11 20:28:33 +0000 access[/certificate/] (info): allowing * access
2013-12-11 20:28:33 +0000 access[/certificate_request] (info): adding
authentication any
2013-12-11 20:28:33 +0000 access[/certificate_request] (info): allowing
''method'' find
2013-12-11 20:28:33 +0000 access[/certificate_request] (info): allowing
''method'' save
2013-12-11 20:28:33 +0000 access[/certificate_request] (info): allowing *
access
2013-12-11 20:28:33 +0000 access[/] (info): adding authentication any
2013-12-11 20:28:33 +0000 Puppet (info): Inserting default
''/status'' (auth
true) ACL
2013-12-11 20:28:33 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:28:33 +0000 Puppet (debug): node supports formats: pson
b64_zlib_yaml yaml raw
2013-12-11 20:28:33 +0000 Puppet (debug): file_metadata supports formats:
pson b64_zlib_yaml yaml raw
2013-12-11 20:28:35 +0000 Puppet (info): Caching node for ip-10-0-22-34
*2013-12-11 20:28:35 +0000 Puppet (warning): Host is missing hostname
and/or domain: ip-10-0-22-342013-12-11 20:28:35 +0000 Puppet (err): Could
not find class ec2metadata for ip-10-0-22-34 on node
ip-10-0-22-342013-12-11 20:28:35 +0000 Puppet (err): Could not find class
ec2metadata for ip-10-0-22-34 on node ip-10-0-22-342013-12-11 20:28:35
+0000 Puppet (err): Could not find class ec2metadata for ip-10-0-22-34 on
node ip-10-0-22-34*
2013-12-11 20:28:35 +0000 Puppet (debug): Finishing transaction 20195420
2013-12-11 20:28:35 +0000 Puppet (debug): Received report to process from
ip-10-0-22-34
2013-12-11 20:28:35 +0000 Puppet (debug): Processing report from
ip-10-0-22-34 with processor Puppet::Reports::Store
2013-12-11 20:29:03 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:29:03 +0000 Puppet (debug): node supports formats: pson
b64_zlib_yaml yaml raw
2013-12-11 20:29:03 +0000 Puppet (debug): file_metadata supports formats:
pson b64_zlib_yaml yaml raw
2013-12-11 20:29:05 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (warning): Host is missing hostname and/or
domain: ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (debug): Received report to process from
ip-10-0-22-34
2013-12-11 20:29:05 +0000 Puppet (debug): Processing report from
ip-10-0-22-34 with processor Puppet::Reports::Store
2013-12-11 20:29:33 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:29:33 +0000 Puppet (debug): node supports formats: pson
b64_zlib_yaml yaml raw
2013-12-11 20:29:33 +0000 Puppet (debug): file_metadata supports formats:
pson b64_zlib_yaml yaml raw
2013-12-11 20:29:35 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (warning): Host is missing hostname and/or
domain: ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (debug): Received report to process from
ip-10-0-22-34
2013-12-11 20:29:35 +0000 Puppet (debug): Processing report from
ip-10-0-22-34 with processor Puppet::Reports::Store
2013-12-11 20:30:03 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:30:03 +0000 Puppet (debug): node supports formats: pson
b64_zlib_yaml yaml raw
2013-12-11 20:30:03 +0000 Puppet (debug): file_metadata supports formats:
pson b64_zlib_yaml yaml raw
2013-12-11 20:30:05 +0000 Puppet (info): Caching node for ip-10-0-22-34
2013-12-11 20:30:05 +0000 Puppet (warning): Host is missing hostname and/or
domain: ip-10-0-22-34
2013-12-11 20:30:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:30:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
2013-12-11 20:30:05 +0000 Puppet (err): Could not find class ec2metadata
for ip-10-0-22-34 on node ip-10-0-22-34
On Tue, Dec 10, 2013 at 10:30 AM, John Pyeatt
<john.pyeatt@singlewire.com>wrote:
> OK, I''ll give your suggestions a shot. I''ve got meeting
the rest of the
> day... lucky me. Thanks for all of the help. It is greatly appreciated.
>
>
> On Tue, Dec 10, 2013 at 10:23 AM, Felix Frank <
> felix.frank@alumni.tu-berlin.de> wrote:
>
>> Hmm, indeed. Do run as user puppet to see if that''s different.
>>
>> Otherwise, looks like you will need to stop the puppetmaster daemon (or
>> apache if using passenger) and launch a debug version of the master
with
>> webrick
>>
>> puppet master --no-daemonize -dv
>>
>> Then have an agent check in and watch the master output for clues.
>>
>> HTH,
>> Felix
>>
>> On 12/10/2013 05:15 PM, John Pyeatt wrote:
>> > I assume you wanted me to run this on the puppetmaster correct? It
looks
>> > like it is being found
>>
>> --
>> You received this message because you are subscribed to the Google
Groups
>> "Puppet Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
an
>> email to puppet-users+unsubscribe@googlegroups.com.
>> To view this discussion on the web visit
>>
https://groups.google.com/d/msgid/puppet-users/52A74015.3010108%40alumni.tu-berlin.de
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> John Pyeatt
> Singlewire Software, LLC
> www.singlewire.com
> ------------------
> 608.661.1184
> john.pyeatt@singlewire.com
>
--
John Pyeatt
Singlewire Software, LLC
www.singlewire.com
------------------
608.661.1184
john.pyeatt@singlewire.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAEisTL%3DJqKXZ9G0CguY9obUyoBhukKp3jSnGjEMGmovvsXk2hw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-12 08:57 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Yes. The agent does default to environment=production if not specified otherwise. Your [production] should match your [main] wrt. modulepath etc. HTH, Felix On 12/11/2013 09:59 PM, John Pyeatt wrote:> Could it be because my puppet.conf has a [production], [test] and > [development] environment with a modulepath= for each one?-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52A97A8E.2000308%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
John Pyeatt
2013-Dec-12 17:36 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
OK, Here is something I found with this problem When I run /etc/init.d/puppetmaster start in node/environment.rb validate_dirs is being passed /etc/puppet/modules:/usr/share/puppet/modules which isn''t what I have in /etc/puppet/puppet.conf modulepath=. BUT!!!!! if I just do a *touch /etc/puppet/puppet.con*f then puppetmaster calls reparse_config_files and it does in fact read my /etc/puppet/puppet.conf modulepath= correctly!!!! Like I said in the original thread, I don''t know the ruby language. But I suspect that there is some type of calling sequence issue going on. On Thu, Dec 12, 2013 at 2:57 AM, Felix Frank < felix.frank@alumni.tu-berlin.de> wrote:> Yes. > > The agent does default to environment=production if not specified > otherwise. Your [production] should match your [main] wrt. modulepath etc. > > HTH, > Felix > > On 12/11/2013 09:59 PM, John Pyeatt wrote: > > Could it be because my puppet.conf has a [production], [test] and > > [development] environment with a modulepath= for each one? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52A97A8E.2000308%40alumni.tu-berlin.de > . > For more options, visit https://groups.google.com/groups/opt_out. >-- John Pyeatt Singlewire Software, LLC www.singlewire.com ------------------ 608.661.1184 john.pyeatt@singlewire.com -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAEisTLkPc7J_ofHZU0o1psP8QOiZFwe7ggcOg3B9%3Dk3Xbs_8Ww%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Jeff Bachtel
2013-Dec-12 19:25 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
Felix, could that above behavior be linked to http://projects.puppetlabs.com/issues/23349 ? That is, could there be a hook/ordering issue? Sprang to mind, anyway. Probably cargo cult. Jeff On Thu, Dec 12, 2013 at 12:36 PM, John Pyeatt <john.pyeatt@singlewire.com>wrote:> OK, > Here is something I found with this problem > > When I run /etc/init.d/puppetmaster start in node/environment.rb > validate_dirs is being passed /etc/puppet/modules:/usr/share/puppet/modules > which isn''t what I have in /etc/puppet/puppet.conf modulepath=. > > BUT!!!!! if I just do a *touch /etc/puppet/puppet.con*f then > puppetmaster calls reparse_config_files and it does in fact read my > /etc/puppet/puppet.conf modulepath= correctly!!!! > > Like I said in the original thread, I don''t know the ruby language. But I > suspect that there is some type of calling sequence issue going on. > > > On Thu, Dec 12, 2013 at 2:57 AM, Felix Frank < > felix.frank@alumni.tu-berlin.de> wrote: > >> Yes. >> >> The agent does default to environment=production if not specified >> otherwise. Your [production] should match your [main] wrt. modulepath etc. >> >> HTH, >> Felix >> >> On 12/11/2013 09:59 PM, John Pyeatt wrote: >> > Could it be because my puppet.conf has a [production], [test] and >> > [development] environment with a modulepath= for each one? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users+unsubscribe@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/puppet-users/52A97A8E.2000308%40alumni.tu-berlin.de >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > John Pyeatt > Singlewire Software, LLC > www.singlewire.com > ------------------ > 608.661.1184 > john.pyeatt@singlewire.com > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscribe@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/CAEisTLkPc7J_ofHZU0o1psP8QOiZFwe7ggcOg3B9%3Dk3Xbs_8Ww%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAHahqg1dwEwx1fRtu3z8p7bv2KG7BfXezmdGjy9vjEaN7Dkrug%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Felix Frank
2013-Dec-13 09:52 UTC
Re: [Puppet Users] Can''t seem to get modulepath attribute recognized by puppetmasterd
On 12/12/2013 08:25 PM, Jeff Bachtel wrote:> Sprang to mind, anyway. Probably cargo cult.No, that''s actually a neat idea. So John, you may want to see if the latest RC master works better for you, that would pretty much confirm this. Thanks, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52AAD8C5.8050400%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.