Yeah .. this seems to be exactly my problem. It would be nice if either the server or client could throw an exception to give a clue about the problem ..
I've spent last night debugging this problem and couldn't find any trace of errors .. On 5 avr, 05:18, Patrick <[email protected]> wrote: > On Apr 4, 2010, at 8:29 PM, h3 wrote: > > > > > > > I have a puppet master running on a Ubuntu Hardy. I have some other > > Ubuntu servers and clients ranging from hardy to karmic that works > > fine. > > > Now I've setuped a fresh Lucid Lynx install (10.04) and I can't get a > > certificate for it: > > > Client: > > >> sudo puppetd --waitforcert 60 --test > > >> info: Creating a new SSL key for h3-desktop > >> warning: peer certificate won't be verified in this SSL session > >> warning: peer certificate won't be verified in this SSL session > >> info: Creating a new SSL certificate request for h3-desktop > >> warning: peer certificate won't be verified in this SSL session > >> warning: peer certificate won't be verified in this SSL session > >> warning: peer certificate won't be verified in this SSL session > >> warning: peer certificate won't be verified in this SSL session > >> notice: Did not receive certificate > >> warning: peer certificate won't be verified in this SSL session > >> notice: Did not receive certificate > > > Server: > > >> h...@server:/tmp$ sudo puppetca --list > >> No certificates to sign > > Is the server version 0.24.x and the client is 0.25.x? 0.24 clients can > connect to 0.25 servers, but not the other way around. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
