Foreman

{{toc}}

h1. rake aborted!

I get the following error while running rake db:migrate

<pre>

rake aborted!

undefined method `reenable' for <Rake::Task db:schema:dump => [environment]>:Rake::Task

</pre>

this means you have an old version of rake (older than 0.87), you can verify it by typing:

<pre>

rake --version

</pre>

Usually this error is "safe" to ignore, however, it is recommended to upgrade to rake >= 0.87

h1. I use puppet enterprise, what now?

As of PE version 1.0, foreman won't install easily without a few modifications.  Since PE ships with its own version of Ruby you will need to install a few gems.

Basically you need to tell foreman to use the PE provided ruby library instead.  Your not required to run the puppet version of ruby either as many distros now ship with ruby 1.8.7.

# You first need to install the pe-ruby-devel package that ships with PE.  You can find this in your packages folder wherever you extracted PE.

      a. rpm -ivh pe-ruby-devel-1.8.7.302-1.el5.i386.rpm 

# Update your path variable to use the ruby version PE ships with (export PATH=/opt/puppet/bin:$PATH)

# Check to make sure your PATH was updated ("which gem" should return /opt/puppet/bin/gem)

# gem install json

# gem install rest-client

(install the gem database driver you use)

# gem install sqlite3 or gem install mysql  ( you may have additional dependencies that would need to be resolved first)

Some of the gem dependencies can be resolved by installing the development library for that package (example: mysql-devel)

I found it difficult to install the sqlite3 gem because of dependency hell so I just setup mysql instead which was far easier to setup.  Additionally mysql is much more scalable than sqlite.

You can get a list of the currently installed gems by using: gem list.

If your running the foreman init script or /etc/sysconfig/foreman configuration file.  You may need to update apache/passenger configurations that point to the PE ruby version.

h1. error: Entry 'some file' not uptodate. Cannot merge.

If you downloaded Foreman from source (git), it could be that some of the files you have modified (or were modified automatically) conflicts with another file Foreman wants to upgrade.

If you don't think that you edited this file (e.g. db/schema.rb) it is usually safe to do:

<pre>

git checkout 'some file'

</pre> 

This will revert the file to its previous condition (as in the repo at the time of checkout) and now you should be able to get the latest version by:

<pre>

git pull

</pre>

h1. Strange errors with passenger

Passenger executes foreman, based on the owner of the config/environmnets.rb file, make sure that this use can actually access:

* puppet configuration files

* sqlite database (if using sqlite)

* write to log, tmp directories

see source:extras/puppet/foreman for complete puppet based setup for Foreman.

h1. error: Could not send facts to Foreman: wrong Content-Length format (RuntimeError)

You might see this error if you run the HTTP push facts script or the sample external nodes script.

This is most likely due to older version of the mongrel gem. Please try and update your gems.

<pre>

gem update mongrel

</pre>

h1. Is my Foreman instance running?

There is simple status service that returns JSON with "result" message "ok" when the instance is up and running. It also "pings" database and returns lag. Example:

<pre>

$ curl -k -H "Accept: application/json" http://instance:3000/status

{"status":200,"result":"ok","db_duration_ms":"5"}

</pre>

h1. How do I enable debugging?

Edit config/environments/production.rb and uncomment "config.log_level = :debug"

h1. [[Unattended Provisioning Troubleshooting]]

h1. Puppet and Storeconfigs: err: Could not retrieve catalog from remote server: Error 400 on SERVER: stack level too deep

Your activerecord Version is to new, you need activrecord 3.0.10 see http://projects.puppetlabs.com/issues/9290

<pre>

gem uninstall activerecord

gem install activerecord -v 3.0.10

</pre>

h1. How do I fix this error: "Unable to find directory $confdir/environments/$environment/modules in environment master" ?

If you've followed http://docs.puppetlabs.com/guides/environment.html#configuring-environments-on-the-puppet-master to 

create a multi-environment puppet configuration, you're initial rake may look something like this:

<pre>

rake puppet:import:puppet_classes RAILS_ENV=production

(in /usr/share/foreman)

Evaluating possible changes to your installation

Problems were detected during the evaluation phase

Unable to find directory $confdir/environments/$environment/modules in environment master

Please fix these issues and try again

</pre>

This is because Foreman does not currently evaluate $confdir.  There is a feature request open on this issue.  In the 

meantime, hard code your $confdir in your puppet.conf.

h1. How do I fix the puppet class import problem with multiple puppet environment ?

If Foreman don't seems to be aware of all your environment and is able to import only your "production" environment (see http://theforeman.org/issues/1159),

try to add ":puppetconfdir: /etc/puppet/puppet.conf" in your settings.yaml.

h1. Unable to connect to Hypervisor?

Make sure the user that's actually running foreman can connect to your remote hypervisor (for instance by running sudo -u foreman virsh -c qemu+ssh://root@<host>/session list).

If you are running foreman through phusion passenger, ps auxwwf | grep "R[a]ils: /usr/share/foreman" | awk '{ print $1 }' will give you the user that's running foreman. If you find that it's not being run by foreman, do the following:

cd ~foreman

chown foreman config/environment.rb

touch ~foreman/tmp/restart.txt