Adding --logdest /path/to/your/log to your config.ru file should work. Here's
what I'm using with 0.25.1 and Passenger 2.2.7:
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not i
Hi
I have similar issues with puppet 0.25 + passenger 2.2.2,
All logs are going to /var/log/messages even when logdir is defined in
/etc/puppet/puppec.conf on the server?
## site id_api_cd
[id_api_cd_keyA_prd]
manifest = /etc/puppet/site/id_api_cd/prd/site.pp
modulepath
On Aug 8, 6:14 am, Ohad Levy wrote:
> I've tried to change logging to warn, it ended up breaking the puppetmaster
> not being able to sign new certificates.
IIRC, you can do something like this for 0.24.8:
Puppet::Util::Log.newdestination("/path/to/log")
Maybe look at Puppet::Util::Log for t
I've tried to change logging to warn, it ended up breaking the puppetmaster
not being able to sign new certificates.
I know the setup in 0.25 is different, so it might work there.
Ohad
On Sat, Aug 8, 2009 at 3:30 AM, cnjohnson wrote:
>
> On Aug 7, 12:50 am, David Schmitt wrote:
> > cnjohnson
On Aug 7, 12:50 am, David Schmitt wrote:
> cnjohnson wrote:
> > I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
> > 5.2. I have two nodes, one x86_64 and one ppc64, that have the client
> > running and they are checking in regularly as expected. I have a
> > minimal site.pp
cnjohnson wrote:
> I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
> 5.2. I have two nodes, one x86_64 and one ppc64, that have the client
> running and they are checking in regularly as expected. I have a
> minimal site.pp file which defines the owner, group and permissions
