so is the client 25 and the server 24? I don't think that will work.

---
Thanks,

Allan Marcus
505-667-5666



On Oct 27, 2009, at 1:41 PM, Jason Antman wrote:

>
> I tried updating one of my clients today from 0.24.8 to the Git head
> from 2009-10-23. Unfortunately, I didn't know how imminent the  
> release was.
>
> In my client log, I'm seeing things like:
> [r...@ccf-hill019-12 log]# puppetd --no-daemonize --debug --test
> --verbose --server FOO
> 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::ProviderLdap: true value when expecting  
> false
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ 
> dscl
> does not exist
> debug: Failed to load library 'ldap' for feature 'ldap'
> debug: /File[/var/lib/puppet/ssl/csr_ccf-hill019-12.example.com.pem]:
> Autorequiring File[/var/lib/puppet/ssl]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/ 
> puppet]
> debug: /File[/var/lib/puppet/ssl/private_keys]: Autorequiring
> File[/var/lib/puppet/ssl]
> debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/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/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/facts]: Autorequiring File[/var/lib/ 
> puppet]
> debug:
> /File[/var/lib/puppet/ssl/private_keys/ccf- 
> hill019-12.example.com.pem]:
> Autorequiring File[/var/lib/puppet/ssl/private_keys]
> debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/ssl]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/log/puppet/http.log]: Autorequiring File[/var/log/ 
> puppet]
> debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/etc/puppet/namespaceauth.conf]: Autorequiring
> File[/etc/puppet]
> debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
> File[/var/lib/puppet/state]
> debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
> File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
> File[/var/lib/puppet]
> debug:
> /File[/var/lib/puppet/ssl/public_keys/ccf-hill019-12.example.com.pem]:
> Autorequiring File[/var/lib/puppet/ssl/public_keys]
> debug: /File[/var/lib/puppet/ssl/certs/ccf- 
> hill019-12.example.com.pem]:
> Autorequiring File[/var/lib/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/ssl/private]: Autorequiring
> File[/var/lib/puppet/ssl]
> debug: /File[/var/lib/puppet/ssl/certs]: Autorequiring
> File[/var/lib/puppet/ssl]
> debug: Finishing transaction -607050108 with 0 changes
> debug: Using cached certificate for ca
> debug: Using cached certificate for ccf-hill019-12.example.com
> debug: Loaded state in 0.00 seconds
> debug: Using cached certificate for ca
> debug: Using cached certificate for ccf-hill019-12.example.com
> debug: Format s not supported for Puppet::Resource::Catalog; has not
> implemented method 'from_s'
> debug: Puppet::Network::Format[json]: false value when expecting true
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> Is this bug 2617? I can't find many mentions of these errors.
>
> I noticed that it *may*/*should* be fixed in 0.25.1. Is that the  
> consensus?
>
> Thanks,
> Jason Antman
>
> >


--~--~---------~--~----~------------~-------~--~----~
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+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to