I am currently working on getting a functional HP-UX Agent
communicating to an RHEL Master.
Agent
OS: HP-UX 11.31 Itanium
Ruby: 1.9.1 (depot from iexpress)
Puppet 2.7.12 - Installed from Source
Facter 1.6.7 - Installed from Source
They are communicating but I get errors when obtaining the reports
On Console:
Importing report report-5774-1.yaml at 2012-04-03 19:45 UTC
undefined method `each'' for nil:NilClass
Backtrace
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in
`extended''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in
`extended''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
`extend''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
`extended''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
`extend''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
`create_from_yaml''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in
`create_from_yaml_file''
When starting the agent:
warning: iconv couldn''t be loaded, which is required for UTF-8/UTF-16
conversions
debug: Failed to load library ''selinux'' for feature
''selinux''
debug: Failed to load library ''shadow'' for feature
''libshadow''
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Puppet::Type::User::ProviderUseradd: file chage does not exist
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does
not exist
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/certs/<agent>.pem]: Autorequiring File[/
etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/private_keys/<agent>.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/public_keys/<agent>.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/
lib/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]:
Autorequiring File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]:
Autorequiring File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/
lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: Finishing transaction 549707456
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/certs/<agent>.pem]: Autorequiring File[/
etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/private_keys/<agent>.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/public_keys/<agent>.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: Finishing transaction 541134144
debug: Using cached certificate for ca
debug: Using cached certificate for <agent>
notice: Starting Puppet client version 2.7.12
debug: Finishing transaction 545632880
debug: Loaded state in 0.00 seconds
processor - invalid major number
usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c
char_major]
[-e major] [major] ...
uname: illegal option -- p
usage: uname [-amnrsvil] [-S nodename]
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw
yaml; using pson
debug: Using cached certificate for ca
debug: Using cached certificate for<agent>
debug: Using cached certificate_revocation_list for ca
info: Caching catalog for <agent>
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ''1333484340''
debug: /Schedule[daily]: Skipping device resources because running on
a host
debug: /Schedule[monthly]: Skipping device resources because running
on a host
debug: /Schedule[hourly]: Skipping device resources because running on
a host
debug: /Schedule[never]: Skipping device resources because running on
a host
debug: /Schedule[weekly]: Skipping device resources because running on
a host
debug: /Schedule[puppet]: Skipping device resources because running on
a host
debug: Finishing transaction 540021248
debug: Storing state
debug: Stored state in 0.04 seconds
notice: Finished catalog run in 0.12 seconds
debug: Value of ''preferred_serialization_format'' (pson) is
invalid for
report, using default (yaml)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
yaml
--
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.
I now have it communicate regularly between master and client but I am now getting some reporting issues. err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 EDT err Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ''undef'' at /opt/puppet/ share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node hpoktst3.ddmi.intra.renhsc.com Puppet 2012-04-05 10:22 EDT notice Using cached catalog Puppet 2012-04-05 10:22 EDT info Not using expired catalog for hpoktst3.ddmi.intra.renhsc.com from cache; expired at 2012-04-04 12:51:17 -0500 Puppet 2012-04-05 10:22 EDT debug catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson Puppet 2012-04-05 10:21 EDT It is correctly inventorying the server, but it is missing a few facts normally on other nodes architecture ia64 clientversion 2.7.12 environment production facterversion 1.6.7 hardwaremodel ia64 id root interfaces lo0,lan0 is_virtual false kernel HP-UX kernelmajversion B.11 kernelrelease B.11.31 kernelversion B.11.31 operatingsystem HP-UX operatingsystemrelease B.11.31 osfamily HP-UX path /opt/iexpress/ruby/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/ contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/ipf/bin:/opt/ nettladm/bin:/opt/fcms/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/sas/bin:/ opt/graphics/common/bin:/opt/sec_mgmt/bastille/bin:/opt/drd/bin:/opt/ dsau/bin:/opt/dsau/sbin:/opt/resmon/bin:/opt/perf/bin:/usr/bin/X11:/ usr/contrib/bin/X11:/usr/contrib/kwdb/bin:/opt/prm/bin:/opt/sfm/bin:/ opt/swm/bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/sentinel/bin:/opt/ swa/bin:/opt/hpsmh/bin:/opt/langtools/bin:/opt/wlm/bin:/opt/gwlm/bin:/ opt/propplus/bin:/opt/gvsd/bin:/opt/atok/bin:/opt/caliper/bin:/opt/ firefox:/opt/gnome/bin:/opt/mozilla:/opt/perl_32/bin:/opt/perl_64/bin:/ opt/thunderbird:/opt/ignite/bin:/opt/cfg2html:/sbin:/home/root:/opt/OV/ bin:/usr/local/bin:/opt/omni/bin:/opt/omni/lbin:/opt/omni/sbin ps ps -ef puppetversion 2.7.12 rubyversion 1.9.1 timezone EDT uptime 21 days uptime_days 21 uptime_hours 525 uptime_seconds 1892399 virtual physical On Apr 3, 4:21 pm, Michael Glatz <mfgl...@gmail.com> wrote:> I am currently working on getting a functional HP-UX Agent > communicating to an RHEL Master. > > Agent > OS: HP-UX 11.31 Itanium > Ruby: 1.9.1 (depot from iexpress) > Puppet 2.7.12 - Installed from Source > Facter 1.6.7 - Installed from Source > > They are communicating but I get errors when obtaining the reports > > On Console: > Importing report report-5774-1.yaml at 2012-04-03 19:45 UTC > undefined method `each'' for nil:NilClass > Backtrace > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in > `extended'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in > `extended'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > `extend'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > `extended'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > `extend'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > `create_from_yaml'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in > `create_from_yaml_file'' > > When starting the agent: > warning: iconv couldn''t be loaded, which is required for UTF-8/UTF-16 > conversions > debug: Failed to load library ''selinux'' for feature ''selinux'' > debug: Failed to load library ''shadow'' for feature ''libshadow'' > debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ > dscl does not exist > debug: Puppet::Type::User::ProviderUseradd: file chage does not exist > debug: Failed to load library ''ldap'' for feature ''ldap'' > debug: Puppet::Type::User::ProviderLdap: feature ldap is missing > debug: Puppet::Type::User::ProviderPw: file pw does not exist > debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does > not exist > debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ > puppet] > debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] > debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/ > puppet/ssl] > debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring > File[/etc/puppet/ssl] > debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/ > puppet/ssl] > debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/etc/puppet/ssl/certs/<agent>.pem]: Autorequiring File[/ > etc/puppet/ssl/certs] > debug: /File[/etc/puppet/ssl/private_keys/<agent>.pem]: Autorequiring > File[/etc/puppet/ssl/private_keys] > debug: /File[/etc/puppet/ssl/public_keys/<agent>.pem]: Autorequiring > File[/etc/puppet/ssl/public_keys] > debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/ > puppet/ssl/certs] > debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/ > var/lib/puppet/state] > debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/ > puppet] > debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/ > puppet] > debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/ > var/lib/puppet/state] > debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/ > var/lib/puppet/state] > debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/ > lib/puppet] > debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: > Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/state/last_run_report.yaml]: > Autorequiring File[/var/lib/puppet/state] > debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/ > lib/puppet/state] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ > puppet] > debug: Finishing transaction 549707456 > debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ > puppet] > debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] > debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] > debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] > debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/ > puppet/ssl] > debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring > File[/etc/puppet/ssl] > debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/ > puppet/ssl] > debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/etc/puppet/ssl/certs/<agent>.pem]: Autorequiring File[/ > etc/puppet/ssl/certs] > debug: /File[/etc/puppet/ssl/private_keys/<agent>.pem]: Autorequiring > File[/etc/puppet/ssl/private_keys] > debug: /File[/etc/puppet/ssl/public_keys/<agent>.pem]: Autorequiring > File[/etc/puppet/ssl/public_keys] > debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/ > puppet/ssl/certs] > debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ > ssl] > debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/ > puppet] > debug: Finishing transaction 541134144 > debug: Using cached certificate for ca > debug: Using cached certificate for <agent> > notice: Starting Puppet client version 2.7.12 > debug: Finishing transaction 545632880 > debug: Loaded state in 0.00 seconds > processor - invalid major number > usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c > char_major] > [-e major] [major] ... > uname: illegal option -- p > usage: uname [-amnrsvil] [-S nodename] > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw > yaml; using pson > debug: Using cached certificate for ca > debug: Using cached certificate for<agent> > debug: Using cached certificate_revocation_list for ca > info: Caching catalog for <agent> > debug: Creating default schedules > debug: Loaded state in 0.00 seconds > info: Applying configuration version ''1333484340'' > debug: /Schedule[daily]: Skipping device resources because running on > a host > debug: /Schedule[monthly]: Skipping device resources because running > on a host > debug: /Schedule[hourly]: Skipping device resources because running on > a host > debug: /Schedule[never]: Skipping device resources because running on > a host > debug: /Schedule[weekly]: Skipping device resources because running on > a host > debug: /Schedule[puppet]: Skipping device resources because running on > a host > debug: Finishing transaction 540021248 > debug: Storing state > debug: Stored state in 0.04 seconds > notice: Finished catalog run in 0.12 seconds > debug: Value of ''preferred_serialization_format'' (pson) is invalid for > report, using default (yaml) > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using > yaml-- 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 Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz <mfglatz@gmail.com> wrote:> I now have it communicate regularly between master and client but I am > now getting some reporting issues. > > err Could not retrieve catalog; skipping run Puppet 2012-04-05 10:22 > EDT > > err Could not retrieve catalog from remote server: Error 400 on > SERVER: No matching value for selector param ''undef'' at /opt/puppet/ > share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node > hpoktst3.ddmi.intra.renhsc.com Puppet 2012-04-05 10:22 EDTYou are connecting a puppet agent to a puppet enterprise master. The pe_mcollective module needs a list of facts provided by the enterprise installer. If you look at /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt, you''ll see the list of facts. Since the puppet installation was done from source, the system is also are missing mcollective and it''s dependencies. I would remove the system from the default group in the puppet enterprise console so the pe_* modules are not part of the node. Thanks, Nan -- 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.
Removing the default group worked for the most part but I am still
running into some issues
It cataloged correctly and even ran the test class I created
notice: Starting Puppet client version 2.7.12
debug: Finishing transaction 545631632
debug: Loaded state in 0.00 seconds
processor - invalid major number
usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c
char_major]
[-e major] [major] ...
uname: illegal option -- p
usage: uname [-amnrsvil] [-S nodename]
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw
yaml; using pson
debug: Using cached certificate for ca
debug: Using cached certificate for <agent>
debug: Using cached certificate_revocation_list for ca
info: Caching catalog for <agent>
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ''1333637360''
debug: /Schedule[daily]: Skipping device resources because running on
a host
debug: /Schedule[monthly]: Skipping device resources because running
on a host
debug: /Schedule[hourly]: Skipping device resources because running on
a host
notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group
changed ''sys'' to ''root''
debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container
Class[Core_permissions] will propagate my refresh event
notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure:
created
debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container
Class[Core_permissions] will propagate my refresh event
notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group
changed ''sys'' to ''root''
notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode
changed ''0444'' to ''0644''
debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container
Class[Core_permissions] will propagate my refresh event
debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container
Class[Core_permissions] will propagate my refresh event
debug: Class[Core_permissions]: The container Stage[main] will
propagate my refresh event
debug: /Schedule[never]: Skipping device resources because running on
a host
debug: /Schedule[weekly]: Skipping device resources because running on
a host
debug: /Schedule[puppet]: Skipping device resources because running on
a host
debug: Finishing transaction 549485440
debug: Storing state
debug: Stored state in 0.04 seconds
notice: Finished catalog run in 0.11 seconds
debug: Value of ''preferred_serialization_format'' (pson) is
invalid for
report, using default (yaml)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
yaml
I am now receiving this issue again
mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT
undefined method `each'' for nil:NilClass
Backtrace
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in
`extended''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in
`extended''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
`extend''
/opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in
`extended''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
`extend''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in
`create_from_yaml''
/opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in
`create_from_yaml_file''
Also it automatically added the node back to default, anyway to
prevent that?
On Apr 5, 10:45 am, Nan Liu <n...@puppetlabs.com>
wrote:> On Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz <mfgl...@gmail.com>
wrote:
> > I now have it communicate regularly between master and client but I am
> > now getting some reporting issues.
>
> > err Could not retrieve catalog; skipping run Puppet 2012-04-05
10:22
> > EDT
>
> > err Could not retrieve catalog from remote server: Error 400 on
> > SERVER: No matching value for selector param ''undef''
at /opt/puppet/
> > share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node
> > hpoktst3.ddmi.intra.renhsc.com Puppet 2012-04-05 10:22 EDT
>
> You are connecting a puppet agent to a puppet enterprise master. The
> pe_mcollective module needs a list of facts provided by the enterprise
> installer. If you look at
> /etc/puppetlabs/facter/facts.d/puppet_enterprise_installer.txt,
you''ll
> see the list of facts. Since the puppet installation was done from
> source, the system is also are missing mcollective and it''s
> dependencies. I would remove the system from the default group in the
> puppet enterprise console so the pe_* modules are not part of the
> node.
>
> Thanks,
>
> Nan
--
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 Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz <mfglatz@gmail.com> wrote:> Removing the default group worked for the most part but I am still > running into some issues > > It cataloged correctly and even ran the test class I created > > notice: Starting Puppet client version 2.7.12 > debug: Finishing transaction 545631632 > debug: Loaded state in 0.00 seconds > processor - invalid major number > usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c > char_major] > [-e major] [major] ... > uname: illegal option -- p > usage: uname [-amnrsvil] [-S nodename] > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw > yaml; using pson > debug: Using cached certificate for ca > debug: Using cached certificate for <agent> > debug: Using cached certificate_revocation_list for ca > info: Caching catalog for <agent> > debug: Creating default schedules > debug: Loaded state in 0.00 seconds > info: Applying configuration version ''1333637360'' > debug: /Schedule[daily]: Skipping device resources because running on > a host > debug: /Schedule[monthly]: Skipping device resources because running > on a host > debug: /Schedule[hourly]: Skipping device resources because running on > a host > notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group > changed ''sys'' to ''root'' > debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container > Class[Core_permissions] will propagate my refresh event > notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: > created > debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container > Class[Core_permissions] will propagate my refresh event > notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group > changed ''sys'' to ''root'' > notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode > changed ''0444'' to ''0644'' > debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container > Class[Core_permissions] will propagate my refresh event > debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container > Class[Core_permissions] will propagate my refresh event > debug: Class[Core_permissions]: The container Stage[main] will > propagate my refresh event > debug: /Schedule[never]: Skipping device resources because running on > a host > debug: /Schedule[weekly]: Skipping device resources because running on > a host > debug: /Schedule[puppet]: Skipping device resources because running on > a host > debug: Finishing transaction 549485440 > debug: Storing state > debug: Stored state in 0.04 seconds > notice: Finished catalog run in 0.11 seconds > debug: Value of ''preferred_serialization_format'' (pson) is invalid for > report, using default (yaml) > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using > yaml > > I am now receiving this issue again > > mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT > undefined method `each'' for nil:NilClass > Backtrace > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in > `extended'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in > `extended'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > `extend'' > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > `extended'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > `extend'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > `create_from_yaml'' > /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in > `create_from_yaml_file''If you are using ruby 1.9.1, it is known to be problematic: http://docs.puppetlabs.com/guides/faq.html> Also it automatically added the node back to default, anyway to > prevent that?Looks like there''s a background task automatically adding nodes. I don''t know a good way around this issue. You can move the pe-* class to another group but you will need to manually add nodes to that group afterwards. HTH, Nan -- 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 Thu, Apr 5, 2012 at 8:22 AM, Nan Liu <nan@puppetlabs.com> wrote:> On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz <mfglatz@gmail.com> wrote: > > Removing the default group worked for the most part but I am still > > running into some issues > > > > It cataloged correctly and even ran the test class I created > > > > notice: Starting Puppet client version 2.7.12 > > debug: Finishing transaction 545631632 > > debug: Loaded state in 0.00 seconds > > processor - invalid major number > > usage: lsdev [-h] [-d driver | -C class] [-b block_major] [-c > > char_major] > > [-e major] [major] ... > > uname: illegal option -- p > > usage: uname [-amnrsvil] [-S nodename] > > debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw > > yaml; using pson > > debug: Using cached certificate for ca > > debug: Using cached certificate for <agent> > > debug: Using cached certificate_revocation_list for ca > > info: Caching catalog for <agent> > > debug: Creating default schedules > > debug: Loaded state in 0.00 seconds > > info: Applying configuration version ''1333637360'' > > debug: /Schedule[daily]: Skipping device resources because running on > > a host > > debug: /Schedule[monthly]: Skipping device resources because running > > on a host > > debug: /Schedule[hourly]: Skipping device resources because running on > > a host > > notice: /Stage[main]/Core_permissions/File[/etc/fstab]/group: group > > changed ''sys'' to ''root'' > > debug: /Stage[main]/Core_permissions/File[/etc/fstab]: The container > > Class[Core_permissions] will propagate my refresh event > > notice: /Stage[main]/Core_permissions/File[/etc/crontab]/ensure: > > created > > debug: /Stage[main]/Core_permissions/File[/etc/crontab]: The container > > Class[Core_permissions] will propagate my refresh event > > notice: /Stage[main]/Core_permissions/File[/etc/passwd]/group: group > > changed ''sys'' to ''root'' > > notice: /Stage[main]/Core_permissions/File[/etc/passwd]/mode: mode > > changed ''0444'' to ''0644'' > > debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container > > Class[Core_permissions] will propagate my refresh event > > debug: /Stage[main]/Core_permissions/File[/etc/passwd]: The container > > Class[Core_permissions] will propagate my refresh event > > debug: Class[Core_permissions]: The container Stage[main] will > > propagate my refresh event > > debug: /Schedule[never]: Skipping device resources because running on > > a host > > debug: /Schedule[weekly]: Skipping device resources because running on > > a host > > debug: /Schedule[puppet]: Skipping device resources because running on > > a host > > debug: Finishing transaction 549485440 > > debug: Storing state > > debug: Stored state in 0.04 seconds > > notice: Finished catalog run in 0.11 seconds > > debug: Value of ''preferred_serialization_format'' (pson) is invalid for > > report, using default (yaml) > > debug: report supports formats: b64_zlib_yaml marshal raw yaml; using > > yaml > > > > I am now receiving this issue again > > > > mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT > > undefined method `each'' for nil:NilClass > > Backtrace > > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:202:in > > `extended'' > > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in `each'' > > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:200:in > > `extended'' > > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > > `extend'' > > /opt/puppet/share/puppet-dashboard/lib/puppet/report.rb:114:in > > `extended'' > > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > > `extend'' > > /opt/puppet/share/puppet-dashboard/app/models/report.rb:107:in > > `create_from_yaml'' > > /opt/puppet/share/puppet-dashboard/app/models/report.rb:86:in > > `create_from_yaml_file'' > > If you are using ruby 1.9.1, it is known to be problematic: > http://docs.puppetlabs.com/guides/faq.html > > > Also it automatically added the node back to default, anyway to > > prevent that? > > Looks like there''s a background task automatically adding nodes. I > don''t know a good way around this issue. You can move the pe-* class > to another group but you will need to manually add nodes to that group > afterwards. > > There''s a cron job that calls a rake task that will automatically addnodes that it knows about to the default group. You will most likely need to A) move the offending classes out of the default group as Nan suggests, or B) disable the cron job and manually add new nodes to the appropriate groups, or C) write a new cron job/rake task that will only add the nodes you want. See /etc/cron.d/default-add-all-nodes on your PE console node. - Justin HTH,> > Nan > > -- > 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. > >-- 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.