I have run into this error on a few nodes. The only workaround I've found so far is to delete the host out of the MySQL table. Is there anything I can do to debug?
Running CentOS 6.3 and Puppet 3.0.1 on master. Broken nodes are mostly running 3.0.0 and 3.0.1, but a mixture of CentOS 5.8 and 6.3. All 64 bit. On Thursday, 25 October 2012 19:47:02 UTC+1, Jeff McCune wrote: > > On Thu, Oct 25, 2012 at 11:26 AM, Fabrice Bacchella > <fbacc...@spamcop.net<javascript:> > > wrote: > >> >> Le 25 oct. 2012 à 18:40, Jeff McCune <je...@puppetlabs.com <javascript:>> >> a écrit : >> >> On Thu, Oct 25, 2012 at 4:42 AM, Fabrice Bacchella >> <fbacc...@spamcop.net<javascript:> >> > wrote: >> >>> This patch does something magic. A broken node (with allocator undefined >>> for Proc) is working when I apply your patch to the puppet master and >>> restart it. I can then remove it and the node will keep working. >>> >> >> Did you restart the puppet master after removing the patch? I expect the >> error to show back up once the patch is backed out and the master process >> is restarted. >> >> >> Yes, I restarted the puppet master each and many times. I think it gets >> the configuration clean, or something like that, because broken nodes are >> now working well, I just checked. >> >> > Weird. Must be a heisenbug. ;) Resolved as soon as we started studying > it... > > If you run into it again, please let me know. I'll still try and > reproduce the issue with the JSON file you emailed me. > > -Jeff > -- 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/-/K5CVrru5KAkJ. 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.
