Using RPMs for el4 (0.22.3). Been trying to get templates to work, but have found problems. I created a very small template, and this works well, variables substitute, great. I tried a much larger one (an httpd.conf), and puppetmaster crashed. the remote puppetd first reported an SSL certificate problem, then on seconds run, "cannot connect to server." Hacked the template down to about 3k... puppetmaster did not crash, but the resulting file on the client was badly truncated. Are there known problems either with Puppet 0.22.3 on templating, or on Ruby 1.8.1 as shipped by Red Hat (actually Centos)? Thanks -Alan -- Alan Sparks, UNIX/Linux Systems Integration and Administration <asparks@doublesparks.net>
On May 2, 2007, at 2:42 PM, Alan Sparks wrote:> Using RPMs for el4 (0.22.3). Been trying to get templates to work, > but > have found problems. > I created a very small template, and this works well, variables > substitute, great. > I tried a much larger one (an httpd.conf), and puppetmaster crashed. > the remote puppetd first reported an SSL certificate problem, then on > seconds run, "cannot connect to server." > Hacked the template down to about 3k... puppetmaster did not crash, > but > the resulting file on the client was badly truncated. > > Are there known problems either with Puppet 0.22.3 on templating, > or on > Ruby 1.8.1 as shipped by Red Hat (actually Centos)?None that I know of, although Ruby 1.8.1 is wicked-old and should be avoided if possible. If you''ve got a 3000k apache.conf file, though, you''re going to have serious trouble managing it. I *highly* recommend splitting it into multiple files, like the Debian folks do (with a sites-available directory containing each virtual host, and a sites-enabled directory linking the hosts in with the right order). Not that that excuses the server crashing on large templates, mind you. Can you run the server with -v --trace and post a stack trace? -- Due to circumstances beyond your control, you are master of your fate and captain of your soul. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies wrote:> On May 2, 2007, at 2:42 PM, Alan Sparks wrote: > > > If you''ve got a 3000k apache.conf file, though, you''re going to have > serious trouble managing it. I *highly* recommend splitting it into > multiple files, like the Debian folks do (with a sites-available > directory containing each virtual host, and a sites-enabled directory > linking the hosts in with the right order). > >Srry, typo. 3000 /line/.> Not that that excuses the server crashing on large templates, mind > you. Can you run the server with -v --trace and post a stack trace? > >I will do this. -Alan -- Alan Sparks, UNIX/Linux Systems Integration and Administration <asparks@doublesparks.net>
Alan, Check this thread in the archives "[Puppet-users] Is there a limit on the size of a template?" http://mail.madstop.com/pipermail/puppet-users/2007-February/001469.html Basically, it looks like you need to upgrade to a newer version of ruby. Trevor On 5/2/07, Alan Sparks <asparks@doublesparks.net> wrote:> Luke Kanies wrote: > > On May 2, 2007, at 2:42 PM, Alan Sparks wrote: > > > > > > If you''ve got a 3000k apache.conf file, though, you''re going to have > > serious trouble managing it. I *highly* recommend splitting it into > > multiple files, like the Debian folks do (with a sites-available > > directory containing each virtual host, and a sites-enabled directory > > linking the hosts in with the right order). > > > > > Srry, typo. 3000 /line/. > > > > Not that that excuses the server crashing on large templates, mind > > you. Can you run the server with -v --trace and post a stack trace? > > > > > I will do this. > -Alan > > -- > Alan Sparks, UNIX/Linux Systems Integration and Administration > <asparks@doublesparks.net> > > _______________________________________________ > Puppet-users mailing list > Puppet-users@madstop.com > https://mail.madstop.com/mailman/listinfo/puppet-users >
Just a followup on this. Tried same thing with Ruby(-libs) 1.8.5 from CentOS testing repository. This does not truncate the files in question (an httpd.conf) file. The interesting part was the file would be delivered truncated to the client (at about 3790 bytes), unless the template itself was "too big", in which case the file delivered was zero bytes, and puppetmasterd crashed. Seemingly, the templating stuff is badly broken in 1.8.1, at least the x86_64 versions, for RHEL4 and CentOS 4. -Alan Alan Sparks wrote:> Luke Kanies wrote: > >> On May 2, 2007, at 2:42 PM, Alan Sparks wrote: >> >> >> If you''ve got a 3000k apache.conf file, though, you''re going to have >> serious trouble managing it. I *highly* recommend splitting it into >> multiple files, like the Debian folks do (with a sites-available >> directory containing each virtual host, and a sites-enabled directory >> linking the hosts in with the right order). >> >> >> > Srry, typo. 3000 /line/. > > > >> Not that that excuses the server crashing on large templates, mind >> you. Can you run the server with -v --trace and post a stack trace? >> >> >> > I will do this. > -Alan > >-- Alan Sparks, UNIX/Linux Systems Integration and Administration <asparks@doublesparks.net>
On May 14, 2007, at 2:46 PM, Alan Sparks wrote:> Just a followup on this. Tried same thing with Ruby(-libs) 1.8.5 from > CentOS testing repository. This does not truncate the files in > question > (an httpd.conf) file. The interesting part was the file would be > delivered truncated to the client (at about 3790 bytes), unless the > template itself was "too big", in which case the file delivered was > zero > bytes, and puppetmasterd crashed. > > Seemingly, the templating stuff is badly broken in 1.8.1, at least the > x86_64 versions, for RHEL4 and CentOS 4.Ok, thanks for letting us know. Just another good reason not to use 1.8.1. -- The most overlooked advantage to owning a computer is that if they foul up there''s no law against wacking them around a little. -- Joe Martin --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
On Mon, May 14, 2007 at 01:46:48PM -0600, Alan Sparks wrote:> Just a followup on this. Tried same thing with Ruby(-libs) 1.8.5 from > CentOS testing repository. This does not truncate the files in question > (an httpd.conf) file. The interesting part was the file would be > delivered truncated to the client (at about 3790 bytes), unless the > template itself was "too big", in which case the file delivered was zero > bytes, and puppetmasterd crashed. > > Seemingly, the templating stuff is badly broken in 1.8.1, at least the > x86_64 versions, for RHEL4 and CentOS 4.It would be nice if you can fill a bug at RedHat''s bugzilla for it so it can get fixed. Thinking about it should we have a page in the wiki about known problems that are caused by ruby, some other lib, etc. and not puppet? Kostas
Seemingly Similar Threads
- Jan 16 17:49:33 murowall kernel: Shorewall:loc2net:CONTINUE:IN=eth0 OUT=eth2 SRC Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth2
- kernel: Page has mapping still set - continues
- Acrobat Reader version for CentOS 3?
- Broken mirrors
- Setting variables for a "group of nodes" - how to approach?