Bug #4808
Intermittent "Could not retrieve catalog from remote server: end of file reached"
| Status: | Accepted | Start date: | 09/21/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | network | |||
| Target version: | - | |||
| Affected Puppet version: | 2.6.1 | Branch: | ||
| Keywords: | ||||
| Votes: | 7 |
Description
With puppet 2.6.1 / ruby 1.8.7 on Solaris 10, we occassionally get “end of file reached” errors. We have ~100 client systems connecting to the puppetmaster.. all are puppet 2.6.1.
Sep 18 12:20:19 my-server puppet-agent[2247]: [ID 702911 daemon.notice] (/Stage[main]/Sjsws::Start_admin/Exec[sjsws_start_admin]/returns) executed successfully Sep 18 12:20:20 my-server puppet-agent[2247]: [ID 702911 daemon.notice] Finished catalog run in 27.08 seconds Sep 18 18:21:00 int-transport puppet-agent[2247]: [ID 702911 daemon.notice] (/Stage[main]/Sjsws::Start_admin/Exec[sjsws_start_admin]/returns) executed successfully Sep 18 18:21:01 my-server puppet-agent[2247]: [ID 702911 daemon.notice] Finished catalog run in 27.30 seconds Sep 19 00:21:09 my-server puppet-agent[2247]: [ID 702911 daemon.error] Could not retrieve catalog from remote server: end of file reached Sep 19 00:21:09 my-server puppet-agent[2247]: [ID 702911 daemon.warning] Not using cache on failed catalog Sep 19 00:21:09 my-server puppet-agent[2247]: [ID 702911 daemon.error] Could not retrieve catalog; skipping run Sep 19 06:21:49 my-server puppet-agent[2247]: [ID 702911 daemon.notice] (/Stage[main]/Sjsws::Start_admin/Exec[sjsws_start_admin]/returns) executed successfully Sep 19 06:21:49 my-server puppet-agent[2247]: [ID 702911 daemon.notice] Finished catalog run in 27.88 seconds Sep 19 12:22:28 my-server puppet-agent[2247]: [ID 702911 daemon.notice] (/Stage[main]/Sjsws::Start_admin/Exec[sjsws_start_admin]/returns) executed successfully Sep 19 12:22:29 my-server puppet-agent[2247]: [ID 702911 daemon.notice] Finished catalog run in 27.22 seconds
It would be nice to avoid these, as we have set things up to send emails for recipe errors.. Our previous version was 0.25.4.. on that version we got intermittent errors with some message about SSL.. we had hoped this upgrade would silence these emails, but not yet.. just a different message :–/
I will try to capture one of these failures with debug log output.
Related issues
History
Updated by Alan Harder over 1 year ago
- Affected Puppet version set to 2.6.1
Updated by Alan Harder over 1 year ago
I ran an update on one system every 10 minutes overnight, and got the error 1 time:
debug: Failed to load library 'rubygems' for feature 'rubygems'
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'shadow' for feature 'libshadow'
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::ProviderDirectoryservice: file /usr/bin/dscl does not exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature microsoft_windows is missing
debug: /File[/etc/opt/csw/puppet/ssl/certificate_requests]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/var/opt/csw/puppet/log]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/state/graphs]: Autorequiring File[/var/opt/csw/puppet/state]
debug: /File[/etc/opt/csw/puppet/ssl/public_keys]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/var/opt/csw/puppet/client_data]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/state/state.yaml]: Autorequiring File[/var/opt/csw/puppet/state]
debug: /File[/etc/opt/csw/puppet/ssl/public_keys/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/public_keys]
debug: /File[/etc/opt/csw/puppet/ssl/certs/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/certs]
debug: /File[/etc/opt/csw/puppet/ssl/private_keys]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/var/opt/csw/puppet/lib]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/run]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/private_keys/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/private_keys]
debug: /File[/etc/opt/csw/puppet/ssl]: Autorequiring File[/etc/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/puppet.conf]: Autorequiring File[/etc/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/clientbucket]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/state/classes.txt]: Autorequiring File[/var/opt/csw/puppet/state]
debug: /File[/var/opt/csw/puppet/facts]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/certs]
debug: /File[/var/opt/csw/puppet/client_yaml]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/var/opt/csw/puppet/state]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/crl.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/etc/opt/csw/puppet/ssl/private]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/etc/opt/csw/puppet/ssl/certs]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: Finishing transaction 8206968
debug: /File[/var/opt/csw/puppet/run]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/private_keys/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/private_keys]
debug: /File[/var/opt/csw/puppet/state]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/public_keys/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/public_keys]
debug: /File[/etc/opt/csw/puppet/ssl/certs/{my-server}.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/certs]
debug: /File[/etc/opt/csw/puppet/ssl/public_keys]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/etc/opt/csw/puppet/ssl/private_keys]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/var/opt/csw/puppet/lib]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/crl.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/var/opt/csw/puppet/log]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/opt/csw/puppet/ssl/certs]
debug: /File[/var/opt/csw/puppet/facts]: Autorequiring File[/var/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl]: Autorequiring File[/etc/opt/csw/puppet]
debug: /File[/etc/opt/csw/puppet/ssl/private]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/etc/opt/csw/puppet/ssl/certificate_requests]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: /File[/etc/opt/csw/puppet/ssl/certs]: Autorequiring File[/etc/opt/csw/puppet/ssl]
debug: Finishing transaction 7730340
debug: Using cached certificate for ca
debug: Using cached certificate for {my-server}
debug: Finishing transaction 7499976
debug: Loaded state in 0.02 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for {my-server}
debug: Using cached certificate_revocation_list for ca
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw yaml; using pson
err: Could not retrieve catalog from remote server: end of file reached
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
debug: Using cached certificate for ca
debug: Using cached certificate for {my-server}
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
Puppetmaster log says:
Sep 21 06:18:09 {my-master} puppet-master[10732]: [ID 702911 daemon.notice] Compiled catalog for {another-client-1} in environment production in 3.92 seconds
Sep 21 06:18:14 {my-master} puppet-master[10732]: [ID 702911 daemon.notice] Compiled catalog for {another-client-2} in environment production in 1.58 seconds
Sep 21 06:18:54 {my-master} puppet-master[10732]: [ID 702911 daemon.notice] Compiled catalog for {my-server} in environment production in 2.62 seconds
Sep 21 06:21:32 {my-master} puppet-master[10732]: [ID 702911 daemon.notice] Compiled catalog for {another-client-3} in environment production in 2.45 seconds
Updated by Alan Harder over 1 year ago
More messages that may or may not be related to this issue, but seem connection related:
err: /Stage[main]/MyClass::Database/MyClass::Run_script[db.sh]/File[/tmp/puppet_myapp/db.sh]: Could not evaluate: Connection reset by peer - SSL_connect Could not retrieve file metadata for puppet:///modules/myapp/scripts/db.sh: Connection reset by peer - SSL_connect at /etc/opt/csw/puppet/modules/myapp/manifests/database.pp:226
As you can probably tell from the error message, the line# referenced above is a file resource for db.sh file.
Fri Sep 17 09:36:52 -0600 2010 /File[/tmp/puppet_myapp/ARTIFACTS/DB/SCHEMA/myfile.sql] (err): Could not evaluate: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Could not retrieve file metadata for puppet:///modules/myapp/sql/myfile.sql: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Fri Sep 17 09:37:22 -0600 2010 /File[/tmp/puppet_myapp/ARTIFACTS/DB/SCHEMA/anotherfile.sql] (err): Could not evaluate: end of file reached Could not retrieve file metadata for puppet:///modules/myapp/sql/anotherfile.sql: end of file reached
The SQL message above looks similar to the intermittent failures we always used to get using Puppet 0.25.4.
Fri Sep 17 14:03:54 -0600 2010 /Stage[main]/MyClass::Database/MyClass::Run_script[db.sh]/File[/tmp/puppet_myapp/db.sh]/content (err):
change from {md5}3d48bc877870f3d564f9d64bf6948e14 to {md5}ec516686434b2f783d6712deb016ef30 failed: end of file reached
Fri Sep 17 10:14:25 -0600 2010 /Stage[main]/Configs/File[/var/sadm/install/admin/puppet] (err): Could not evaluate: end of file reached Could not retrieve file metadata for puppet:///modules/configs/pkg.admin: end of file reached at /etc/opt/csw/puppet/modules/configs/manifests/init.pp:32
Tue Sep 21 14:34:46 -0600 2010 Puppet (err): Could not retrieve catalog from remote server: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Tue Sep 21 14:34:46 -0600 2010 Puppet (warning): Not using cache on failed catalog Tue Sep 21 14:34:46 -0600 2010 Puppet (err): Could not retrieve catalog; skipping run
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Accepted
- Target version set to 2.6.2
Updated by Paul Berry over 1 year ago
- Target version changed from 2.6.2 to 69
It looks like this is not going to make it into the 2.6.2 release.
Updated by Alan Harder over 1 year ago
Bummer.. well, we get several of these every day so let me know if there is any other debugging info we can collect.
Updated by Peter Meier over 1 year ago
I usually get this error when restarting the server while a client is currently waiting for a catalog compile.
Updated by Brice Figureau over 1 year ago
Alan Harder wrote:
Bummer.. well, we get several of these every day so let me know if there is any other debugging info we can collect.
It looks like the master drops the connection in the middle. Could it be a timeout settings in apache/nginx/whatever proxy you use? Could it be a network equipment somewhere that drop packets and the TCP connection ends dropped?
Updated by Alan Harder over 1 year ago
I asked our lab guys about it.. they have not seen dropped connections with other apps/tools. Nearly all of our clients are within this lab network; no proxies involved.
Updated by Alan Harder over 1 year ago
Updated by James Quacinella over 1 year ago
I too face this issue, and would be willing to get you any debug information that I can get. There doesn’t seem to be much of a pattern, and it only happens about once a day with about 12 servers checking in. Mostly with the same file but at random times and random machines. Both puppetd and puppetmasterd are at version 0.25.5 and I am not using any proxy in front of puppetmasterd.
Updated by John Arundel over 1 year ago
Same thing occurring for us (at least the SSL error messages). Client and server version 2.6.3 on Ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux] with webrick. Here’s the trace:
debug: Failed to load library 'selinux' for feature 'selinux' debug: Puppet::Type::User::ProviderLdap: true value when expecting false debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist 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: Failed to load library 'ldap' for feature 'ldap' debug: /File[/var/lib/puppet/ssl/crl.pem]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private]: 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/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/certs/admodamgmt.admoda.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet] debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/lib/puppet/state] debug: /File[/var/lib/puppet/state/state.yaml]: 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/ssl/private_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/public_keys/admodamgmt.admoda.com.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys] debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/private_keys/admodamgmt.admoda.com.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/puppet] debug: Finishing transaction 70028338148820 debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet] debug: /File[/var/lib/puppet/ssl/certs]: 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/ssl/certs/ca.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/ssl/private_keys/admodamgmt.admoda.com.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys] debug: /File[/var/lib/puppet/ssl/certificate_requests]: Autorequiring File[/var/lib/puppet/ssl] debug: /File[/var/lib/puppet/ssl/public_keys/admodamgmt.admoda.com.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/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/public_keys]: 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/certs/admodamgmt.admoda.com.pem]: Autorequiring File[/var/lib/puppet/ssl/certs] debug: Finishing transaction 70028337157260 debug: Using cached certificate for ca debug: Using cached certificate for admodamgmt.admoda.com debug: Finishing transaction 70028336774360 debug: Loaded state in 0.11 seconds debug: Executing '/etc/puppet/etckeeper-commit-pre' debug: Using cached certificate for ca debug: Using cached certificate for admodamgmt.admoda.com 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 admodamgmt.admoda.com debug: Puppet::Type::Package::ProviderUrpmi: file urpmi does not exist debug: Puppet::Type::Package::ProviderPkg: file /usr/bin/pkg does not exist debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/sbin/portinstall does not exist debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist debug: Puppet::Type::Package::ProviderHpux: file /usr/sbin/swinstall does not exist debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/eix-update does not exist debug: Puppet::Type::Package::ProviderYum: file yum does not exist debug: Puppet::Type::Package::ProviderFink: file /sw/bin/fink does not exist debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_delete does not exist debug: Puppet::Type::Package::ProviderNim: file /usr/sbin/nimclient does not exist debug: Puppet::Type::Package::ProviderAix: file /usr/bin/lslpp does not exist debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portupgrade does not exist debug: Puppet::Type::Package::ProviderSun: file /usr/sbin/pkgrm does not exist debug: Puppet::Type::Group::ProviderLdap: true value when expecting false debug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::Group::ProviderPw: file /usr/sbin/pw does not exist debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Puppet::Type::Service::ProviderLaunchd: file /bin/launchctl does not exist debug: Puppet::Type::Service::ProviderGentoo: file /sbin/rc-update does not exist debug: Puppet::Type::Service::ProviderDaemontools: file /usr/bin/svc does not exist debug: Puppet::Type::Service::ProviderRedhat: file /sbin/service does not exist debug: Puppet::Type::Service::ProviderRunit: file /usr/bin/sv does not exist debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw yaml; using pson debug: Executing '/etc/puppet/etckeeper-commit-post' /usr/lib/ruby/1.8/puppet/parameter.rb:171:in `fail' /usr/lib/ruby/1.8/puppet/type/file/source.rb:157:in `init_metadata' /usr/lib/ruby/1.8/puppet/type/file/source.rb:149:in `each' /usr/lib/ruby/1.8/puppet/type/file/source.rb:149:in `init_metadata' /usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `send' /usr/lib/ruby/1.8/puppet/util/cacher.rb:106:in `cached_value' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/1.8/puppet/util/cacher.rb:98:in `cached_value' /usr/lib/ruby/1.8/puppet/util/cacher.rb:48:in `metadata' /usr/lib/ruby/1.8/puppet/type/file/source.rb:116:in `copy_source_values' /usr/lib/ruby/1.8/puppet/type/file/source.rb:113:in `each' /usr/lib/ruby/1.8/puppet/type/file/source.rb:113:in `copy_source_values' /usr/lib/ruby/1.8/puppet/type/file.rb:632:in `retrieve' /usr/lib/ruby/1.8/puppet/type.rb:703:in `retrieve_resource' /usr/lib/ruby/1.8/puppet/type.rb:1861:in `to_trans' /usr/lib/ruby/1.8/puppet/type/file.rb:701:in `to_trans' /usr/lib/ruby/1.8/puppet/type.rb:1886:in `to_resource' /usr/lib/ruby/1.8/puppet/type.rb:203:in `uniqueness_key' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:83:in `add_resource' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:72:in `each' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:72:in `add_resource' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:561:in `to_catalog' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:531:in `each' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:531:in `to_catalog' /usr/lib/ruby/1.8/puppet/resource/catalog.rb:468:in `to_ral' /usr/lib/ruby/1.8/puppet/configurer.rb:117:in `convert_catalog' /usr/lib/ruby/1.8/puppet/configurer.rb:112:in `retrieve_catalog' /usr/lib/ruby/1.8/puppet/configurer.rb:143:in `run' /usr/lib/ruby/1.8/puppet/agent.rb:39 /usr/lib/ruby/1.8/puppet/agent/locker.rb:21:in `lock' /usr/lib/ruby/1.8/puppet/agent.rb:39 /usr/lib/ruby/1.8/sync.rb:230:in `synchronize' /usr/lib/ruby/1.8/puppet/agent.rb:39 /usr/lib/ruby/1.8/puppet/agent.rb:103:in `with_client' /usr/lib/ruby/1.8/puppet/agent.rb:37 /usr/lib/ruby/1.8/puppet/application.rb:171:in `call' /usr/lib/ruby/1.8/puppet/application.rb:171:in `controlled_run' /usr/lib/ruby/1.8/puppet/agent.rb:35:in `run' /usr/lib/ruby/1.8/puppet/application/agent.rb:114:in `onetime' /usr/lib/ruby/1.8/puppet/application/agent.rb:88:in `run_command' /usr/lib/ruby/1.8/puppet/application.rb:287:in `run' /usr/lib/ruby/1.8/puppet/application.rb:393:in `exit_on_fail' /usr/lib/ruby/1.8/puppet/application.rb:287:in `run' /usr/sbin/puppetd:4 err: Could not run Puppet configuration client: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A Could not retrieve file metadata for puppet:///user/john-authorized_keys: SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A at /etc/puppet/modules/user/manifests/virtual.pp:97
Updated by Nigel Kersten over 1 year ago
- Target version deleted (
69)