thr3ads.net - Puppet users - [Puppet Users] client won''t use remote file bucket [Oct 2010]

If this information is useful, please help other people find it:
Share via:

luke.bigum

2010-Oct-19 15:31 UTC

[Puppet Users] client won''t use remote file bucket

Hi all,

I''m having a stupid moment getting a remote file bucket working. My
client only file buckets locally, not remotely.

I have this site.pp:
*********
filebucket { "main": server => "puppet" }
File { backup => "main" }
node ''default'' {
  include test
}
*********

and this test module:
*********
class test {
  file { "/etc/sudoers":
    source => "puppet:///modules/test/sudoers",
    owner => "root",
    group => "root",
    mode => "0440",
    ensure => present,
    backup => "main",
  }
}
*********

$ puppetd --test --environment testing
...
info: FileBucket adding /etc/sudoers as {md5}
fee30f6b0672f6c174709249f37380d4
info: /Stage[main]/Test/File[/etc/sudoers]: Filebucketed /etc/sudoers
to main with sum fee30f6b0672f6c174709249f37380d4
notice: Finished catalog run in 0.49 seconds

According to the Apache logs (I use Passenger) the only PUT request
it''s doing is for it''s report:

10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
catalog/..." 200 1439 "-" "-"
10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
file_metadata/modules/test/sudoers HTTP/1.1" 200 307 "-"
"-"
10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
file_content/modules/test/sudoers HTTP/1.1" 200 1421 "-"
"-"
10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
file_content/modules/test/sudoers HTTP/1.1" 200 1421 "-"
"-"
10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
file_metadata/modules/test/sudoers HTTP/1.1" 200 307 "-"
"-"
10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "PUT /testing/report/
puppet-test.fasthosts.net.uk HTTP/1.1" 200 35 "-" "-"

I''ve also stopped Apache and started up the Webrick Puppet Master,
same result, no file bucketed to the server.

Can someone point out what I''ve missed?

-- 
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.

James Turnbull

2010-Oct-19 15:58 UTC

head link

Re: [Puppet Users] client won''t use remote file bucket

