Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13] puppet 3.6.0 Mac OSX 10.9 Mavericks filesystems: HFS+ Installed puppet via gem then uninstalled gem and installed with dmg. Issue showed up randomly on some systems that were updated after 3.4.2 Issue does not show up on RHEL or Ubuntu Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Had it happen again today.. Here from /var/log/messages on the client: Jun 2 15:37:07 host puppet-agent[10513]: Unable to fetch my node definition, but the agent run will continue: Jun 2 15:37:07 host puppet-agent[10513]: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Could not evaluate: Could not retrieve file metadata for puppet://puppet/pluginfacts: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Wrapped exception: Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Could not evaluate: Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Wrapped exception: Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Jun 2 15:37:08 host puppet-agent[10513]: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Jun 2 15:37:08 host puppet-agent[10513]: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked I don't know why my cert is jacked up, but there's the Log message again. Add Comment
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Brian Wilkins It looks like the agent's cert was revoked on the server side. You can confirm that by looking at the list of revoked certs (by serial number) on the master: # openssl crl -in `puppet master --configprint cacrl` -noout -text ... Revoked Certificates: Serial Number: 02 Revocation Date: Jun 2 20:15:12 2014 GMT More importantly, are you able to run the daemonized agent with --trace? Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Oddly it doesn't show any on the master, but thats a side issue Anyways, so I tried it again. To get the error to go away, I removed pluginsync = true from my puppet.conf on the agent. The error didn't happen anymore. I had the agent running as a service for several days. I had to turn it off to debug some erb I am writing so I could run the agent on demand. Starting seeing these errors when I would run the agent on demand at the command line. Looked at my puppet.conf, removed pluginsync = true. The errors stopped. I just added back in pluginsync = true and the errors don't happen again. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] puppet 3.6.0 Red Hat Enterprise Linux Server release 6.5 (Santiago) filesystems: /dev/mapper/obvg-rootvol on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/mapper/obvg-homevol on /home type ext4 (rw) /dev/mapper/obvg-tmpvol on /tmp type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) Installed puppet via puppetlabs-repo (RPM) Issue showed up randomly one day, puppet had been running for a few days on VM Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log mike jeski Rudy McComb Brian Wilkins Tamas Szasz Ronald Valente The error definitely originates on the agent side, so ignore my earlier comments about adding --debug and --trace to your puppet master. Part of the confusion is that if the puppet reports setting includes log, then the log messages from the client's report will be written into the master's syslog, as happened here: May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//hostname/Puppet) Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation This makes it appear as though the error came from the master, when in reality it came from hostname. Could you please update your comments to include the following information about your puppet agents only: ruby version puppet version linux distro(s), e.g. Ubuntu 12.04 LTS type of filesystems relevant to puppet, e.g. mount -l how did you install puppet, e.g. rpm, apt, yum, gem, source, etc are there multiple versions of puppet installed, e.g. as package (if so where from), as a gem, as tarball did the issue show up recently after updating puppet? If so, what version were you running previously? How did you update? using puppet itself, package manager, gem update? if you are able to reproduce the problem with a daemonized agent, can you add --trace to the script that launches puppet, e.g. on Ubuntu, edit /etc/default/puppet and restart the puppet service: DAEMON_OPTS=--trace
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log I am using Apache httpd with mod_passenger. I originally commented on this error because I saw it all weekend. I am NOT seeing it currently. I do not know why. I had to make the suggested configuration change, but then I took it out and removed the `puppet` entry from my `/etc/hosts`. I have my puppetmaster defined in the server config section of my `puppet.conf`. So I shouldn't have needed that setting. It is a very odd error. One thing of note is the puppet agent and puppetmaster are running on VMWare VMs. I am not sure if that makes a difference. This is my ruby version: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]. I am running puppet 3.6 I would get you the trace, but I don't think it is helpful because I am not currently experiencing the error. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title
Rudy McComb commented on an issue
Re: Could not autoload puppet /util /instrumentation /listeners /log
Im on OSX 10.9.3. ruby --version ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13]
from agent cabimd010855:~ madmin$ sudo puppet agent -t --test --trace Password: Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb Info: Loading facts in /var/lib/puppet/lib/facter/esx_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/git_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/has_compiler.rb Info: Loading facts in /var/lib/puppet/lib/facter/httpd_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_charge_percent.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_charging.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_cycles.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_health.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_current_user.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_encryption_enabled.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_flash_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_has_wireless.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_java_vendor.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_java_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_laptop.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_memory_in_gb.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_timezone.rb Info: Loading facts in /var/lib/puppet/lib/facter/mysql_client_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mysql_server_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/operatingsystemversion.rb Info: Loading facts in /var/lib/puppet/lib/facter/os_maj_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/php_rpm_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/php_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/printers.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_httpd.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_mysql.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_php.rb Info: Loading facts in /var/lib/puppet/lib/facter/rvm_installed.rb Info: Loading facts in /var/lib/puppet/lib/facter/rvm_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/user_online.rb Info: Loading facts in /var/lib/puppet/lib/facter/vmwaretools_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/warranty.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_productkey.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_sid.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_systemtype.rb Could not retrieve fact='mac_battery_charge_percent', resolution='anonymous': invalid value for Float(): Could not retrieve fact='mac_battery_charge_percent', resolution='anonymous': invalid value for Float(): sed: 1: 1 {p;q}
: extra characters at the end of q command Info: Caching catalog for cabimd010855.harborfreight.com Info: Applying configuration version '1401293317' Notice: /Stage[main]/Macmodule::Clientconfig/Exec[display msg at login screen]/returns: executed successfully Notice: /Stage[main]/Macmodule::Clientconfig/Exec[display sysinfo at login screen]/returns: executed successfully Notice: Finished catalog run in 13.55 seconds
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Andy Parker commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Rudy McComb, yes that is consistent with what we have seen from others. I think Joshua Cooper forgot about that wrinkle in the whole thing. The error only seems to come up after the agent has run a few times in daemon mode. In our investigation we found that the mtime on some files appeared to change and that caused it to try to reload the files. We were never able to determine why the mtime was changing, however. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Puppetmaster is Ubuntu 12.04LTS and 3.5.1 for Puppet. # ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Joshua Cooper, I added the --trace for passenger and syslog is still reporting the same error with no more information May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com//File[/var/lib/puppet/lib]) Failed to generate additional resources using 'eval_generate': undefined method `exist?' for Puppet::FileSystem:Module May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com/Puppet) Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com/Puppet) Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title
Joshua Cooper commented on an issue
Re: Could not autoload puppet /util /instrumentation /listeners /log
mike jeski Rudy McComb Brian Wilkins Tamas Szasz Ronald Valente we are having difficulty reproducing this issue, and could really use your help trying to track this down.
Could you include the output from ruby --version? When you see the error is it always on the agent, master or both? Note that sometimes the agent will report an error 400, indicating that the error originated on the master. In that case, we only care about the master side error. If agent, can you run with puppet agent --test --trace and include the full stack trace in your comments above? If master, are you using webrick or passenger? If webrick, can you append --trace} to the arguments used to invoke the master. Exactly how depends on your platform. For example, on Centos you can edit {{/etc/sysconfig/puppetmaster to add:
PUPPETMASTER_EXTRA_OPTS=--trace
Then restart the master. You should see stack traces written to syslog, e.g. /var/log/messages.
If passenger, can you add --trace to the config.ru used to invoke puppet. For example, on Debian, look in /usr/share/puppet/rack/puppetmasterd/config.ru, and add these lines:
ARGV --trace
Next restart apache, e.g. service apache2 restart. Stack traces should be written into syslog, e.g.
May 27 22:35:30 puppetmaster puppet-master[3650]: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type ... at /etc/puppet/manifests/site.pp:11 on node ...
May 27 22:35:30 puppetmaster puppet-master[3650]: /usr/lib/ruby/vendor_ruby/puppet/resource.rb:220:in `initialize'
Finally, does the error occur when the master is processing multiple concurrent requests? Or can you reproduce with a single agent?
Add Comment
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log upgraded to Puppet 3.6.0 issue still exists: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log same issue here with 3.6.1 on Ubuntu 12.04.4 and Debian Squeeze Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Same issue here with Puppet version 3.6.0 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log This is a similar to an issue on 10.9.2 OSX, happens at random. This error occurs even though the run completed successfully. Level Resource message err Puppet Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation err Puppet Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation info Puppet Redefining component in Puppet::Type err /File[/var/lib/puppet/lib] Failed to generate additional resources using 'eval_generate': undefined method `exist?' for Puppet::FileSystem:Module info Puppet Retrieving plugin Nothing to show Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log So to work around this issue, I downgraded to 3.4.0. However, I gave 3.5.0 a try this week and this issue is back. Affecting Ubuntu 12.04 and Debian 6.0 boxes running ext4 filesystems. — This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Andrew Parker commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Ronald Valente, are you seeing this issue on 3.4.3? If so, could you provide any information about when it occurs, the system it is running on (OS, filesystem, etc), the puppet version, and ruby version? Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log See also PUP-1745 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Ronald Valente commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log OS: Ubuntu 12.04.04 LTS FS: ext4/lvm Ruby: 1.8.7 (only because puppet-common still depends on ruby1.8 for precise even though it ships with 1.9.3) ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] puppet --version 3.4.3 Also Note: A force of a puppet run will complete without error. (See manual run below) puppet agent --test Info: Applying configuration version '1392948172' Notice: Finished catalog run in 16.18 seconds Changes: Events: Resources: Total: 253 Time: Filebucket: 0.00 Vcsrepo: 0.00 Schedule: 0.00 Anchor: 0.00 Group: 0.00 Ssh authorized key: 0.00 User: 0.01 Exec: 0.86 Augeas: 0.92 Service: 1.08 Last run: 1393002908 Total: 15.73 Config retrieval: 2.78 File: 2.79 Package: 7.27 Version: Config: 1392948172 Puppet: 3.4.3 Also Note2:This is only happening on one of my nodes. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Ronald Valente commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Anyone seeing a regression in 3.4.3 regarding this issue? (err): Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log ahh, thanks Nick that got it. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title mike jeski commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log I still see this issue on nodes running ubuntu 12.04 and Debian 6.0.8. fiddling with the rb.log does nothing. ext4 filesystems. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Nick Walker commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log mike jeski You said you tried fiddling with rb.log. Have you tried applying the change described in this PR? https://github.com/jpartlow/puppet/commit/1004eaea5cd5fcadcd94709c5a4d314e3f297cef Also what version of puppet are you running? The PR above was merged in Puppet 3.4.2. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title
Joshua Partlow commented on an issue
Re: Could not autoload puppet /util /instrumentation /listeners /log
So the steps to reproduce a failure in the lib/puppet/util/instrumentation/listeners/log.rb autoloading are as follows:
With a running master, set up a non-daemonized agent to run and note it's PID. Then `touch puppet/util/instrumentation/listeners/log.rb`, and then issue a `kill -s SIGUSR1 {agent.pid}
` so that the agent does another run. This should fail with:
Error: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in P
uppet::Util::Instrumentation
Error: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Lo
g is already defined in Puppet::Util::Instrumentation
/home/jpartlow/work/puppet/lib/puppet/agent.rb:84:in `exit': no implicit conversion from nil to intege
r (TypeError)
from /home/jpartlow/work/puppet/lib/puppet/agent.rb:84:in `block in run_in_fork'
With the patched code, you should be able to verify that nsec changes are not being checked as follows. Assuming you have an ext4 filesystem which notes nsecs, kill and restart the puppet agent. You can then touch just the nsecs of the file, using `stat --format --mtime: %y' to see the full timestamp, and `touch -t MMDDHHMM.SS` to truncate it to just the current seconds. Then pinging the agent to rerun with a SIGUSR1 should not fail, as nsecs should be ignored by the patched puppet agent.
Add Comment
Puppet / PUP-724
Could not autoload puppet /util /instrumentation /listeners /log
This message was sent by
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Merged in commit 917cc40 to be released in 3.5.0 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log Change By: Joshua Partlow Fix Version/s: 3.5.0 Fix Version/s: 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log We discussed this for a while in hipchat, and consensus was to retarget for 3.4.2, which we hope to release Monday, and then merge to PE 3.2.x Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Cherry-picked to puppet/stable in 98e9219 Merged to pe-puppet/3.2.x in 5af6e12 Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Kylo Ginsberg commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Comments from HC on how to do FR: let's see, you could start a daemonized puppet agent, touch the instrumentation log file mentioned and see it blow up, then restart and touch just changing nsecs and see it not blow up...I think. I might be missing some steps. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log Change By: Michelle Johansen Sprint: Week2013-11-26to2013-12-4,Week2013-12-04to2013-12-11,Week2013-12-11to2013-12-18,Week2013-12-19to2014-1-2 ,Week2014-1-8to2014-1-15 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Just waiting to hear whether the patch worked for the customer. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Michelle Johansen updated an issue Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log Change By: Michelle Johansen Reporter: zendesk.jira NickWalker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Partlow commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log I accidentally tried updating this ticket via email; don't know if that will come through or not. Anyway; I updated pp-2121 with a little patch to test only integer secs. If this fixes the customer's issues, I will put up the PR for inclusion in Puppet. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
