similar to: Puppet Dashboard: db:migrate failure (1.2.2 to 1.2.4)

Thoughts? [root@ca-sna-pm01 config]# rake RAILS_ENV=production db:migrate (in /usr/share/puppet-dashboard) 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. config.gem: Unpacked gem rdoc-3.6.1 in vendor/gems has no

Hi All, I am a first time Ruby on Rails user/developer – and am having trouble setting it up on a web server. The hosting service I use is www.machighway.com. Rails version is 2.3.14, ruby version is 1.8.7. I tried following the tutorial at: http://guides.rubyonrails.org/v2.3.11/getting_started.html Except for the main page – all my pages are not returning anything. I would love it if

Hi all, I DONT KNOW WHAT IS THIS WHEN I RUN SERVER OR CONSOLE ITS COMMING. PLEASE ANYBODY TELME WHATS PROBLEM WHATS SOLLUTION rajesh@rajesh:~/workspace/apl$ ruby script/console Loading development environment (Rails 2.3.2) NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after 2011-11-01. Gem.source_index called from

hi All, I''m trying to install puppet-dashboard. When I start it: # /etc/init.d/puppet-dashboard start * Starting Puppet Dashboard 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/script/../config/../vendor/rails/railties/lib/rails/gem_dependency.rb:21. NOTE:

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

Hi I''m trying to configure Puppet-dashboard after installing Puppet from the open source package. But there was no issues when using the Enterprise package. Do you have any solutions for the below error? I''m trying to configure Puppet-dashboard. # rake RAILS_ENV=production db:migrate NOTE: Gem.source_index is deprecated, use Specification. It will be removed on or after

I''ve "inherited" the administration of a puppet-dashboard (version 1.1.0, installed on RHEL 5.6 from puppetlabs RPM), and have hit a problem I''m hoping for some help with. In short, one table, "resource_statuses" appears to be growing at a rate far higher then the other tables: mysql> select count(*) from nodes; +----------+ | count(*) | +----------+ |

I''m using puppet-dashboard 1.1.0-1 on Ubuntu. I remove old reports using this command: nice -n +1 rake RAILS_ENV=production reports:prune upto=1 unit=mon This seems to work fine, and the amount of reports returnd by this mysql query seems to drop by the proper amount: select count(*) from reports; Right now it returns a value of 12591. So far so good. The problem is the

Hi, This is the third or fourth time this happens. But puppetd gets a zombie shell childprocess and then never finishes the run. /opt/tc-puppet/bin/ruby /opt/tc-puppet/sbin/puppetd \_ [sh] <defunct> How do I begin looking on what can be wrong? This error has appeared on both 2.7.6 and 2.7.11. Regards, Elias -- You received this message because you are subscribed to the Google Groups

How would I convert this program to output exactly the same thing but only for all the (noop) operations. We keep puppet in noop mode to audit its actions before they are applied. Thus it is necessary to ensure we understand exactly what all the nodes noop operations would be if we listed the noop restriction for a normal apply. This program will report in a reasonable format for those non-noop

I recently upgraded a server''s rubygems from 0.9.0 to 1.2.0. Upon doing so, one of our apps that uses soap4r thinks all the security certificates it sees are invalid (see Error 1 below). I tried reverting to 0.9.0, but anything that uses rubygems crashes now (see Error 2 below). If anyone could help me solve either problem, that would be great. Ideally, I''d like to run the latest

Thanks for the help Sean. I managed to get the install fixed, but I''m still having problems. When I do mongrel_rails start, the process just gets stuck and never completes. If I interrupt it I get the following... ** Ruby version is not up-to-date; loading cgi_multipart_eof_fix /usr/lib/ruby/1.8/rubygems/source_index.rb:186:in `search'': Interrupt from

To install the ruby-augeas gem, I installed rubygems on Debian etch, which lead to: Setting up libgems-ruby1.8 (0.9.0-5) ... Setting up ruby1.8-dev (1.8.5-4etch4) ... Setting up rubygems (0.9.0-5) ... Before this (I mean *immediately* before this) puppet worked fine exceept for not being able to find a provider for Augeas. After this, though: ec2-www1:/usr/src# puppetd -t Failed to load

I keep getting this when I try to start the server: [Macintosh:rails/work/demo] jslicari% script/server /Library/Ruby/Site/1.8/rubygems.rb:723:in `set_paths'': uninitialized constant Gem::Etc (NameError) from /Library/Ruby/Site/1.8/rubygems.rb:719:in `each'' from /Library/Ruby/Site/1.8/rubygems.rb:719:in `set_paths'' from /Library/Ruby/Site/1.8/rubygems.rb:526:in

I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem

Hello group! I was working with puppetmaster 0.24 but I try to install the 2.6 version from source; that work fine but I can''t revert the installation. I want to revert to 0.24 because I have more that 100 host with 0.24 clients. I run Debian 5 "Lenny". This is the error: Restarting puppet master/usr/local/lib/site_ruby/1.8/rubygems.rb:419:in `dir'': undefined

We''re deploying mongrel with Apache on CentOS. I have installed mongrel but when I try to run it, I get the following error. Can someone tell my why and how to fix it. Also does anyone have experience in deploying mongrel on CentOS ? mongrel_rails start -d /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load -- (LoadError)

Dear All! I''ve set up my apache, passenger and configs, the passenger works, but the app can''t be started. the erros are the following These are the possible causes: * There may be a syntax error in the application''s code. Please check for such errors and fix them. * A required library may not installed. Please install all libraries that this

We''re deploying mongrel with Apache on CentOS. I have installed mongrel but when I try to run it, I get the following error. Can someone tell my why and how to fix it. Also does anyone have experience in deploying mongrel on CentOS ? mongrel_rails start -d /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load -- (LoadError)

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''