luke.bigum wrote:> Hi all,
>
> I''m having a stupid moment getting a remote file bucket working.
My
> client only file buckets locally, not remotely.
>
> I have this site.pp:
> *********
> filebucket { "main": server =>  "puppet" }
> File { backup =>  "main" }
> node ''default'' {
>    include test
What Puppet version?

Regards

James Turnbull

-- 
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.

luke.bigum

2010-Oct-19 16:02 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Sorry should have said that. 2.6.2 client and server running on CentOS
5. Stock CentOS ruby (1.8.5), server runs via Passenger and Ruby
Enterprise 1.8.7.

On Oct 19, 4:58 pm, James Turnbull <ja...@puppetlabs.com>
wrote:> luke.bigum wrote:
> > Hi all,
>
> > I''m having a stupid moment getting a remote file bucket
working. My
> > client only file buckets locally, not remotely.
>
> > I have this site.pp:
> > *********
> > filebucket { "main": server =>  "puppet" }
> > File { backup =>  "main" }
> > node ''default'' {
> >    include test
>
> What Puppet version?
>
> Regards
>
> James Turnbull
-- 
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.

luke.bigum

2010-Oct-19 16:07 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

That was meant to read "Clients run stock CentOS ruby (1.8.5), server
runs via Passenger and Ruby Enterprise 1.8.7."

On Oct 19, 5:02 pm, "luke.bigum" <luke.bi...@fasthosts.co.uk>
wrote:> Sorry should have said that. 2.6.2 client and server running on CentOS
> 5. Stock CentOS ruby (1.8.5), server runs via Passenger and Ruby
> Enterprise 1.8.7.
>
> On Oct 19, 4:58 pm, James Turnbull <ja...@puppetlabs.com> wrote:
>
> > luke.bigum wrote:
> > > Hi all,
>
> > > I''m having a stupid moment getting a remote file bucket
working. My
> > > client only file buckets locally, not remotely.
>
> > > I have this site.pp:
> > > *********
> > > filebucket { "main": server =>  "puppet" }
> > > File { backup =>  "main" }
> > > node ''default'' {
> > >    include test
>
> > What Puppet version?
>
> > Regards
>
> > James Turnbull
>
>
-- 
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.

James Turnbull

2010-Oct-19 22:22 UTC

head link

Re: [Puppet Users] Re: client won''t use remote file bucket

luke.bigum wrote:> Sorry should have said that. 2.6.2 client and server running on CentOS
> 5. Stock CentOS ruby (1.8.5), server runs via Passenger and Ruby
> Enterprise 1.8.7.
> 
And no errors in the debug logs?  Can you pastie some --debug --trace logs?

Thanks

James

-- 
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

-- 
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.

luke.bigum

2010-Oct-20 09:05 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Not that I''ve been able to see, James, though I''d put money on
that
I''ve probably missed something so ridiculously simple that I
can''t see
it. I''ve attached the client and Webrick master debug logs - the
Master''s Report http error at the end can be ignored, it''s
because
Apache is shut down on the box (Puppet Master and Dashboard are the
same server in this case). I''ve also pasted master and client configs
in case it helps.

As the logs show, the puppet clients *say* they are filebucketing to
''main'', but it only ends up in the local
/var/lib/puppet/clientbucket/
and not the master''s /var/lib/puppet/bucket/. Even the Puppet Master,
which is also a Puppet client, only filebuckets into the clientbucket
directory.


[root@puppet-test ~]# grep -v ''#'' /etc/puppet/puppet.conf |
egrep -v ''^
$''
[main]
    logdir = /var/log/puppet
    rundir = /var/run/puppet
    ssldir = $vardir/ssl
[agent]
    environment = testing
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig
    report = true
    reportserver = puppet
    splay = true
    runinterval = 1200


[root@puppet-master-01 puppet]# grep -v ''#''
/etc/puppet/puppet.conf |
egrep -v ''^$''
[main]
    logdir = /var/log/puppet
    rundir = /var/run/puppet
    ssldir = $vardir/ssl
    tagmap = /etc/puppet/tagmail.conf
    pluginsync = true
    factpath = $vardir/lib/facter
[agent]
    environment = production
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig
    report = true
    reportserver = puppet
    splay = true
    runinterval = 1200
[master]
    certname = puppet
    ssl_client_header = SSL_CLIENT_S_DN
    ssl_client_verify_header = SSL_CLIENT_VERIFY
    modulepath = /var/lib/puppet/modules:/etc/puppet/modules
    reports = tagmail, http, store
    reporturl = http://localhost:3000/reports
[production]
    manifest   = /etc/puppet/conf/production/manifests/site.pp
    modulepath = /etc/puppet/conf/production/modules
[development]
    manifest   = /etc/puppet/conf/development/manifests/site.pp
    modulepath = /etc/puppet/conf/development/modules
[testing]
    manifest   = /etc/puppet/conf/testing/manifests/site.pp
    modulepath = /etc/puppet/conf/testing/modules


[root@puppet-test ~]# puppetd --test --debug --trace --verbose
debug: Puppet::Type::User::ProviderLdap: true value when expecting
false
debug: Puppet::Type::User::ProviderUser_role_add: file rolemod does
not exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/
var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/public_keys/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
public_keys]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/
lib/puppet/state]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/
puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/ssl/private_keys/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
private_keys]
debug: /File[/var/lib/puppet/ssl/certs/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
certs]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/
lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/
lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/
var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: Finishing transaction 23911437109040
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
public_keys]
debug: /File[/var/lib/puppet/ssl/certs/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
certs]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/
lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/
var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/private_keys/puppet-
test.fasthosts.net.uk.pem]: Autorequiring File[/var/lib/puppet/ssl/
private_keys]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/
var/lib/puppet/ssl]
debug: Finishing transaction 23911437768100
debug: Using cached certificate for ca
debug: Using cached certificate for puppet-test.fasthosts.net.uk
debug: Finishing transaction 23911437050520
debug: Loaded state in 0.01 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for puppet-test.fasthosts.net.uk
debug: Using cached certificate_revocation_list for ca
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw
yaml; using pson
info: Caching catalog for puppet-test.fasthosts.net.uk
debug: Creating default schedules
debug: Loaded state in 0.01 seconds
debug: /Stage[main]/Test/File[/etc/sudoers]/require: requires
Filebucket[main]
info: Applying configuration version ''1287565081''
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: /Stage[main]/Test/File[/etc/sudoers]/content: Executing ''diff -
u /etc/sudoers /tmp/puppet-file.31871.0''
--- /etc/sudoers        2010-10-20 09:53:04.000000000 +0100
+++ /tmp/puppet-file.31871.0    2010-10-20 09:53:09.000000000 +0100
@@ -18,4 +18,3 @@
 %3rdline ALL=(ALL) NOPASSWD: ALL
 %Development ALL=(ALL) NOPASSWD: ALL,!SU,!SHELLS
 %2ndline ALL=SERVICES, LOCATE, PROCESSES, SECONDLINE
