[Puppet Users] Re: Configuring hosts with data from other hosts
Ive struggled with the same problem of distributing variables and other generated data amongst hosts. For external resources Ive found a great use in configuring a BackupPC server. Each node builds their backup configuration file with tag 'backuppc_server_conf' and the server retrieves all the generated files with that tag. What I havent been unable to solve, is making each nodes hiera values accessable to each other. My hierarchy is $fqdn-common. The very crude workaround Ive used is in a module, query foreman for all fqdn's. Then pass that to a define that 'redefines' fqdn variable before calling hiera. Is there alternatively a way to query resources like all mysql::db types? I would like to just get all the mysql::db instances on a given node so other nodes could use that data. This could be another way to configure backuppc or generate monitoring checks. - Trey -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/5a1FTfRCFSsJ. 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 client could not request certificate: Error 500 on SERVER
I am seriously thinking of putting those recursive chown's in root crontab on
puppet masters and puppet agents for /etc/puppet* and
/var/lib/puppet*
I shouldn't have to do this but have
seen cases of ownership reversion.
--Stuart
Via Apple iPhone 4S on the ATT Wireless Network
On Aug 13, 2012, at 3:04 AM, Frederik Vos inktvi...@gmail.com wrote:
For the people still looking for an answer:
chown -R puppet:puppet /var/lib/puppet/reports
Op woensdag 30 maart 2011 21:02:43 UTC+2 schreef hyzhang het volgende:
Thank. I am pasting the entire message here:
Mar 30 14:01:04 puppetclient1 puppet-agent[28571]: Could not request
certificate: Error 500 on SERVER: !DOCTYPE HTML PUBLIC -//W3C//DTD
HTML 4.01//EN http://www.w3.org/TR/html4/strict.dtd; html
head meta http-equiv=Content-Type content=text/html;
charset=UTF-8 meta name=generator content=Phusion
Passenger titleRuby (Rack) application could not be started/
title style type=text/css body { font-
family: Verdana, 'Bitstream Vera Sans', Arial, Sans-Serif;
font-size: 10pt;background: white; color:
#22; margin: 0; padding-top: 3em; padding-
bottom: 3em;padding-left: 4.5em;padding-right: 4.5em; } h1
{ font-size: 17pt;font-weight: medium;color:
#533e72; border-bottom: 1px solid #533e72; } h1.title
{ margin-top: 0; } h1.error_title { color: red;
border-bottom: 1px solid red; } a {text-decoration: none; }
a:hover { text-decoration: underline; } dt { font-weight:
bold; color: #280050; } dd { margin-top: 0.5em;
margin-bottom: 1em; } .commands { border: 1px
Somehow I am able to get the certificate for the client. Since above
error message says Ruby (Rack) application could not be started, I
did
#rackup /usr/share/puppet/rack/puppetmasterd/config.ru
Then I see the rack process on puppet server
#ps -ef|grep rack
puppet 27140 1 0 14:21 ?00:00:00 Rack: /usr/share/
puppet/rack/puppetmasterd
From then on the server is able to receive the client certificate
request and sign it.
Do I have to start the rack manually in a manner like that? I thought
if I start httpd service, it would start rack automatically.
I am still not sure if I did everything right.
Thanks,
-Haiyan
On Mar 30, 2:38 pm, Hugo Cisneiros (Eitch)
hugo.cisnei...@gmail.com wrote:
On Wed, Mar 30, 2011 at 3:00 PM, hyzhang hyzh...@jcvi.org wrote:
Hi, I am new to puppet.
I have puppet server set up with passenger. But when I start puppetd
from client, I see following error in the syslog file:
Mar 30 13:52:03 puppetclient1 puppet-agent[29732]: Could not request
certificate: Error 500 on SERVER: !DOCTYPE HTML PUBLIC -//W3C//DTD
HTML 4.01//EN http://www.w3.org/TR/html4/strict.dtd; html
head meta http-equiv=Content-Type content=text/html;
charset=UTF-8 meta name=generator content=Phusion
Passenger titleRuby (Rack) application could not be started/
title
You didn't paste the most important part of the error. Thie page ruby/rack
generates usually have some pretty useful information in an error field.
Like a module missing on an import/require, permission problems, and so on.
Please identify and post the error so we can be helpful :)
--
[]'s
Hugowww.devin.com.br
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/ltKL6JvCWQEJ.
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: merging iptables rules with puppet
I have been meaning to have a look at that one and see if it will work for what I need. I have likely put it off because I am always too busy and my firewall module works. I also like having the rules go away automagically if they aren't needed any more. On 17 August 2012 05:27, Justin Ellison jus...@techadvise.com wrote: I can't say enough good about the puppetlabs-firewall module. They've put a lot of work into it, and it works perfectly. https://github.com/puppetlabs/puppetlabs-firewall No need for concat here. Justin On Thursday, August 16, 2012 1:01:01 AM UTC-5, Pete wrote: Hi, I manage my iptables setup with the concat module and nail together a rules file and then reload it if it's changed I also have a define setup so other classes can define rules and my firewall class pulls them all in. works well for me because when i remove a class the firewall rull associated with it goes away too. I am intending on putting my modules in githib but have been super busy and haven't had a chance yet. On 16 August 2012 07:07, Geoff Galitz gga...@shutterstock.com wrote: We are executing iptables rule, not editing the backend files, though we could do that if that were the only option. -G On Wed, Aug 15, 2012 at 4:54 PM, Luke Baker bak...@missouri.edu wrote: By dynamically loading rules do you mean executing iptables rule or are you editing your iptables-save file and then reloading? On Wednesday, August 15, 2012 1:48:44 PM UTC-5, Geoff Galitz wrote: I'm still a bit noobish with puppet... In short what I want to do is merge puppet managed iptables with dynamically added rules added by some scripts. We have a basic config setup with a template (iptables.erb) and we can add rules to that in manifests. But of course puppet will wipe any changes made from the OS. Any advice on how to get puppet to respect the dynamically loaded rules? Thanks. -G -- --- Geoff Galitz, gga...@shutterstock.com WebOps Shutterstock Images -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/VX2Sj8i2-ssJ. 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. -- --- Geoff Galitz, gga...@shutterstock.com WebOps Shutterstock Images -- 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. -- You received this message because you are subscribed to the Google Groups Puppet Users group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/2RiSuyvxkAwJ. 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.
[Puppet Users] Re: Installing puppet-dashboard on ubuntu precise
Hi Daniele, Yeah you are probably right. I can't uninstall the other one as it is a dependance on mod-passenger. I'm not really familiar with ruby, Is there a way I can override the search path? I don't have RUBYLIBDIR set in my environment. Cheers, Sam On Friday, 17 August 2012 17:41:49 UTC+10, Daniele Sluijters wrote: Hi, Are you sure there's no rack 1.3.5 somewhere around your system? If there is it is probably found in the $RUBYLIBDIR path before the one installed from gem so you're still seeing the error. If not, then it's getting interesting... -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from
Re: [Puppet Users] Re: Installing puppet-dashboard on ubuntu precise
Hi Sam, I would rather suggest uninstalling mod-passenger and then do a fresh install, rather going into all this mess.. Regards, System Admin Ashish Jaiswal On Monday 20 August 2012 07:03:54 AM IST, Sam Morrison wrote: Hi Daniele, Yeah you are probably right. I can't uninstall the other one as it is a dependance on mod-passenger. I'm not really familiar with ruby, Is there a way I can override the search path? I don't have RUBYLIBDIR set in my environment. Cheers, Sam On Friday, 17 August 2012 17:41:49 UTC+10, Daniele Sluijters wrote: Hi, Are you sure there's no rack 1.3.5 somewhere around your system? If there is it is probably found in the $RUBYLIBDIR path before the one installed from gem so you're still seeing the error. If not, then it's getting interesting... -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from
[Puppet Users] Dynamic Lookup of facter variable.
I don't get it...
if ! ( $ec2_instance_type in [$ec2_inst_type_allow]) {
notice(NOT ALLOWED)
} else {
notice(ALLOWED)
}
2012-08-20T02:39:10.537134+00:00 truth puppet-master[24080]: Dynamic
lookup of $ec2_instance_type at /truth/sauce/env/prod/modules/rol
e/manifests/validate_server.pp:12 is deprecated. Support will be
removed in Puppet 2.8. Use a fully-qualified variable name (e.g., $
classname::variable) or parameterized classes.
Line 12 is the if statement. However, on the same client system...
[us1:i-16c5c050] root@testweb11:~# facter | grep ec2_instance_type
ec2_instance_type = m1.large
It's a facter variable. What's it complaining about?
Doug.
--
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] Dynamic Lookup of facter variable.
Facts exist at top scope, as indicated in the scoping doc several people have
referred you to on this list. Use $::ec2_instance_type
Sent from my iPad
On Aug 19, 2012, at 10:44 PM, Douglas Garstang doug.garst...@gmail.com wrote:
I don't get it...
if ! ( $ec2_instance_type in [$ec2_inst_type_allow]) {
notice(NOT ALLOWED)
} else {
notice(ALLOWED)
}
2012-08-20T02:39:10.537134+00:00 truth puppet-master[24080]: Dynamic
lookup of $ec2_instance_type at /truth/sauce/env/prod/modules/rol
e/manifests/validate_server.pp:12 is deprecated. Support will be
removed in Puppet 2.8. Use a fully-qualified variable name (e.g., $
classname::variable) or parameterized classes.
Line 12 is the if statement. However, on the same client system...
[us1:i-16c5c050] root@testweb11:~# facter | grep ec2_instance_type
ec2_instance_type = m1.large
It's a facter variable. What's it complaining about?
Doug.
--
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] Dynamic Lookup of facter variable.
Oh god that's ugly.
On Sun, Aug 19, 2012 at 7:48 PM, Eric Shamow e...@puppetlabs.com wrote:
Facts exist at top scope, as indicated in the scoping doc several people have
referred you to on this list. Use $::ec2_instance_type
Sent from my iPad
On Aug 19, 2012, at 10:44 PM, Douglas Garstang doug.garst...@gmail.com
wrote:
I don't get it...
if ! ( $ec2_instance_type in [$ec2_inst_type_allow]) {
notice(NOT ALLOWED)
} else {
notice(ALLOWED)
}
2012-08-20T02:39:10.537134+00:00 truth puppet-master[24080]: Dynamic
lookup of $ec2_instance_type at /truth/sauce/env/prod/modules/rol
e/manifests/validate_server.pp:12 is deprecated. Support will be
removed in Puppet 2.8. Use a fully-qualified variable name (e.g., $
classname::variable) or parameterized classes.
Line 12 is the if statement. However, on the same client system...
[us1:i-16c5c050] root@testweb11:~# facter | grep ec2_instance_type
ec2_instance_type = m1.large
It's a facter variable. What's it complaining about?
Doug.
--
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.
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: doug.garst...@gmail.com
Cell: +1-805-340-5627
--
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: Installing puppet-dashboard on ubuntu precise
I'd rather not do that as mod-passenger is needed by something else (puppetmaster) Is there no way I can make dashboard use the gem version as opposed to the standard one? Is that what RUBYLIBDIR is for? Cheers, Sam On Monday, 20 August 2012 11:43:11 UTC+10, Ashish Jaiswal wrote: Hi Sam, I would rather suggest uninstalling mod-passenger and then do a fresh install, rather going into all this mess.. Regards, System Admin Ashish Jaiswal On Monday 20 August 2012 07:03:54 AM IST, Sam Morrison wrote: Hi Daniele, Yeah you are probably right. I can't uninstall the other one as it is a dependance on mod-passenger. I'm not really familiar with ruby, Is there a way I can override the search path? I don't have RUBYLIBDIR set in my environment. Cheers, Sam On Friday, 17 August 2012 17:41:49 UTC+10, Daniele Sluijters wrote: Hi, Are you sure there's no rack 1.3.5 somewhere around your system? If there is it is probably found in the $RUBYLIBDIR path before the one installed from gem so you're still seeing the error. If not, then it's getting interesting... -- Daniele Sluijters On Wednesday, 15 August 2012 07:17:38 UTC+2, Sam Morrison wrote: Hi, I'm trying to install dashboard on precise and I get the below error. I'm using the latest version that is available in the puppet apt repository. The package rdoc is installed (it's just a virtual package pointing to ruby) Are there some other missing dependencies that the package doesn't specify? I don't know ruby that well so finding it hard to debug. Also it's well after 2011-11-01 is that a problem too? Thanks, Sam root@admin:/usr/share/puppet-dashboard# rake RAILS_ENV=production db:migrate --trace NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE: Gem::SourceIndex#initialize is deprecated with no replacement. It will be removed on or after 2011-11-01. Gem::SourceIndex#initialize called from /usr/share/puppet-dashboard/config/../vendor/rails/railties/lib/rails/vendor_gem_source_index.rb:100. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It will be removed on or after 2011-11-01. Gem::SourceIndex#add_spec called from /usr/lib/ruby/vendor_ruby/1.8/rubygems/source_index.rb:91. NOTE: Gem::SourceIndex#add_spec is deprecated, use Specification.add_spec. It
