I am getting this error after installing puppet with gem$ gem install puppetFetching: facter-1.6.14.gem (100%)Fetching: puppet-3.0.1.gem (100%)Successfully installed facter-1.6.14Successfully installed puppet-3.0.12 gems installedInstalling 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.mdCould not find main page README.mdCould not find main page README.mdCould not find main page README.md$ puppet --versionError: Could not intialize global default settings: Error converting value for param 'factpath': Could not find value for $confdirgoogle search found this link and that is already fixed for this versionPlease advise.
--
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...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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.
What version(s) of facter are you running? Perhaps you have multiple
installed here as well? It seems strange that the trace you posted
references two distinct library paths,
e.g.
/usr/local/lib/site_ruby/1.8/facter and /usr/lib/ruby/vendor_ruby/facter
I did some clean up. Now I have only one version of puppet and facter.
On Tue, Nov 6, 2012 at 7:08 PM, Asif Iqbal <vad...@gmail.com> wrote:
I did some clean up. Now I have only one version of puppet and facter.It still seems like you could have stale files.Could you verify there are no stale files by pasting the output of this command?ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d| $LOAD_PATH.collect {|l| { l => Dir["#{l}/#{d}/**.rb"] }}}.to_yaml'
This will locate all of the puppet and facter libraries that are present along the ruby load path.Thanks,-Jeff
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Nov 7, 2012 at 4:18 PM, Jeff McCune <je...@puppetlabs.com> wrote:
On Tue, Nov 6, 2012 at 7:08 PM, Asif Iqbal <vad...@gmail.com> wrote:
I did some clean up. Now I have only one version of puppet and facter.It still seems like you could have stale files.Could you verify there are no stale files by pasting the output of this command?ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d| $LOAD_PATH.collect {|l| { l => Dir["#{l}/#{d}/**.rb"] }}}.to_yaml'
This will locate all of the puppet and facter libraries that are present along the ruby load path.Thanks,-Jeff--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@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?
yep, It does look like I have two different ruby
/usr/local/lib/site_ruby
ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d| $LOAD_PATH.collect {|l| { l => Dir["#{l}/#{d}/**/*.rb"] }}}.to_yaml'
Could you add --trace and --evaltrace to whatever command you're executing that gives the error, then paste the command and the output?
http://paste.ubuntu.com/1344430/On Thu, Nov 8, 2012 at 4:34 PM, Jeff McCune <je...@puppetlabs.com> wrote:
Could you add --trace and --evaltrace to whatever command you're executing that gives the error, then paste the command and the output?
--
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?
Thanks,
-Jeff
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Nov 14, 2012 at 6:18 PM, Jeff McCune <je...@puppetlabs.com> wrote:
On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal <vad...@gmail.com> wrote:These definitely seem like bugs. Could you please file a bug report
>
> Here is another simple one
>
> # puppet apply --trace --evaltrace -e 'user {"dummy": ensure => present}'
>
> http://paste.ubuntu.com/1344435/
at http://projects.puppetlabs.com/projects/puppet/issues/new with
these links, or copies of them in the ticket? If you add me as a
watcher, I'll try my best to get this resolved as quickly as we can.
It seems similar to #13429, but not the exact same problem.
submitted it in the bug and assigned it to you.thanks a lot for your help.
Thanks,
-Jeff
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@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?