-#gfdsgds
debug: Finishing transaction 23911435522540
info: FileBucket adding /etc/sudoers as {md5}
41b292d5db0cc7ed6f4ffde8c795596a
info: /Stage[main]/Test/File[/etc/sudoers]: Filebucketed /etc/sudoers
to main with sum 41b292d5db0cc7ed6f4ffde8c795596a
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
notice: /Stage[main]/Test/File[/etc/sudoers]/content: content changed
''{md5}41b292d5db0cc7ed6f4ffde8c795596a'' to ''{md5}
743b5ecb2b094e24aeb14f716b535d76''
debug: Finishing transaction 23911435648400
debug: Storing state
debug: Stored state in 0.06 seconds
notice: Finished catalog run in 0.45 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for puppet-test.fasthosts.net.uk
debug: Using cached certificate_revocation_list for ca
debug: Value of ''preferred_serialization_format'' (pson) is
invalid for
report, using default (marshal)
debug: report supports formats: b64_zlib_yaml marshal raw yaml; using
marshal





[root@puppet-master-01 puppet]# puppetmasterd --no-daemonize --debug --
trace --verbose
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: Puppet::Type::User::ProviderLdap: feature ldap is missing
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does
not exist
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: /File[/var/lib/puppet/ssl/private]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/reports]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/public_keys/puppet.pem]:
Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/yaml]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring
File[/var/lib/puppet/ssl]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/rrd]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/auth.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/
var/lib/puppet/ssl/certs]
debug: /File[/var/log/puppet/masterhttp.log]: Autorequiring File[/var/
log/puppet]
debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/server_data]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring File[/
var/lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/private_keys/puppet.pem]:
Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: /File[/etc/puppet/fileserver.conf]: Autorequiring File[/etc/
puppet]
debug: /File[/etc/puppet/manifests]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/
lib/puppet/ssl]
debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/
puppet/ssl]
debug: /File[/var/lib/puppet/bucket]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/ssl/certs/puppet.pem]: Autorequiring
File[/var/lib/puppet/ssl/certs]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: Finishing transaction 23561543042560
debug: /File[/var/lib/puppet/ssl/ca/private]: Autorequiring File[/var/
lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/ca_crl.pem]: Autorequiring File[/
var/lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/serial]: Autorequiring File[/var/
lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/ca_crt.pem]: Autorequiring File[/
var/lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/requests]: Autorequiring File[/var/
lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/ca_pub.pem]: Autorequiring File[/
var/lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/private/ca.pass]: Autorequiring
File[/var/lib/puppet/ssl/ca/private]
debug: /File[/var/lib/puppet/ssl/ca/inventory.txt]: Autorequiring
File[/var/lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/signed]: Autorequiring File[/var/
lib/puppet/ssl/ca]
debug: /File[/var/lib/puppet/ssl/ca/ca_key.pem]: Autorequiring File[/
var/lib/puppet/ssl/ca]
debug: Finishing transaction 23561544774000
debug: Using cached certificate for ca
debug: Using cached certificate for ca
debug: Using cached certificate for puppet
notice: Starting Puppet master version 2.6.2
debug: No modules mount given; autocreating with default permissions
debug: No plugins mount given; autocreating with default permissions
debug: Finishing transaction 23561542147100
info: access[^/catalog/([^/]+)$]: allowing ''method'' find
info: access[^/catalog/([^/]+)$]: allowing $1 access
info: access[/certificate_revocation_list/ca]: allowing
''method'' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing ''method'' save
info: access[/report]: allowing * access
info: access[/file]: allowing * access
info: access[/certificate/ca]: adding authentication no
info: access[/certificate/ca]: allowing ''method'' find
info: access[/certificate/ca]: allowing * access
info: access[/certificate/]: adding authentication no
info: access[/certificate/]: allowing ''method'' find
info: access[/certificate/]: allowing * access
info: access[/certificate_request]: adding authentication no
info: access[/certificate_request]: allowing ''method'' find
info: access[/certificate_request]: allowing ''method'' save
info: access[/certificate_request]: allowing * access
info: access[/]: adding authentication any
info: Inserting default ''/status''(auth) acl because none where
found
in ''/etc/puppet/auth.conf''
info: Inserting default ''/resource''(auth) acl because none
where found
in ''/etc/puppet/auth.conf''
info: Expiring the node cache of puppet-test.fasthosts.net.uk
info: Not using expired node for puppet-test.fasthosts.net.uk from
cache; expired at Wed Oct 20 09:49:04 +0100 2010
info: Caching node for puppet-test.fasthosts.net.uk
debug: importing
''/etc/puppet/conf/production/manifests/standalone.pp''
in environment production
debug: importing ''/etc/puppet/conf/production/manifests/
puppetmasters.pp'' in environment production
debug: importing ''/etc/puppet/conf/production/manifests/
customer_mysql.pp'' in environment production
debug: importing ''/etc/puppet/conf/testing/modules/test/manifests/
init.pp'' in environment testing
debug: Automatically imported test from test into testing
notice: Compiled catalog for puppet-test.fasthosts.net.uk in
environment testing in 0.09 seconds
/usr/lib/ruby/1.8/net/http.rb:560:in `initialize''
/usr/lib/ruby/1.8/net/http.rb:560:in `open''
/usr/lib/ruby/1.8/net/http.rb:560:in `connect''
/usr/lib/ruby/1.8/timeout.rb:48:in `timeout''
/usr/lib/ruby/1.8/timeout.rb:76:in `timeout''
/usr/lib/ruby/1.8/net/http.rb:560:in `connect''
/usr/lib/ruby/1.8/net/http.rb:553:in `do_start''
/usr/lib/ruby/1.8/net/http.rb:542:in `start''
/usr/lib/ruby/site_ruby/1.8/puppet/reports/http.rb:18:in `process''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/processor.rb:
32:in `process''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/processor.rb:
25:in `each''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/processor.rb:
25:in `process''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/processor.rb:
14:in `save''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:253:in
`save''
/usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:64:in `save''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:168:in
`save_object''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:143:in
`do_save''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in
`send''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb:68:in
`process''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb:24:in
`service''
/usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service''
/usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:45:in
`listen''
/usr/lib/ruby/1.8/webrick/server.rb:173:in `call''
/usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread''
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start''
/usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread''
/usr/lib/ruby/1.8/webrick/server.rb:95:in `start''
/usr/lib/ruby/1.8/webrick/server.rb:92:in `each''
/usr/lib/ruby/1.8/webrick/server.rb:92:in `start''
/usr/lib/ruby/1.8/webrick/server.rb:23:in `start''
/usr/lib/ruby/1.8/webrick/server.rb:82:in `start''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:42:in
`listen''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in
`initialize''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in `new''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:41:in
`listen''
/usr/lib/ruby/1.8/thread.rb:135:in `synchronize''
/usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb:38:in
`listen''
/usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:127:in `listen''
/usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb:142:in `start''
/usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb:124:in `start''
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:114:in `main''
/usr/lib/ruby/site_ruby/1.8/puppet/application/master.rb:46:in
`run_command''
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run''
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:393:in
`exit_on_fail''
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:287:in `run''
/usr/sbin/puppetmasterd:4
err: Report http failed: Connection refused - connect(2)
notice: Caught INT; calling stop

