Puppet users - Feb 2011 - trouble with retrieving information from current source

I''m rather new to puppet and I''ve been trying to get a module
to work
on the client servers.  Right now I''m trying to get
http://forge.puppetlabs.com/ghoneycutt/pam to run.  When I try to run
it I get these two errors:

err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of
resource: Could not retrieve information from source(s)
puppet:///modules/pam/Ubuntu/sshd at /etc/puppet/modules/pam/manifests/
init.pp:19
err: //pam/File[/etc/pam.d/login]: Failed to retrieve current state of
resource: Could not retrieve information from source(s)
puppet:///modules/pam/Ubuntu/login at /etc/puppet/modules/pam/
manifests/init.pp:19

I am pretty sure that it is something that I haven''t configured yet; I
have changed my fileserver.conf file to try and fix it, but nothing
seems to work, and I am still new enough that I''m not sure what to
change to fix this.  Right now it''s:

# fileserver.conf
[files]
 path /etc/puppet/manifests
 allow *.domain.local
 allow IP ADDR

[modules]
 allow *.domain.local
 allow IP ADDR

[plugins]
 allow *.domain.local
 allow IP ADDR

Also, as of now I have Puppet doing very little (other than trying to
get this pam module to work I''m using it to manage the /etc/hosts
file), and I think that my biggest problem is that something isn''t
configured the right way, or I am forgetting to add something.  Any
insight to what I''m doing wrong is greatly appreciated. Thanks!

-- 
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.

On 02/15/2011 05:32 PM, rredeno2 wrote:
> I''m rather new to puppet and I''ve been trying to get a
module to work
> on the client servers.  Right now I''m trying to get
> http://forge.puppetlabs.com/ghoneycutt/pam to run.  When I try to run
> it I get these two errors:
> 
> err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of
> resource: Could not retrieve information from source(s)
> puppet:///modules/pam/Ubuntu/sshd at /etc/puppet/modules/pam/manifests/
> init.pp:19
> err: //pam/File[/etc/pam.d/login]: Failed to retrieve current state of
> resource: Could not retrieve information from source(s)
> puppet:///modules/pam/Ubuntu/login at /etc/puppet/modules/pam/
> manifests/init.pp:19
Hi,

is that really the error message? It seems to be missing a component to
me. I do see where the error originates in the manifest, but the part
specifying what the non-working source actually *is* doesn''t appear...

That may just be me being stuck with 0.25.5 atm, but if the error
logging has been cropped of this bit of info, that would be a regression
imo.

Please double-check the error message and repost if necessary.

Cheers,
Felix
> I am pretty sure that it is something that I haven''t configured
yet; I
> have changed my fileserver.conf file to try and fix it, but nothing
> seems to work, and I am still new enough that I''m not sure what to
> change to fix this.  Right now it''s:
> 
> # fileserver.conf
> [files]
>  path /etc/puppet/manifests
>  allow *.domain.local
>  allow IP ADDR
> 
> [modules]
>  allow *.domain.local
>  allow IP ADDR
> 
> [plugins]
>  allow *.domain.local
>  allow IP ADDR
> 
> Also, as of now I have Puppet doing very little (other than trying to
> get this pam module to work I''m using it to manage the /etc/hosts
> file), and I think that my biggest problem is that something isn''t
> configured the right way, or I am forgetting to add something.  Any
> insight to what I''m doing wrong is greatly appreciated. Thanks!
> 
-- 
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.

What component do you think I''m missing?

I checked the error again and this is what I''ve done:

puppetmasterd --verbose --no-daemonize (when I run this command, it
first says that it can''t create a PID file, so I have to remove the
old puppetmasterd.pid file, rerun the command, and then it runs.  Is
this the correct way to handle this or is this another error?)

Then I ran  sudo puppetd --server localserver.com --test --debug --
trace and got:

