Hi, i experienced this on 1.0.1, but find a workaround, yesterday we
finally upgraded our Foreman to 1.1.1 and again during Cron run i receive :
rake aborted!
uninitialized constant Rake:DSL
/usr/share/foreman/Rakefile:3
(See full trace by running task with --trace)
and one more strange thing - on the statistics page - i have all the
information besides class distribution.
We are using Debian Squeeze 64bit and Nginx + Passenger, Shared database
with Puppet.
BTW, is there an option to extract sensitive data and migrate to separate
database?
Thank you in advance.
> Hi, i experienced this on 1.0.1, but find a workaround, yesterday we
> finally upgraded our Foreman to 1.1.1 and again during Cron run i receive :
>
> rake aborted!
> uninitialized constant Rake:DSL
> /usr/share/foreman/Rakefile:3
> (See full trace by running task with --trace)
>
What command is being executed, and what's the output with --trace
> and one more strange thing - on the statistics page - i have all the
> information besides class distribution.
>
> We are using Debian Squeeze 64bit and Nginx + Passenger, Shared database
> with Puppet.
> BTW, is there an option to extract sensitive data and migrate to separate
> database?
>
There was a discussion on separating the databases yesterday, see:
https://groups.google.com/d/msg/foreman-users/QE_1i-cG0LI/zUtGRvOSa5kJ
Greg
···
On 28 March 2013 06:08, Andrei Burd wrote:
Hi Greg,
Looks like i was using the old cron:
cd /usr/share/foreman; rake reports:expire days=7 RAILS_ENV="production"
but now when I"m running
cd /usr/share/foreman && bundle exec /usr/bin/rake reports:expire
i receive rake aborted!
development database is not configured
Tasks: TOP => reports:expire => environment
(See full trace by running task with --trace)
About separating DB, we were thinking about it, hope we will split it soon.
···
On Thursday, March 28, 2013 12:52:09 PM UTC+2, Greg Sutcliffe wrote:
>
> On 28 March 2013 06:08, Andrei Burd <burda...@gmail.com >wrote:
>
>> Hi, i experienced this on 1.0.1, but find a workaround, yesterday we
>> finally upgraded our Foreman to 1.1.1 and again during Cron run i receive :
>>
>> rake aborted!
>> uninitialized constant Rake:DSL
>> /usr/share/foreman/Rakefile:3
>> (See full trace by running task with --trace)
>>
>
> What command is being executed, and what's the output with --trace
>
>
>> and one more strange thing - on the statistics page - i have all the
>> information besides class distribution.
>>
>> We are using Debian Squeeze 64bit and Nginx + Passenger, Shared database
>> with Puppet.
>> BTW, is there an option to extract sensitive data and migrate to separate
>> database?
>>
>
> There was a discussion on separating the databases yesterday, see:
> https://groups.google.com/d/msg/foreman-users/QE_1i-cG0LI/zUtGRvOSa5kJ
>
> Greg
>
You forgot the rails_env 
cd /usr/share/foreman && bundle exec /usr/bin/rake
reports:expire RAILS_ENV=production
Greg
···
On 28 March 2013 11:01, Andrei Burd wrote:
Hi Greg,
Looks like i was using the old cron:
cd /usr/share/foreman; rake reports:expire days=7 RAILS_ENV=“production”
but now when I"m running
cd /usr/share/foreman && bundle exec /usr/bin/rake reports:expire
i receive rake aborted!
development database is not configured
Time for a coffee brake =) This one is on me.
Thanks.
···
On Thursday, March 28, 2013 1:51:05 PM UTC+2, Greg Sutcliffe wrote:
>
> On 28 March 2013 11:01, Andrei Burd <burda...@gmail.com >wrote:
>
>> Hi Greg,
>>
>> Looks like i was using the old cron:
>> cd /usr/share/foreman; rake reports:expire days=7 RAILS_ENV="production"
>>
>>
>> but now when I"m running
>> cd /usr/share/foreman && bundle exec /usr/bin/rake reports:expire
>> i receive rake aborted!
>> development database is not configured
>>
>
> You forgot the rails_env ;)
>
> cd /usr/share/foreman && bundle exec /usr/bin/rake
> reports:expire RAILS_ENV=production
>
> Greg
>