-- 
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.

Roman

2010-Nov-09 03:47 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Hi James.

Could you tell if you found a resolution to this problem? I seem to
experience it as well.

Thanks in advance,

Regards,
Roman

On Oct 20, 2:31 am, "luke.bigum" <luke.bi...@fasthosts.co.uk>
wrote:> Hi all,
>
> I''m having a stupid moment getting a remote file bucket working.
My
> client only file buckets locally, not remotely.
>
> I have this site.pp:
> *********
> filebucket { "main": server => "puppet" }
> File { backup => "main" }
> node ''default'' {
>   include test}
>
> *********
>
> and this test module:
> *********
> class test {
>   file { "/etc/sudoers":
>     source => "puppet:///modules/test/sudoers",
>     owner => "root",
>     group => "root",
>     mode => "0440",
>     ensure => present,
>     backup => "main",
>   }}
>
> *********
>
> $ puppetd --test --environment testing
> ...
> info: FileBucket adding /etc/sudoers as {md5}
> fee30f6b0672f6c174709249f37380d4
> info: /Stage[main]/Test/File[/etc/sudoers]: Filebucketed /etc/sudoers
> to main with sum fee30f6b0672f6c174709249f37380d4
> notice: Finished catalog run in 0.49 seconds
>
> According to the Apache logs (I use Passenger) the only PUT request
> it''s doing is for it''s report:
>
> 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> catalog/..." 200 1439 "-" "-"
> 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> file_metadata/modules/test/sudoers HTTP/1.1" 200 307 "-"
"-"
> 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> file_content/modules/test/sudoers HTTP/1.1" 200 1421 "-"
"-"
> 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
> file_content/modules/test/sudoers HTTP/1.1" 200 1421 "-"
"-"
> 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
> file_metadata/modules/test/sudoers HTTP/1.1" 200 307 "-"
"-"
> 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "PUT /testing/report/
> puppet-test.fasthosts.net.uk HTTP/1.1" 200 35 "-"
"-"
>
> I''ve also stopped Apache and started up the Webrick Puppet Master,
> same result, no file bucketed to the server.
>
> Can someone point out what I''ve missed?
-- 
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.