debug: Failed to load library ''selinux'' for feature
''selinux''
debug: Puppet::Type::User::ProviderLdap: true value when expecting
false
debug: Puppet::Type::User::ProviderUser_role_add: file roledel does
not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/
lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/
lib/puppet]
debug: /File[/var/lib/puppet/ssl/certs/monitor.cazoodle.com.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private_keys/
monitor.cazoodle.com.pem]: Autorequiring File[/var/lib/puppet/ssl/
private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/
var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/
lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/ssl/public_keys/
monitor.cazoodle.com.pem]: Autorequiring File[/var/lib/puppet/ssl/
public_keys]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/
var/lib/puppet/ssl/certs]
debug: Finishing transaction 70220780888980 with 0 changes
debug: Using cached certificate for ca, good until Fri Jan 22 21:15:06
UTC 2016
debug: Using cached certificate for monitor.cazoodle.com, good until
Fri Jan 22 21:15:06 UTC 2016
debug: Loaded state in 0.00 seconds
info: Retrieving plugin
debug: Using cached certificate for ca, good until Fri Jan 22 21:15:06
UTC 2016
debug: Using cached certificate for monitor.cazoodle.com, good until
Fri Jan 22 21:15:06 UTC 2016
debug: Using cached certificate_revocation_list for ca, good until
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: Finishing transaction 70220780526300 with 0 changes
debug: Executing ''/etc/puppet/etckeeper-commit-pre''
debug: catalog supports formats: b64_zlib_yaml marshal pson raw yaml;
using pson
info: Caching catalog for monitor.cazoodle.com
debug: Creating default schedules
debug: Finishing transaction 70220781391100 with 0 changes
debug: Loaded state in 0.00 seconds
debug: //pam/Pam::Accesslogin[systems]/Exec[present : systems : ALL]/
require: requires Exec[prep access.conf]
debug: //pam/Pam::Accesslogin[root]/Exec[present : root : ALL]/
require: requires Exec[prep access.conf]
info: Applying configuration version ''1297953008''
debug: //pam/Exec[prep access.conf]: Executing check ''tail -n 1 /etc/
security/access.conf | grep ''^\- : ALL : ALL''''
debug: Executing ''tail -n 1 /etc/security/access.conf | grep
''^\- :
ALL : ALL''''
debug: //pam/Pam::Accesslogin[root]/Exec[present : root : ALL]:
Executing check ''grep '' : root : ALL''
/etc/security/access.conf''
debug: Executing ''grep '' : root : ALL''
/etc/security/access.conf''
debug: //pam/Pam::Accesslogin[systems]/Exec[present : systems : ALL]:
Executing check ''grep '' : systems : ALL''
/etc/security/access.conf''
debug: Executing ''grep '' : systems : ALL''
/etc/security/access.conf''
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
/usr/lib/ruby/1.8/puppet/parameter.rb:401:in `fail''
/usr/lib/ruby/1.8/puppet/type/file/source.rb:160:in `init_metadata''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `send''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `cached_value''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:46:in `metadata''
/usr/lib/ruby/1.8/puppet/type/file/source.rb:111:in
`copy_source_values''
/usr/lib/ruby/1.8/puppet/type/file.rb:630:in `retrieve''
/usr/lib/ruby/1.8/puppet/type.rb:726:in `evaluate''
/usr/lib/ruby/1.8/puppet/transaction.rb:62:in `apply''
/usr/lib/ruby/1.8/puppet/transaction.rb:251:in
`eval_children_and_apply_resource''
/usr/lib/ruby/1.8/puppet/util.rb:418:in `thinmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:417:in `thinmark''
/usr/lib/ruby/1.8/puppet/transaction.rb:250:in
`eval_children_and_apply_resource''
/usr/lib/ruby/1.8/puppet/transaction.rb:207:in `eval_resource''
/usr/lib/ruby/1.8/puppet/transaction.rb:296:in `evaluate''
/usr/lib/ruby/1.8/puppet/util.rb:418:in `thinmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:417:in `thinmark''
/usr/lib/ruby/1.8/puppet/transaction.rb:295:in `evaluate''
/usr/lib/ruby/1.8/puppet/transaction.rb:289:in `collect''
/usr/lib/ruby/1.8/puppet/transaction.rb:289:in `evaluate''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:142:in `apply''
/usr/lib/ruby/1.8/puppet/configurer.rb:169:in `run''
/usr/lib/ruby/1.8/puppet/util.rb:178:in `benchmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:177:in `benchmark''
/usr/lib/ruby/1.8/puppet/configurer.rb:168:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:134:in `with_client''
/usr/lib/ruby/1.8/puppet/agent.rb:51:in `run''
/usr/lib/ruby/1.8/puppet/application/puppetd.rb:103:in `onetime''
/usr/lib/ruby/1.8/puppet/application.rb:226:in `send''
/usr/lib/ruby/1.8/puppet/application.rb:226:in `run_command''
/usr/lib/ruby/1.8/puppet/application.rb:217:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:306:in `exit_on_fail''
/usr/lib/ruby/1.8/puppet/application.rb:217:in `run''
/usr/sbin/puppetd:159
err: //pam/File[/etc/pam.d/login]: Failed to retrieve current state of
resource: Could not retrieve information from source(s)
puppet:///modules/pam/Ubuntu/login at /etc/puppet/modules/pam/
manifests/init.pp:19
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
/usr/lib/ruby/1.8/puppet/parameter.rb:401:in `fail''
/usr/lib/ruby/1.8/puppet/type/file/source.rb:160:in `init_metadata''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `send''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `cached_value''
/usr/lib/ruby/1.8/puppet/util/cacher.rb:46:in `metadata''
/usr/lib/ruby/1.8/puppet/type/file/source.rb:111:in
`copy_source_values''
/usr/lib/ruby/1.8/puppet/type/file.rb:630:in `retrieve''
/usr/lib/ruby/1.8/puppet/type.rb:726:in `evaluate''
/usr/lib/ruby/1.8/puppet/transaction.rb:62:in `apply''
/usr/lib/ruby/1.8/puppet/transaction.rb:251:in
`eval_children_and_apply_resource''
/usr/lib/ruby/1.8/puppet/util.rb:418:in `thinmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:417:in `thinmark''
/usr/lib/ruby/1.8/puppet/transaction.rb:250:in
`eval_children_and_apply_resource''
/usr/lib/ruby/1.8/puppet/transaction.rb:207:in `eval_resource''
/usr/lib/ruby/1.8/puppet/transaction.rb:296:in `evaluate''
/usr/lib/ruby/1.8/puppet/util.rb:418:in `thinmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:417:in `thinmark''
/usr/lib/ruby/1.8/puppet/transaction.rb:295:in `evaluate''
/usr/lib/ruby/1.8/puppet/transaction.rb:289:in `collect''
/usr/lib/ruby/1.8/puppet/transaction.rb:289:in `evaluate''
/usr/lib/ruby/1.8/puppet/resource/catalog.rb:142:in `apply''
/usr/lib/ruby/1.8/puppet/configurer.rb:169:in `run''
/usr/lib/ruby/1.8/puppet/util.rb:178:in `benchmark''
/usr/lib/ruby/1.8/benchmark.rb:308:in `realtime''
/usr/lib/ruby/1.8/puppet/util.rb:177:in `benchmark''
/usr/lib/ruby/1.8/puppet/configurer.rb:168:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/sync.rb:230:in `synchronize''
/usr/lib/ruby/1.8/puppet/agent.rb:53:in `run''
/usr/lib/ruby/1.8/puppet/agent.rb:134:in `with_client''
/usr/lib/ruby/1.8/puppet/agent.rb:51:in `run''
/usr/lib/ruby/1.8/puppet/application/puppetd.rb:103:in `onetime''
/usr/lib/ruby/1.8/puppet/application.rb:226:in `send''
/usr/lib/ruby/1.8/puppet/application.rb:226:in `run_command''
/usr/lib/ruby/1.8/puppet/application.rb:217:in `run''
/usr/lib/ruby/1.8/puppet/application.rb:306:in `exit_on_fail''
/usr/lib/ruby/1.8/puppet/application.rb:217:in `run''
/usr/sbin/puppetd:159
err: //pam/File[/etc/pam.d/sshd]: Failed to retrieve current state of
resource: Could not retrieve information from source(s)
puppet:///modules/pam/Ubuntu/sshd at /etc/puppet/modules/pam/manifests/
init.pp:19
debug: Finishing transaction 70220781344240 with 0 changes
debug: Storing state
debug: Stored state in 0.01 seconds
notice: Finished catalog run in 0.28 seconds
debug: Executing ''/etc/puppet/etckeeper-commit-post''

