thr3ads.net - Puppet users - [Puppet Users] viewing b64_zlib

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

Sukh Khehra

2010-Aug-26 16:05 UTC

[Puppet Users] viewing b64_zlib_yaml data

I am using puppet 0.25.1on Centos 5.4 on both client and server along
with apache 2.2.3/mongrel 1.1.5 on the server side. I am getting http
status code 400 (The request could not be understood by the server due
to malformed syntax) in balancer_access_log for a handful of hosts like
so. How do I can decode that data to look at it to see what''s wrong
with
it?

 

 

172.16.19.30 - - [26/Aug/2010:00:31:10 +0000] "GET
/production/catalog/hostname.sk.local?facts=<compressed b64 string?
Encrypted?>&facts_format=b64_zlib_yaml HTTP/1.1" 400 190
"-" "-"

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

Brice Figureau

2010-Aug-26 16:12 UTC

head link

Re: [Puppet Users] viewing b64_zlib_yaml data

On Thu, 2010-08-26 at 09:05 -0700, Sukh Khehra wrote:> I am using puppet 0.25.1on Centos 5.4 on both client and server along
> with apache 2.2.3/mongrel 1.1.5 on the server side. I am getting http
> status code 400 (The request could not be understood by the server due
> to malformed syntax) in balancer_access_log for a handful of hosts
> like so. How do I can decode that data to look at it to see what’s
> wrong with it?
> 
>  
> 
>  
> 
> 172.16.19.30 - - [26/Aug/2010:00:31:10 +0000]
> "GET /production/catalog/hostname.sk.local?facts=<compressed b64
> string? Encrypted?>&facts_format=b64_zlib_yaml HTTP/1.1" 400
190 "-"
> "-"
There''s nothing wrong in the data itself. There are great chances the
problem is that the request is too large for Apache to handle.
I don''t know its exact limit, but I believe it''s around 4k.
I think apache error.log should log the error, if not then it might be
either a mongrel error or the master itself.
You should also check your master log to see if it logs anything about
this.

-- 
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!

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

Sukh Khehra

2010-Aug-26 18:20 UTC

head link

RE: [Puppet Users] viewing b64_zlib_yaml data

Thanks for the helpful suggestions.

I checked for this and my problem does not appear to be request size
related. I say this because I turned on the logging for the request size
and see that it is serving requests larger than the problem hosts just
fine. I even tried turning on debugging for puppetmaster but it is not
logging anything helpful (log pasted below). The behavior I see is that
the puppetmaster is not seeing any facts from the client (I suspect due
to the issue I posted about originally). Any other ideas?


