Puppet users - Mar 2008 - puppet hanging with memory leak and high cpu

I''m using the following two package:

puppet-0.24.2-1.el5
puppet-server-0.24.2-1.el5


With the following class PuppetMaster will hang consuming 100% and
begin consuming memory at the rate of 1MB/second.  This happens soon
as a puppet client tries to sync:

Mar 24 17:44:43 aus-vm02-s06 puppetd[5835]: Starting Puppet client
version 0.24.2
Mar 24 17:44:45 aus-vm02-s06 puppetd[5835]: Starting catalog run

and it never finishes....

here is the class:

class jdk {

        file { "/usr/local/src": ensure => directory }

        file { "/usr/local/src/jdk-1_5_0_15-linux-amd64.rpm":
                        source => "puppet:///files/jdk-1_5_0_15-linux-
amd64.rpm"
        }

        package { "jdk":
                        ensure   => installed,
                        provider => rpm,
                        source   => "/usr/local/src/jdk-1_5_0_15-linux-
amd64.rpm"
        }

}


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, 2008-03-24 at 15:49 -0700, Brent Meshier wrote:
> I''m using the following two package:
> 
> puppet-0.24.2-1.el5
> puppet-server-0.24.2-1.el5
> 
There might be some underlying problem, but the puppet: protocol isn''t
very good for tranferring large files (and the JDK rpm''s are huge) You
can expect the server and the client needing 1-2 times the files size
for transfers.

If you stick the JDK RPM on a webserver somewhere, you can simplify your
manifest to 

        package { "jdk":
               ensure   => installed,
               provider => rpm,
               source   =>
"http://server/path/jdk-1_5_0_15-linux-amd64.rpm"
        }

If you have more than just this one RPM, it might be worth setting up a
local yum repo and enabling that on the clients.

David



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

How do I get large files on to the client if I can''t use puppet://
The file {} method doesn''t allow you to use the http protocol.  I have
many .tar.gz files I need to get on to the client, untar and
installed.

--Brent
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 25 March 2008, Brent Meshier wrote:
> How do I get large files on to the client if I can''t use puppet://
> The file {} method doesn''t allow you to use the http protocol.  I
have
> many .tar.gz files I need to get on to the client, untar and
> installed.
The usual way to distribute this stuff is either rsyncing (piecemeal or a 
whole tree) or mounting a remote file system like nfs).


AFAICT, puppet will grow http(s) file transfer support when the REST 
transition is completed. As usual, sending $$ to Luke may improve priorities.


Regards, DavidS
- -- 
The primary freedom of open source is not the freedom from cost, but the free-
dom to shape software to do what you want. This freedom is /never/ exercised
without cost, but is available /at all/ only by accepting the very different
costs associated with open source, costs not in money, but in time and effort.
- -- http://www.schierer.org/~luke/log/20070710-1129/on-forks-and-forking
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH6P60/Pp1N6Uzh0URAp7GAJ0Spxv1vdXVPAsGlEoPOZoTApTtFgCdEPDv
D44/Oq0O3aleU8WMxoumWVo=vlhj
-----END PGP SIGNATURE-----

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

On Mon, 2008-03-24 at 20:01 -0700, Brent Meshier wrote:
> How do I get large files on to the client if I can''t use puppet://
> The file {} method doesn''t allow you to use the http protocol.
In the case of rpm you''re in luck since rpm has support for ftp and
http
built in.
> I have
> many .tar.gz files I need to get on to the client, untar and
> installed.
Package them as RPM''s ;) (I am only half joking) Though generally,
using
an exec to run rsync or similar is the simplest way to put large files
on the client.

Just to be clear: the problem with the puppet protocol and large files
comes from using XML-RPC, where the whole payload is wrapped in XML;
this is done in memory, and not streamed. Luke is addressing that with
the REST work, which will remove all that gnarly XML-RPC overhead.

David



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---