Splendid! The time was off by months. Apparently FreeBSD's ntpd doesn't handle this to well (it just quits) so an initial "ntpdate -b" got it back on track, and after that both nptd and puppet works fine.
I think this i a trap easy to fall in to, so I'll make a suggestion to the developers to add a hint of this in the error-message it throws. It should be fairly easy to do (I say not nowing much about Ruby at all). As for the segfault, I will try to reproduce it and single it in before submitting any bugreport. Thanks Jeff. /Freddie On Sep 21, 6:55 pm, Jeff McCune <j...@puppetlabs.com> wrote: > On Tue, Sep 21, 2010 at 7:35 AM, FreddieB <freddie.bra...@gmail.com> wrote: > > [snip[ > > >> debug: OpenSSL: Error(9): certificate is not yet valid > >> debug: OpenSSL: Cert: /CN=deploy01 > >> /usr/local/lib/ruby/site_ruby/1.8/puppet/network/http_pool.rb:68: > >> [BUG] Bus Error > >> ruby 1.8.7 (2009-12-24 patchlevel 248) [amd64-freebsd8] > > I see two possible problem. "certificate is not yet valid" usually > indicates the agent's clock is out of sync with the master's clock. > > However, you're also getting a segfault which is clearly a bug and > should never happen. This segfault is happening on the agent and > looks to be a bug in the ruby package you have. I'm not sure the > exact solution off the top of my head, but I suspect other FreeBSD > puppet users have run into this. I suggest searching the usual > suspects; the puppet ticket tracker > athttp://projects.puppetlabs.com/projects/puppet/issuesand google. > > Hope this helps, > -- > Jeff McCunehttp://www.puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