luke.bigum

2010-Nov-09 09:33 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Roman,

Not that I know of. I''m still aware it doesn''t work in my
site, but
I''m content with local file bucketing until I have the time to look at
this again.

-Luke

On Nov 9, 3:47 am, Roman <roman....@googlemail.com>
wrote:> Hi James.
>
> Could you tell if you found a resolution to this problem? I seem to
> experience it as well.
>
> Thanks in advance,
>
> Regards,
> Roman
>
> On Oct 20, 2:31 am, "luke.bigum"
<luke.bi...@fasthosts.co.uk> wrote:
>
> > Hi all,
>
> > I''m having a stupid moment getting a remote file bucket
working. My
> > client only file buckets locally, not remotely.
>
> > I have this site.pp:
> > *********
> > filebucket { "main": server => "puppet" }
> > File { backup => "main" }
> > node ''default'' {
> >   include test}
>
> > *********
>
> > and this test module:
> > *********
> > class test {
> >   file { "/etc/sudoers":
> >     source => "puppet:///modules/test/sudoers",
> >     owner => "root",
> >     group => "root",
> >     mode => "0440",
> >     ensure => present,
> >     backup => "main",
> >   }}
>
> > *********
>
> > $ puppetd --test --environment testing
> > ...
> > info: FileBucket adding /etc/sudoers as {md5}
> > fee30f6b0672f6c174709249f37380d4
> > info: /Stage[main]/Test/File[/etc/sudoers]: Filebucketed /etc/sudoers
> > to main with sum fee30f6b0672f6c174709249f37380d4
> > notice: Finished catalog run in 0.49 seconds
>
> > According to the Apache logs (I use Passenger) the only PUT request
> > it''s doing is for it''s report:
>
> > 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> > catalog/..." 200 1439 "-" "-"
> > 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> > file_metadata/modules/test/sudoers HTTP/1.1" 200 307
"-" "-"
> > 10.44.222.42 - - [19/Oct/2010:16:18:26 +0100] "GET /testing/
> > file_content/modules/test/sudoers HTTP/1.1" 200 1421
"-" "-"
> > 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
> > file_content/modules/test/sudoers HTTP/1.1" 200 1421
"-" "-"
> > 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "GET /testing/
> > file_metadata/modules/test/sudoers HTTP/1.1" 200 307
"-" "-"
> > 10.44.222.42 - - [19/Oct/2010:16:18:27 +0100] "PUT
/testing/report/
> > puppet-test.fasthosts.net.uk HTTP/1.1" 200 35 "-"
"-"
>
> > I''ve also stopped Apache and started up the Webrick Puppet
Master,
> > same result, no file bucketed to the server.
>
> > Can someone point out what I''ve missed?
>
>
-- 
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.