2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Reopening
log files
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Starting
Puppet server version 0.25.5
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Mongrel
client debugging enabled. [$mongrel_debug_client = true].
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Finishing
transaction 23456270353820 with 0 changes
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[files]) allowing *.sk.local access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[files]) allowing 172.16.19.0/24 access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[modules]) allowing *.sk.local access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[modules]) allowing 172.16.19.0/24 access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[plugins]) allowing *.sk.local access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]:
(mount[plugins]) allowing 172.16.19.0/24 access
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: No path
given for plugins mount; creating a special PluginMount
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Creating
interpreter
2010-08-26T18:03:19+00:00 PUPPETMASTER puppetmasterd[18675]: Finishing
transaction 23456270320960 with 0 changes
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[^/catalog/([^/]+)$]) allowing ''method'' find
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[^/catalog/([^/]+)$]) allowing $1 access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_revocation_list/ca]) allowing ''method''
find
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_revocation_list/ca]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/report]) allowing ''method'' save
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/report]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/file]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/ca]) adding authentication no
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/ca]) allowing ''method'' find
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/ca]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/]) adding authentication no
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/]) allowing ''method'' find
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate/]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_request]) adding authentication no
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_request]) allowing ''method'' find
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_request]) allowing ''method'' save
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]:
(access[/certificate_request]) allowing * access
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: (access[/])
adding authentication any
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: Using
cached node for hostname.sk.local
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/cron.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/hostsfile.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/services-off.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/unix.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/httpd.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/ruby-shadow.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/facter_mods.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/services-on.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/sysctl-conf.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/timezone.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/_nagios.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/_operations.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/subversion.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/resolvconf.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/log-scripts.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/manifests/classes/vmware-tools''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: Host is
missing hostname and/or domain: hostname.sk.local
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/init.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/virt_all_groups.pp''
2010-08-26T18:03:46+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/virt_all_users.pp''
2010-08-26T18:03:47+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/virt_homedirs.pp''
2010-08-26T18:03:47+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/groups.pp''
2010-08-26T18:03:47+00:00 PUPPETMASTER puppetmasterd[18675]: Adding code
to users::groups_se on line 120 in file
/etc/puppet/modules/production/users/manifests/groups.pp
2010-08-26T18:03:47+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/users.pp''
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/homedirs.pp''
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/managehome.pp''
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/nscd.pp''
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/users/manifests/spam_nfs.pp''
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: Adding code
to main on line 10 in file
/etc/puppet/modules/production/users/manifests/init.pp
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: Autoloaded
module users
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: No true
answers and no default
2010-08-26T18:03:48+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/common/manifests/init.pp''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Autoloaded
module common
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/puppet/manifests/init.pp''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Autoloaded
module puppet
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/root/manifests/init.pp''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Autoloaded
module root
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: importing
''/etc/puppet/modules/production/arc/manifests/init.pp''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Autoloaded
module arc
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Class
''users::virt_all_users'' already evaluated; not evaluating
again
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Puppet::Type::Package::ProviderRpm) Executing ''/bin/rpm
--version''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Puppet::Type::Package::ProviderYum) Executing ''/bin/rpm
--version''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Puppet::Type::Package::ProviderAptrpm) Executing ''/bin/rpm -ql
rpm''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Puppet::Type::Package::ProviderUrpmi) Executing ''/bin/rpm -ql
rpm''
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Scope(Class[ruby-shadow])) Need to install shadow, But not have for
this OS:
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: No true
answers and no default
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(Scope(Class[puppet::sysconfig])) Retrieving template
puppet/sysconfig-puppet.erb
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]:
(template[/etc/puppet/modules/production/puppet/templates/sysconfig-pupp
et.erb]) Bound template variables for
/etc/puppet/modules/production/puppet/templates/sysconfig-puppet.erb in
0.00 seconds

2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Failed to
parse template puppet/sysconfig-puppet.erb: Could not find value for
''ipaddress'' at
/etc/puppet/modules/production/puppet/manifests/init.pp:132 on node
hostname.sk.local
2010-08-26T18:03:49+00:00 PUPPETMASTER puppetmasterd[18675]: Failed to
parse template puppet/sysconfig-puppet.erb: Could not find value for
''ipaddress'' at
/etc/puppet/modules/production/puppet/manifests/init.pp:132 on node
hostname.sk.local



-----Original Message-----
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of Brice Figureau
Sent: Thursday, August 26, 2010 9:12 AM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] viewing b64_zlib_yaml data

On Thu, 2010-08-26 at 09:05 -0700, Sukh Khehra wrote:> I am using puppet 0.25.1on Centos 5.4 on both client and server along
> with apache 2.2.3/mongrel 1.1.5 on the server side. I am getting http
> status code 400 (The request could not be understood by the server due
> to malformed syntax) in balancer_access_log for a handful of hosts
> like so. How do I can decode that data to look at it to see what''s
> wrong with it?
> 
>  
> 
>  
> 
> 172.16.19.30 - - [26/Aug/2010:00:31:10 +0000]
> "GET /production/catalog/hostname.sk.local?facts=<compressed b64
> string? Encrypted?>&facts_format=b64_zlib_yaml HTTP/1.1" 400
190 "-"
> "-"
There''s nothing wrong in the data itself. There are great chances the
problem is that the request is too large for Apache to handle.
I don''t know its exact limit, but I believe it''s around 4k.
I think apache error.log should log the error, if not then it might be
either a mongrel error or the master itself.
You should also check your master log to see if it logs anything about
this.

