On Tue, Nov 6, 2012 at 1:14 PM, Jeff McCune <j...@puppetlabs.com> wrote:
> Did you have a version of Puppet on this system previously? This
> definitely seems like a bug, but it seems like one that only manifests if
> there's some other copy of Puppet that is also being loaded along with the
> version you expect.
>
>
There was a puppet 2.6.8 before and it was failing horribly with all kind
of ruby file missing.
So I installed this version using gem. Now I removed gem version puppet to
get the puppet 2.6.8 back
Now puppet version works again
$ puppet --version
2.6.8
But it does not help with this manifest
$ cat ldap.pp
class { "pam_ldap": }
$ puppet apply ldap.pp
/usr/lib/ruby/vendor_ruby/facter/virtual.rb:168: undefined method
`has_weight' for #<Facter::Util::Resolution:0x7f55970a3748> (NoMethodError)
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `instance_eval'
from /usr/local/lib/site_ruby/1.8/facter/util/fact.rb:38:in `add'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:35:in `add'
from /usr/local/lib/site_ruby/1.8/facter.rb:105:in `add'
from /usr/lib/ruby/vendor_ruby/facter/virtual.rb:167
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:73:in `load_file'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:38:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:33:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `each'
from /usr/local/lib/site_ruby/1.8/facter/util/loader.rb:30:in `load_all'
from /usr/local/lib/site_ruby/1.8/facter/util/collection.rb:90:in
`load_all'
from /usr/local/lib/site_ruby/1.8/facter.rb:95:in `to_hash'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/facts/facter.rb:71:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector/indirection.rb:188:in
`find'
from /usr/local/lib/site_ruby/1.8/puppet/indirector.rb:50:in `find'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:88:in `main'
from /usr/local/lib/site_ruby/1.8/puppet/application/apply.rb:35:in
`run_command'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:420:in `hook'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:411:in
`exit_on_fail'
from /usr/local/lib/site_ruby/1.8/puppet/application.rb:305:in `run'
from /usr/local/lib/site_ruby/1.8/puppet/util/command_line.rb:62:in
`execute'
from /usr/bin/puppet:4
-Jeff
>
>
> On Tue, Nov 6, 2012 at 9:20 AM, Asif Iqbal <vad...@gmail.com> wrote:
>
>> On Tue, Nov 6, 2012 at 11:31 AM, Asif Iqbal <vad...@gmail.com> wrote:
>>
>>> I am getting this error after installing puppet with gem
>>>
>>> $ gem install puppet
>>> Fetching: facter-1.6.14.gem (100%)
>>> Fetching: puppet-3.0.1.gem (100%)
>>> Successfully installed facter-1.6.14
>>> Successfully installed puppet-3.0.1
>>> 2 gems installed
>>> Installing ri documentation for facter-1.6.14...
>>> Installing ri documentation for puppet-3.0.1...
>>> Installing RDoc documentation for facter-1.6.14...
>>> Installing RDoc documentation for puppet-3.0.1...
>>> Could not find main page README.md
>>> Could not find main page README.md
>>> Could not find main page README.md
>>> Could not find main page README.md
>>>
>>> $ puppet --version
>>> Error: Could not intialize global default settings: Error converting
>>> value for param 'factpath': Could not find value for $confdir
>>>
>>> google search found this link and that is already fixed for this version
>>>
>>> https://github.com/puppetlabs/puppet/pull/750
>>>
>>>
>>> Please advise.
>>>
>>>
>> I am on Ubuntu 12.04.1 LTS 64bit server and gem version is 1.8.24
>>
>> --
>>> Asif Iqbal
>>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>> A: Because it messes up the order in which people normally read text.
>>> Q: Why is top-posting such a bad thing?
>>>
>>>
>>>
>>
>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>>
>>
>> --
>> 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.
>>
>
> --
> 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.
>
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
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.
