Issue #20559 has been updated by David Gordon. File disclaim.txt added
Thanks. I think this one is explained now. I raised #20573 to cover the missing classes. I think my site.pp is ok, but will check in the morning. -----Original Message----- From: [email protected] [[email protected]] Sent: Monday, May 06, 2013 08:14 PM W. Europe Standard Time To: Gordon, David; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: [Puppet - Bug #20559] Upgrade to Puppet 3.2.0-0.1rc1 failed Issue #20559 has been updated by Charlie Sharpsteen. David Gordon wrote: I’ve taken out the timeout and things start now, so all good there. Good to hear. This is definitely a duplicate of #20447 . Hopefully the the #16568 fix will deal with my other problem – should know by tomorrow. Please let us know if the problem persists, as I mentioned your missing classes could also be caused by #15106 . I’m hoping to dig into that bug this week and any additional data would be very helpful. ________________________________ Bug #20559: Upgrade to Puppet 3.2.0-0.1rc1 failed * Author: David Gordon * Status: Duplicate * Priority: Normal * Assignee: Charlie Sharpsteen * Category: * Target version: * Affected Puppet version: * Keywords: daemon scheduler * Branch: Hi, I have the following packages install on my RHEL 2.6.32-220.13.1.el6.x86_64 machine: puppet-server-3.1.1-1.el6.noarch puppetdb-1.2.0-1.el6.noarch puppet-dashboard-1.2.23-1.el6.noarch puppetdb-terminus-1.2.0-1.el6.noarch puppet-3.1.1-1.el6.noarch Ruby version is: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] I tried to upgrade to 3.2.0-0.1rc1 to resolve a mysterious problem where I get sporadic 400 errors “Class not found”. Apart from these, 3.1.1 work ok. Upgrading puppet and puppet-server packages worked, but the puppetmaster dies at startup. The service starts with ‘OK’ but then service status states ‘dead but pidfile exists. Running puppetmaster —no-daemonize —debug in the foreground also exitted with no errors logged. Doing the same with strace showed 'bad file descriptor’. Downgraded back to 3.1.1 and it works again. ________________________________ You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account ---------------------------------------- Bug #20559: Upgrade to Puppet 3.2.0-0.1rc1 failed https://projects.puppetlabs.com/issues/20559#change-90543 * Author: David Gordon * Status: Duplicate * Priority: Normal * Assignee: Charlie Sharpsteen * Category: * Target version: * Affected Puppet version: * Keywords: daemon scheduler * Branch: ---------------------------------------- Hi, I have the following packages install on my RHEL 2.6.32-220.13.1.el6.x86_64 machine: puppet-server-3.1.1-1.el6.noarch puppetdb-1.2.0-1.el6.noarch puppet-dashboard-1.2.23-1.el6.noarch puppetdb-terminus-1.2.0-1.el6.noarch puppet-3.1.1-1.el6.noarch Ruby version is: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] I tried to upgrade to 3.2.0-0.1rc1 to resolve a mysterious problem where I get sporadic 400 errors "Class not found". Apart from these, 3.1.1 work ok. Upgrading puppet and puppet-server packages worked, but the puppetmaster dies at startup. The service starts with 'OK' but then service status states 'dead but pidfile exists. Running puppetmaster --no-daemonize --debug in the foreground also exitted with no errors logged. Doing the same with strace showed 'bad file descriptor'. Downgraded back to 3.1.1 and it works again. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