This error has me confused, because as it appears to me, the file
location that it''s saying it can''t retrieve the information
from
exists in the right place.  Thanks

-- 
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.

On 02/17/2011 03:45 PM, rredeno2 wrote:
> What component do you think I''m missing?
Oops, sorry - I didn''t look careful enough yesterday.

So you have a modules/pam/files/Ubuntu/login file?

Does the puppetmaster log any problems of its own during the client run?

Regards,
Felix

-- 
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.

The exact file extension is /modules/pam/files/CentOS/login (or $ssh), and 
both the login and sshd files are there .  I was considering changing CentOS 
to Ubuntu to see if this made a difference, but in the pam module''s
init.pp
file, it has the $operatingsystem variable where I believe the CentOS 
directory was located. (puppet:///modules/pam/$operatingsystem/login)  I was 
assuming that the module takes into account various operating systems, and 
wasn''t sure of what effect it would have on the rest of the module if I
changed it.  I did change $operatingsystem to CentOS to see if having the 
exact file extension would work, but that had the same error, but just with 
saying CentOS instead of Ubuntu in the source file path, so I changed it 
back.

And the original two errors are the only ones that I''m getting when I
run
it.

Thanks

-- 
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.

On 02/17/2011 04:54 PM, rredeno2 wrote:
> The exact file extension is /modules/pam/files/CentOS/login (or $ssh),
> and both the login and sshd files are there .  I was considering
> changing CentOS to Ubuntu to see if this made a difference, but in the
> pam module''s init.pp file, it has the $operatingsystem variable
where I
> believe the CentOS directory was located.
> (puppet:///modules/pam/$operatingsystem/login)  I was assuming that the
> module takes into account various operating systems, and wasn''t
sure of
> what effect it would have on the rest of the module if I changed it.  I
> did change $operatingsystem to CentOS to see if having the exact file
> extension would work, but that had the same error, but just with saying
> CentOS instead of Ubuntu in the source file path, so I changed it back.
> 
> And the original two errors are the only ones that I''m getting
when I
> run it.
The module structure requires you to have a subdirectory for each client
operatingsystem you deploy with puppet.

I cannot infer what the error cause is when you do have, in fact, a
subdirectory named Ubuntu that contains the needed files. Create this
directory and watch the puppetmaster''s debug output during a run once
more (although I fear that may turn up nothing).

HTH,
Felix

-- 
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.

That worked!  I wish I would''ve just done that earlier.  Ok, so for
each
operating system that I have, I just need a new subdirectory?  That''s
easy
enough, and I think that I can figure out how to make it recognize the 
different operating systems.  This also makes me feel better that I 
apparently set everything else up correctly.  Thank you so much for your 
help, even though it turned out to be rather trivial.

-- 
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.