Re: [Puppet Users] Re: puppet failing to run
On Wed, Nov 14, 2012 at 6:18 PM, Jeff McCune j...@puppetlabs.com wrote:
On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal vad...@gmail.com wrote:
Here is another simple one
# puppet apply --trace --evaltrace -e 'user {dummy: ensure =
present}'
http://paste.ubuntu.com/1344435/
These definitely seem like bugs. Could you please file a bug report
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-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.
Re: [Puppet Users] Re: puppet failing to run
On Fri, Nov 9, 2012 at 12:11 AM, Asif Iqbal vad...@gmail.com wrote:
Here is another simple one
# puppet apply --trace --evaltrace -e 'user {dummy: ensure = present}'
http://paste.ubuntu.com/1344435/
These definitely seem like bugs. Could you please file a bug report
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.
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-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.
Re: [Puppet Users] Re: puppet failing to run
On Wed, Nov 7, 2012 at 6:55 PM, Asif Iqbal vad...@gmail.com wrote:
yep, It does look like I have two different ruby
Not necessarily, these are just all of the directories a single ruby
executable will look to when trying to load *.rb files using the 'require'
statement.
/usr/local/lib/site_ruby
Looking at the output you pasted, it doesn't look like Puppet is anywhere
on your system except inside of /usr/lib/ruby/vendor_ruby/puppet/
I do have a minor typo though. The command is only searching the top level
of the Puppet tree, not all subdirectories. Could you try this final
command to verify there's only one copy of Puppet and Facter?
ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d| $LOAD_PATH.collect
{|l| { l = Dir[#{l}/#{d}/**/*.rb] }}}.to_yaml'
(Note the /**/*.rb instead of the plain /*.rb)
-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-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.
Re: [Puppet Users] Re: puppet failing to run
On Thu, Nov 8, 2012 at 12:43 PM, Jeff McCune j...@puppetlabs.com wrote:
ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d|
$LOAD_PATH.collect {|l| { l = Dir[#{l}/#{d}/**/*.rb] }}}.to_yaml'
http://paste.ubuntu.com/1343465/
--
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.
Re: [Puppet Users] Re: puppet failing to run
OK, this definitely looks like a problem with Puppet.
Could you add --trace and --evaltrace to whatever command you're executing
that gives the error, then paste the command and the output?
Thanks,
-Jeff
On Thu, Nov 8, 2012 at 12:12 PM, Asif Iqbal vad...@gmail.com wrote:
On Thu, Nov 8, 2012 at 12:43 PM, Jeff McCune j...@puppetlabs.com wrote:
ruby -r puppet -e 'puts %w{ puppet facter }.collect {|d|
$LOAD_PATH.collect {|l| { l = Dir[#{l}/#{d}/**/*.rb] }}}.to_yaml'
http://paste.ubuntu.com/1343465/
--
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.
Re: [Puppet Users] Re: puppet failing to run
On Thu, Nov 8, 2012 at 4:34 PM, Jeff McCune j...@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? http://paste.ubuntu.com/1344430/ -- 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.
Re: [Puppet Users] Re: puppet failing to run
On Fri, Nov 9, 2012 at 12:08 AM, Asif Iqbal vad...@gmail.com wrote:
On Thu, Nov 8, 2012 at 4:34 PM, Jeff McCune j...@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?
http://paste.ubuntu.com/1344430/
Here is another simple one
# puppet apply --trace --evaltrace -e 'user {dummy: ensure = present}'
http://paste.ubuntu.com/1344435/
--
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.
Re: [Puppet Users] Re: puppet failing to run
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-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.
Re: [Puppet Users] Re: puppet failing to run
On Wed, Nov 7, 2012 at 4:18 PM, Jeff McCune j...@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'
http://paste.ubuntu.com/1341582/
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-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.
Re: [Puppet Users] Re: puppet failing to run
On Wed, Nov 7, 2012 at 9:51 PM, Asif Iqbal vad...@gmail.com wrote:
On Wed, Nov 7, 2012 at 4:18 PM, Jeff McCune j...@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'
http://paste.ubuntu.com/1341582/
yep, It does look like I have two different ruby
/usr/local/lib/site_ruby
and
/usr/lib/ruby
the /usr/local/ one does not match to any ubuntu apt. I can remove that if
necessary.
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-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?
--
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.
Re: [Puppet Users] Re: puppet failing to run
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. -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.
Re: [Puppet Users] Re: puppet failing to run
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
Re: [Puppet Users] Re: puppet failing to run
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
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
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,
Re: [Puppet Users] Re: puppet failing to run
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com wrote:
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
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
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
Re: [Puppet Users] Re: puppet failing to run
It looks to me as if there are at least two facters installed. One was
likely installed using install.rb (probably the one in
/usr/local/lib/site_ruby), and another was installed using the package
manager. Can you post the output of both `dpkg -S facter` and `dpkg -l
facter`? That will show which was installed via source and which one
was installed using apt.
On Tue, Nov 6, 2012 at 4:57 PM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com wrote:
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
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
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
Re: [Puppet Users] Re: puppet failing to run
I did some clean up. Now I have only one version of puppet and facter.
$ dpkg -S facter
http://paste.ubuntu.com/1338890/
$ dpkg -l facter
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=-=-==
ii facter1.6.14-1puppetlabs1 Ruby module for collecting
simple facts about a host opera
$ dpkg -L facter
http://paste.ubuntu.com/1338889/
$ puppet apply ldap.pp
Error: Could not intialize global default settings: Error converting value
for param 'factpath': Could not find value for $confdir
$ cat ldap.pp
class { pam_ldap: }
On Tue, Nov 6, 2012 at 9:55 PM, Matthaus Owens matth...@puppetlabs.comwrote:
It looks to me as if there are at least two facters installed. One was
likely installed using install.rb (probably the one in
/usr/local/lib/site_ruby), and another was installed using the package
manager. Can you post the output of both `dpkg -S facter` and `dpkg -l
facter`? That will show which was installed via source and which one
was installed using apt.
On Tue, Nov 6, 2012 at 4:57 PM, Asif Iqbal vad...@gmail.com wrote:
On Tue, Nov 6, 2012 at 7:11 PM, Moses Mendoza mo...@puppetlabs.com
wrote:
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
$ facter --version
1.5.8
On Tue, Nov 6, 2012 at 11:19 AM, Asif Iqbal vad...@gmail.com wrote:
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