Mikael Fridh

2010-Nov-11 15:23 UTC

head link

Re: [Puppet Users] client won''t use remote file bucket

On Tue, Oct 19, 2010 at 5:31 PM, luke.bigum <luke.bigum@fasthosts.co.uk>
wrote:> Hi all,
>
> I''m having a stupid moment getting a remote file bucket working.
My
> client only file buckets locally, not remotely.
>
> I have this site.pp:
> *********
> filebucket { "main": server => "puppet" }
> File { backup => "main" }
> node ''default'' {
>  include test
> }
> *********
I have pretty much the same config stolen from the example in the
puppet docs and also get no bucketing on the master.

agent trace log:

debug: Finishing transaction 23620811645560
info: FileBucket adding /etc/rc.d/init.d/ibe as
{md5}bc5a527cdb18f4e7030b72f30bc67786
info: /Stage[main]/Ibe::Config/File[/etc/rc.d/init.d/ibe]:
Filebucketed /etc/rc.d/init.d/ibe to main with sum
bc5a527cdb18f4e7030b72f30bc67786

It says it backs it up to "main" but nothing''s received on
the master.
Likewise, masterhttp.log have nothing but report PUTs in it. server
bucket is empty. No errors anywhere.

Centos5, 2.6.2.
Same behaviour on previous 0.2x.x versions.

--
Mike

-- 
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.

Felix Frank

2010-Nov-18 23:23 UTC

head link

Re: [Puppet Users] Re: client won''t use remote file bucket

On 09.11.2010 10:33, luke.bigum wrote:> Roman,
>
> Not that I know of. I''m still aware it doesn''t work in my
site, but
> I''m content with local file bucketing until I have the time to
look at
> this again.
>
> -Luke
>
> On Nov 9, 3:47 am, Roman<roman....@googlemail.com>  wrote:
>> Hi James.
>>
>> Could you tell if you found a resolution to this problem? I seem to
>> experience it as well.
>>
>> Thanks in advance,
>>
>> Regards,
>> Roman
>>
>> On Oct 20, 2:31 am,
"luke.bigum"<luke.bi...@fasthosts.co.uk>  wrote:
>>
>>> Hi all,
>>
>>> I''m having a stupid moment getting a remote file bucket
working. My
>>> client only file buckets locally, not remotely.
>>
>>> I have this site.pp:
>>> *********
>>> filebucket { "main": server =>  "puppet" }
>>> File { backup =>  "main" }
>>> node ''default'' {
>>>    include test}
All this rings a faint bell. We had a similar problem after upgrading to 
0.25.5.

For us, specifying "path => false" in the filebucket { } solved the
issue.

Let me know if it does anything for you.

HTH,
Felix

-- 
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.

luke.bigum

2010-Nov-19 09:15 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Felix,

That fixes the problem, my remote file bucket now works. I''ll raise a
bug for this.

Thanks!

-Luke

On Nov 18, 11:23 pm, Felix Frank <Felix.Fr...@alumni.tu-berlin.de>
wrote:> On 09.11.2010 10:33, luke.bigum wrote:
>
>
>
> > Roman,
>
> > Not that I know of. I''m still aware it doesn''t work
in my site, but
> > I''m content with local file bucketing until I have the time
to look at
> > this again.
>
> > -Luke
>
> > On Nov 9, 3:47 am, Roman<roman....@googlemail.com>  wrote:
> >> Hi James.
>
> >> Could you tell if you found a resolution to this problem? I seem
to
> >> experience it as well.
>
> >> Thanks in advance,
>
> >> Regards,
> >> Roman
>
> >> On Oct 20, 2:31 am,
"luke.bigum"<luke.bi...@fasthosts.co.uk>  wrote:
>
> >>> Hi all,
>
> >>> I''m having a stupid moment getting a remote file
bucket working. My
> >>> client only file buckets locally, not remotely.
>
> >>> I have this site.pp:
> >>> *********
> >>> filebucket { "main": server =>
 "puppet" }
