Hi again,
A couple of quick updates: - I upgraded my server and client to 2.6.6-rc1 (again from tmz's repo) and the problem still persists. - I run the master behind nginx and via unicorn. Quick revert to WEBrick showed the same problem. -Naresh V. On 2 March 2011 21:17, Naresh V <[email protected]> wrote: > Hi, > > I recently upgraded my puppet master and clients from 2.6.2 to 2.6.4. > Things were fine until today I tried introducing a new host to my > master for the first time: > > client: > > [root@db-us1 ~]# rpm -qa puppet > puppet-2.6.4-0.7.el5 > > > [root@db-us1 ~]# puppetd -t -v > warning: peer certificate won't be verified in this SSL session > warning: peer certificate won't be verified in this SSL session > err: Could not request certificate: Error 400 on SERVER: header too long > Exiting; failed to retrieve certificate and waitforcert is disabled > [root@db-us1 ~]# > > > master: > > #-(0)> rpm -qa | grep puppet > puppet-2.6.4-0.7.el5 > puppet-server-2.6.4-0.7.el5 > > Mar 2 14:26:29 puppet puppet-master[21312]: header too long > > #-(0)> puppetca -l > err: Could not call list: header too long > > > How can I fix this? > > > -Naresh V. > > P.S.: The RPMs are from tmz's repo. > -- 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.
