Adam, can you vote or watch that bug please so we know other people are being affected by it?
Thanks Nigel, done.
It's actually suggesting that you edit the puppet source code. Obviously this is not a long term solution, but it would be very helpful if you had success doing this and could let us know in the ticket.
Ah, of course - I tried this and it did solve the problem for me.
Are you actually using webrick as the puppet master? We do highly suggest that people set up Passenger or Mongrel with Apache for production environments, as webrick hits scalability limits rather quickly.
Yes I'm using webrick. I only have a small number of servers hanging off this puppetmaster with little chance of expansion so there are no scaling issues to worry about just yet.
But now it's all working fine, so thanks for your help! Cheers, Adam. -- 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.
