[foreman-dev] Errr dureing installation - Erro durante instalação do foreman.

2017-05-11 Thread Gerrard Netto
Alguém poderia me ajudar? Durante a instalação do foreman+Puppet, no CentOS, após executar o foreman-installer apareceram estes erros: Could not set home on user[foreman]: Execution of '/usr/sbin/usermod -d /usr/share/foreman foreman' returned 8: usermod: user foreman is currently used by

Re: [foreman-dev] Re: Revert removal of @host.params for host_param

2017-05-11 Thread Daniel Lobato
Right now 1.15 is released. I decided not to document the deprecation as the consensus seems to maintain both ways of addressing this. The deprecations are still going to show up in the logs, so I suggest someone submits a PR to remove the deprecations and cherry-pick it for 1.15.1

Re: [foreman-dev] Re: 1.15.0 release status

2017-05-11 Thread Daniel Lobato
Thanks - all packages are out now, freight cache needs to be updated by someone with access to deb.theforeman.org, see the steps in: http://projects.theforeman.org/projects/foreman/wiki/Release_Process#Completion-tasks Similarly, those who have permissions please update Twitter, IRC and Google+

Re: [foreman-dev] Script to recycle passenger processes

2017-05-11 Thread Lukas Zapletal
It's just a script as cron job, if we agree that hourly is viable option (that's what I think). I think I could also backport it into 1.15 as "opt-in" (e.g. disabled by default) so people can easily test it. On Wed, May 10, 2017 at 1:58 PM, Bryan Kearney wrote: > On

Re: [foreman-dev] Performance analysis deep-dive, what would you like to hear about?

2017-05-11 Thread Lukas Zapletal
Thanks for doing this. Ideas: - Rails ActiveRecord SQL debugging (eager loading and N+1 problems - how to spot them) - how we configure passenger by default and what are the limitations - how passenger handles memory-leaked processes (it doesn't - see my script) - how to enable slow SQL logging

Re: [foreman-dev] Re: 1.15.0 release status

2017-05-11 Thread Dominic Cleal
On 11/05/17 02:16, Daniel Lobato wrote: > Thanks, it seems like either I don't understand the combination filter > or it didn't work >