> >>> File { backup =>  "main" }
> >>> node ''default'' {
> >>>    include test}
>
> All this rings a faint bell. We had a similar problem after upgrading to
> 0.25.5.
>
> For us, specifying "path => false" in the filebucket { }
solved the issue.
>
> Let me know if it does anything for you.
>
> HTH,
> Felix
-- 
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.

Felix Frank

2010-Nov-19 09:56 UTC

head link

Re: [Puppet Users] Re: client won''t use remote file bucket

On 11/19/2010 10:15 AM, luke.bigum wrote:> Felix,
> 
> That fixes the problem, my remote file bucket now works. I''ll
raise a
> bug for this.
> 
> Thanks!
> 
> -Luke
Huh, interesting.

This commit is what tipped me off about the likely fix:
266aafa6efa9dff5fb0b49ffdafc9372edcafdfe

I''m not sure if it''s the source of this problem, but
it''s probably as
good a lead as any.

Glad this helped!

Cheers,
Felix

-- 
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.

Mikael Fridh

2010-Nov-23 09:13 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

On Nov 19, 10:56 am, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:> On 11/19/2010 10:15 AM, luke.bigum wrote:
>
> > Felix,
>
> > That fixes the problem, my remote file bucket now works. I''ll
raise a
> > bug for this.
Fixes it for me as well, thanks!

--
Mikael

-- 
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.

Nicolas Aizier

2010-Dec-22 02:41 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Hi all,

this solve the issue for me also but now even if it still do backup
in /var/lib/puppet/bucket it doesn''t mention it in the report ?
Before that "path => false" line it was mentionning it but not
doing
it .....

Strange isn''t it ?

On Nov 23, 7:13 pm, Mikael Fridh <fri...@gmail.com>
wrote:> On Nov 19, 10:56 am, Felix Frank <felix.fr...@alumni.tu-berlin.de>
> wrote:
>
> > On 11/19/2010 10:15 AM, luke.bigum wrote:
>
> > > Felix,
>
> > > That fixes the problem, my remote file bucket now works.
I''ll raise a
> > > bug for this.
>
> Fixes it for me as well, thanks!
>
> --
> Mikael
-- 
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.

Nicolas Aizier

2010-Dec-22 03:01 UTC

head link

[Puppet Users] Re: client won''t use remote file bucket

Oh my bad, I just realize that is is backuping by md5 .... so one
backup to rule them all ....
Stupid me, forget about that. It''s working fine.

On Dec 22, 12:41 pm, Nicolas Aizier <nicolas.aiz...@googlemail.com>
wrote:> Hi all,
>
> this solve the issue for me also but now even if it still do backup
> in /var/lib/puppet/bucketit doesn''t mention it in the report ?
> Before that "path => false" line it was mentionning it but not
doing
> it .....
>
> Strange isn''t it ?
>
> On Nov 23, 7:13 pm, Mikael Fridh <fri...@gmail.com> wrote:
>
>
>
>
>
>
>
> > On Nov 19, 10:56 am, Felix Frank
<felix.fr...@alumni.tu-berlin.de>
> > wrote:
>
> > > On 11/19/2010 10:15 AM, luke.bigum wrote:
>
> > > > Felix,
>
> > > > That fixes the problem, my remotefilebucketnow works.
I''ll raise a
> > > > bug for this.
>
> > Fixes it for me as well, thanks!
>
> > --
> > Mikael
-- 
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.

Possibly Parallel Threads

Search for more reasonably related threads

Puppet users - Oct 2010 - client won't use remote file bucket

[Puppet Users] client won''t use remote file bucket

Re: [Puppet Users] client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

Re: [Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

Re: [Puppet Users] client won''t use remote file bucket

Re: [Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

Re: [Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

[Puppet Users] Re: client won''t use remote file bucket

Possibly Parallel Threads