On Jun 20, 2007, at 1:17 PM, Udo Waechter wrote:
> Hi all,
> I just stumbled over a huge rails.log in /var/log/puppet on the
> puppetmaster.
> It is full of DB statments which seems to point to the fact that
> puppetmaster''s rails environment is set to development.
>
> No problem, I thought, set the system''s RAILS_ENV to production
> make it
> available to the master daemon and restart it.
> Unfortunately, this does not work. I searched through the puppet files
> and on the mailing list but could not find any reference to this
> problem.
>
> Can someone tell me where and how to set puppets rails environment to
> production.
> The logfile gets really huge and is not necessary in a production
> environmnet. I currently redirect them to /dev/null but this is not a
> solution, since the strings are stillcreated by rails.
Huh. I can''t find any evidence that Puppet specifies an environment
anywhere, so Rails must be defaulting to ''development''.
I, um, frankly have no idea how to fix this. Anyone have any ideas?
--
The one thing more difficult than following a regimen is not
imposing it
on others. -- Marcel Proust
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com