-- 
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!

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

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

Brice Figureau

2010-Aug-26 18:37 UTC

head link

Re: [Puppet Users] viewing b64_zlib_yaml data

On 26/08/10 20:20, Sukh Khehra wrote:> Thanks for the helpful suggestions.
> 
> I checked for this and my problem does not appear to be request size
> related. I say this because I turned on the logging for the request size
> and see that it is serving requests larger than the problem hosts just
> fine.
I meant incoming request. Those are usually the issue with apache,
especially if the given node has a large number of facts or long facts.
> I even tried turning on debugging for puppetmaster but it is not
> logging anything helpful (log pasted below). The behavior I see is that
> the puppetmaster is not seeing any facts from the client (I suspect due
> to the issue I posted about originally). Any other ideas?
You can try to decode the facts (as you asked in your first message)
with this:
1) launch irb
2) enter:
require ''zlib''
require ''cgi''
text="<insert here the content of the facts parameters as in your
log>"
Zlib::Inflate.inflate(Base64.decode64(CGI.unescape(text)))

This should print on the console the YAML serialization of the facts.
If in those you have the missing facts, then the problem is that this
request is not transmitted verbatim to puppet.

Hope that helps,
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

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

Sukh Khehra

2010-Aug-26 20:37 UTC

head link

RE: [Puppet Users] viewing b64_zlib_yaml data

Apache is not logging any error when this happens. I experimented with
upping the LimitRequestLine, and LimitRequestFieldsize apache config
directives but hasn''t made any difference.

I tried your suggestion to decode the string (even one that works ok)
but am getting this error....Not sure what this means...

I even tried 
irb(main):017:0>
Zlib::Inflate.inflate(Base64.decode64(CGI.unescape(text)))
Zlib::BufError: buffer error
        from (irb):17:in `inflate''
        from (irb):17
        from :0


-----Original Message-----
From: puppet-users@googlegroups.com
[mailto:puppet-users@googlegroups.com] On Behalf Of Brice Figureau
Sent: Thursday, August 26, 2010 11:37 AM
To: puppet-users@googlegroups.com
Subject: Re: [Puppet Users] viewing b64_zlib_yaml data

On 26/08/10 20:20, Sukh Khehra wrote:> Thanks for the helpful suggestions.
> 
> I checked for this and my problem does not appear to be request size
> related. I say this because I turned on the logging for the request
size> and see that it is serving requests larger than the problem hosts just
> fine.
I meant incoming request. Those are usually the issue with apache,
especially if the given node has a large number of facts or long facts.
> I even tried turning on debugging for puppetmaster but it is not
> logging anything helpful (log pasted below). The behavior I see is
that> the puppetmaster is not seeing any facts from the client (I suspect
due> to the issue I posted about originally). Any other ideas?
You can try to decode the facts (as you asked in your first message)
with this:
1) launch irb
2) enter:
require ''zlib''
require ''cgi''
text="<insert here the content of the facts parameters as in your
log>"
Zlib::Inflate.inflate(Base64.decode64(CGI.unescape(text)))

This should print on the console the YAML serialization of the facts.
If in those you have the missing facts, then the problem is that this
request is not transmitted verbatim to puppet.

Hope that helps,
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

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

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

Puppet users - Aug 2010 - viewing b64_zlib_yaml data

[Puppet Users] viewing b64_zlib_yaml data

Re: [Puppet Users] viewing b64_zlib_yaml data

RE: [Puppet Users] viewing b64_zlib_yaml data

Re: [Puppet Users] viewing b64_zlib_yaml data

RE: [Puppet Users] viewing b64_zlib_yaml data