Craig White
2011-Nov-02 19:13 UTC
[Puppet Users] vmware player interference - no support for http method POST
as soon as I installed vmware player and spun up a VM instance on my development system, I could no longer connect to puppet... cwhite@development:~/tti_framework$ sudo puppet agent --server MY_PUPPETMASTER --verbose --test --debug debug: Failed to load library ''selinux'' for feature ''selinux'' debug: Failed to load library ''shadow'' for feature ''libshadow'' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderLdap: true value when expecting false 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::File::ProviderMicrosoft_windows: feature microsoft_windows is missing debug: /File[/etc/puppet/ssl/certs/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/log/http.log]: Autorequiring File[/var/lib/puppet/log] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/private_keys/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring File[/var/lib/puppet/state] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet] debug: Finishing transaction 90587490 debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/public_keys/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/public_keys] debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet] debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certs/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/certs] debug: /File[/etc/puppet/ssl/private_keys/development.domain.pem]: Autorequiring File[/etc/puppet/ssl/private_keys] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/log/http.log]: Autorequiring File[/var/lib/puppet/log] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction 90415240 debug: Using cached certificate for ca debug: Using cached certificate for development.domain notice: Ignoring --listen on onetime run debug: Finishing transaction 90044120 debug: Loaded state in 0.00 seconds info: Retrieving plugin debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Using cached certificate for ca debug: Using cached certificate for development.domain debug: Using cached certificate_revocation_list for ca debug: Finishing transaction 89860050 info: Loading facts in passenger_version info: Loading facts in datacenter info: Loading facts in passenger_version info: Loading facts in datacenter debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson err: Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run debug: Value of ''preferred_serialization_format'' (pson) is invalid for report, using default (b64_zlib_yaml) debug: report supports formats: b64_zlib_yaml marshal raw yaml; using b64_zlib_yaml Anyone stumble into this before? Fix? $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION="Ubuntu 10.04.3 LTS" -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! -- 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.
Nigel Kersten
2011-Nov-02 19:50 UTC
Re: [Puppet Users] vmware player interference - no support for http method POST
On Wed, Nov 2, 2011 at 12:13 PM, Craig White <craig.white@ttiltd.com> wrote:> > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > No support for http method POST > warning: Not using cache on failed catalog >You must be running a newer version agent than your master is. -- 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.
Craig White
2011-Nov-02 20:00 UTC
Re: [Puppet Users] vmware player interference - no support for http method POST
On Nov 2, 2011, at 12:50 PM, Nigel Kersten wrote:> > > On Wed, Nov 2, 2011 at 12:13 PM, Craig White <craig.white@ttiltd.com> wrote: > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST > warning: Not using cache on failed catalog > > You must be running a newer version agent than your master is.---- indeed - someone must have run a generalized ''gem update'' because it wasn''t me. The worst part about that is that I actually stumbled into this before (perhaps in August). I have a terrific memory but it seems to be very short in duration. ;-) Thanks Craig -- 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.
Nigel Kersten
2011-Nov-03 15:05 UTC
Re: [Puppet Users] vmware player interference - no support for http method POST
On Wed, Nov 2, 2011 at 1:00 PM, Craig White <craig.white@ttiltd.com> wrote:> > On Nov 2, 2011, at 12:50 PM, Nigel Kersten wrote: > > > > > > > On Wed, Nov 2, 2011 at 12:13 PM, Craig White <craig.white@ttiltd.com> > wrote: > > > > err: Could not retrieve catalog from remote server: Error 400 on SERVER: > No support for http method POST > > warning: Not using cache on failed catalog > > > > You must be running a newer version agent than your master is. > ---- > indeed - someone must have run a generalized ''gem update'' because it > wasn''t me. The worst part about that is that I actually stumbled into this > before (perhaps in August). I have a terrific memory but it seems to be > very short in duration. > > ;-) > >So that sucks, we''re obviously not providing a useful enough error message here. Do you want to bug report that a 2.7.x client should provide something more useful in terms out of output when it tries to POST the facts with a catalog request to a server that doesn''t accept the POST action? -- 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.