On Wednesday, July 17, 2013 5:31:47 PM UTC-5, Forrie wrote: > > I do not have separate Puppet installs. At the moment, it's been > installed via the Gem, so the master and agent are coming from the same > code, running on the original host (it was not rebuilt). It is running > under Passenger/Apache, presently. > > Then I'm sorry, I can't follow this. The description of the problem is either too inconsistent or too fragmented.
Fresh installs of Puppet are not known to exhibit the problem you describe, so the issue must have arisen through the upgrade. Since you're using gem, perhaps you have a compatibility problem among the set of gems currently installed. Or back to basics: you DID restart apache/passenger after upgrading the master, right? If I am to have any hope of being able to do anything further for you, however, then I need a detailed timeline of what was done to Puppet on your site, starting from "everything is running great on Puppet 2.7 / CentOS 5" (or whatever), including which systems were (re)built, what OS and Puppet versions were used, and what problems were observed on which systems. John -- 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 puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
