HP-UX Puppet Agent
505 views
Skip to first unread message
Michael Glatz
Apr 3, 2012, 4:21:46 PM4/3/12
to Puppet Users
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
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
Michael Glatz
Apr 5, 2012, 10:33:41 AM4/5/12
to Puppet Users
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
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
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
Nan Liu
Apr 5, 2012, 10:45:01 AM4/5/12
to puppet...@googlegroups.com
On Thu, Apr 5, 2012 at 2:33 PM, Michael Glatz <mfg...@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
> 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
Michael Glatz
Apr 5, 2012, 10:57:30 AM4/5/12
to Puppet Users
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
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
mporting report report-14137-1.yaml at 2012-04-05 10:49 EDT
prevent that?
On Apr 5, 10:45 am, Nan Liu <n...@puppetlabs.com> wrote:
running into some issues
It cataloged correctly and even ran the test class I created
notice: Starting Puppet client version 2.7.12
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'
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
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
a host
debug: /Schedule[monthly]: Skipping device resources because running
on a host
debug: /Schedule[hourly]: Skipping device resources because running on
a host
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
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: Storing state
debug: Stored state in 0.04 seconds
notice: Finished catalog run in 0.11 seconds
debug: Stored state in 0.04 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
report, using default (yaml)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
yaml
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
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'
prevent that?
On Apr 5, 10:45 am, Nan Liu <n...@puppetlabs.com> wrote:
Nan Liu
Apr 5, 2012, 11:22:56 AM4/5/12
to puppet...@googlegroups.com
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
Justin Stoller
Apr 5, 2012, 11:32:15 AM4/5/12
to puppet...@googlegroups.com
There's a cron job that calls a rake task that will automatically add nodes 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
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...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Rick Copley
Mar 18, 2014, 11:15:08 AM3/18/14
to puppet...@googlegroups.com
Hi, has anyone had success getting a puppet agent to run in HP-UX 11.31?
Corentin Blanche
Mar 23, 2015, 11:09:59 AM3/23/15
to puppet...@googlegroups.com
Hi everyone,
It would be very nice to have any feedback on how to have a functionnal PE Agent on HP-UX as the one from Michael Glatz:
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
Thank you for any replies :)
Have a pretty nice day.
Kindest Regards,
Johan De Wit
Mar 23, 2015, 4:25:03 PM3/23/15
to puppet...@googlegroups.com
Hi Corentin,
The only option we have is installing from gems.
This is I believe possible as soon as you have ruby and rubygems installed.
Keep in mind that the documentation you will find (like the one from Martin Alfke, wo did a successful install of puppet 2.x) installed the 2.x version of puppet.
You are looking to get the 3.7.4 version installed, and a recent version of facter is also needed.
If someone has dome experience installing a 3.x series of puppet, this would be great to hear about it.
Grts
Johan
The only option we have is installing from gems.
This is I believe possible as soon as you have ruby and rubygems installed.
Keep in mind that the documentation you will find (like the one from Martin Alfke, wo did a successful install of puppet 2.x) installed the 2.x version of puppet.
You are looking to get the 3.7.4 version installed, and a recent version of facter is also needed.
If someone has dome experience installing a 3.x series of puppet, this would be great to hear about it.
Grts
Johan
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/58123b60-84da-4ce3-af47-b8a273ef91d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
-- Johan De Wit Open Source Consultant Red Hat Certified Engineer (805008667232363) Puppet Certified Professional 2013/2014 (PCP0000006) Puppet Certified Intstructor blog : http://johan.koewacht.net/ _________________________________________________________ Open-Future Phone +32 (0)2/255 70 70 Zavelstraat 72 Fax +32 (0)2/255 70 71 3071 KORTENBERG Mobile +32 (0)474/42 40 73 BELGIUM http://www.open-future.be _________________________________________________________
Upcoming Events:
Puppet Fundamentals | http://www.open-future.be/puppet-fundamentals-training-16th-till-18th-march
Puppet Architect | http://www.open-future.be/puppet-architect-training-19th-till-20th-march
Puppet Practitioner | http://www.open-future.be/puppet-practitioner-training-14th-till-16th-april
Linux Training | http://www.open-future.be/linux-training-20th-till-24th-april
Bacula Administrator 1 | http://www.open-future.be/bacula-administrator-i-training-28th-till-30th-april
Zabbix Certified Specialist | http://www.open-future.be/zabbix-certified-specialist-training-4th-till-6th-may
Zabbix Certified Professional | http://www.open-future.be/zabbix-certified-professional-training-7th-till-8th-may
Subscribe to our newsletter: http://eepurl.com/BUG8H
Reply all
Reply to author
Forward
0 new messages