Hi, has anyone had success getting a puppet agent to run in HP-UX 11.31? On Thursday, April 5, 2012 11:32:15 AM UTC-4, Justin Stoller wrote:
> > > On Thu, Apr 5, 2012 at 8:22 AM, Nan Liu <[email protected] <javascript:> > > wrote: > >> On Thu, Apr 5, 2012 at 2:57 PM, Michael Glatz >> <[email protected]<javascript:>> >> 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 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 > > > 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 [email protected]<javascript:> >> . >> To unsubscribe from this group, send email to >> [email protected] <javascript:>. >> 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/b9b888b3-e7f5-41af-9985-7888e30d6304%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
