Package: puppet
Version: 0.18.0-1
Severity: important
X-Debbugs-Cc: [EMAIL PROTECTED]

Hi Matt, everybody!

I have installed (on two different machines, with two different kernels, one a
freshly bootstrapped sid) puppet and experienced segvs if the manifest becomes
to large.

To reproduce, I have made a most trivial site.pp:

define test() {
        file { "/tmp/$name":
                source => "puppet://puppet/files/$name",
                mode => 0664, owner => root, group => root,
                backup => server
        }
}

filebucket { server:
        server => puppet
}

node default {
test{ 1 : }
test{ 2 : }
test{ 3 : }
test{ 4 : }
# ...

}


Depending on the numbers of "test" entries I either get 

| info: Statefile /var/lib/puppet/state/state.yaml does not exist
| info: Caching configuration at /etc/puppet/localconfig.yaml
| notice: Starting configuration run
| info: Statefile /var/lib/puppet/state/state.yaml does not exist
| *** glibc detected *** corrupted double-linked list: 0xb7e568b8 ***
| Aborted

or

| info: Caching configuration at /etc/puppet/localconfig.yaml
| notice: Starting configuration run
| /usr/lib/ruby/1.8/xmlrpc/client.rb:412:in `call': negative allocation size 
(or too big) (NoMemoryError)
|         from /usr/lib/ruby/1.8/puppet/networkclient.rb:64:in `describe'
|         from /usr/lib/ruby/1.8/puppet/client/proxy.rb:15:in `describe'
|         from /usr/lib/ruby/1.8/puppet/type/pfile/source.rb:41:in `describe'
|         from /usr/lib/ruby/1.8/puppet/type/pfile/source.rb:93:in `retrieve'
|         from /usr/lib/ruby/1.8/puppet/type/pfile/source.rb:92:in `retrieve'
|         from /usr/lib/ruby/1.8/puppet/type/pfile.rb:731:in `retrieve'
|         from /usr/lib/ruby/1.8/puppet/type.rb:1815:in `evaluate'
|         from /usr/lib/ruby/1.8/puppet/transaction.rb:44:in `apply'
|          ... 10 levels...
|         from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
|         from /usr/lib/ruby/1.8/puppet/client/master.rb:306:in `lock'
|         from /usr/lib/ruby/1.8/puppet/client/master.rb:349:in `run'
|         from /usr/sbin/puppetd:415
| *** glibc detected *** corrupted double-linked list: 0x0866e0e0 ***
| Aborted

or

| info: Caching configuration at /etc/puppet/localconfig.yaml
| notice: Starting configuration run
| /usr/lib/ruby/1.8/xmlrpc/client.rb:412: [BUG] Segmentation fault
| ruby 1.8.4 (2005-12-24) [i486-linux]
| 
| Aborted

Sometimes it even works.

The puppetmaster runs on sarge and using puppet on sarge as client also works
with any numer of "test" entries.

Regards, David

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-vserver-686
Locale: LANG=C, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)

Versions of packages puppet depends on:
ii  adduser                3.92              Add and remove users and groups
ii  facter                 1.3.3-1           a library for retrieving facts 
fro
ii  libopenssl-ruby        1.0.0+ruby1.8.2-1 OpenSSL interface for Ruby
ii  libxmlrpc-ruby         1.8.2-1           XML-RPC support for Ruby
ii  lsb-base               3.1-10            Linux Standard Base 3.1 init 
scrip
ii  ruby                   1.8.2-1           An interpreter of object-oriented 

Versions of packages puppet recommends:
ii  rdoc                          1.8.2-1    Generate documentation from ruby 
s

-- no debconf information

-- 
- hallo... wie gehts heute?
- *hust* gut *rotz* *keuch*
- gott sei dank kommunizieren wir über ein septisches medium ;)
 -- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15

Reply via email to