On Thursday, December 6, 2012 9:28:29 AM UTC-6, Luca Gioppo wrote: > > Ruby version 1.8.7 on both master and agent. > > But on the agent I get: > Error: Could not retrieve catalog from remote server: Error 400 on SERVER: > can't instantiate uninitialized class > Debug: Using cached catalog for jbossm.cortile.cloudlabcsi.local > Using cached catalog > > So the problem should be in the puppet master and not in the agent. > > That's fundamentally different from what you wrote before. Did the behavior indeed change between your posts? Are we to take the second as the behavior you are seeing now? Is it consistent?
Moreover Google tells me that the reported error message indeed does not appear in Puppet's code base, but that it does appear in the code of at least a couple of different Ruby implementations. Given that yours is the first report I have seen of Puppet emitting that message, I am inclined to suspect that the bug is in Ruby code that does not belong to Puppet itself -- it could be in a custom type or provider, a Ruby DSL manifest, or a template. As for debugging, you can use the --debug flag for the master, too. Even before that, however, you should look in its logs; any details about what may be going wrong on the master will be reported there, not in the agents' logs. Also, you should try to find the minimal set of modules / classes that need to be assigned to the node (in its node block or by your ENC) to trigger the error. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/IIRoPN-8TxEJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
