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 on several files. Changes to those files on the two client nodes are reverted according to the site.pp file as expected. I have a question about logging, though. Puppet now logs through /var/ log/messages. This is fine, but not my first choice. Is this being handled by apache? Do I need to add an entry in the virtual host section of httpd.conf; or is this being handled by rack? I would prefer that the logging be done in /var/puppet/log/masterhttp.log Any suggestions would be appreciated. Cheers-- Charles --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 on > several files. Changes to those files on the two client nodes are > reverted according to the site.pp file as expected. > > I have a question about logging, though. Puppet now logs through /var/ > log/messages. This is fine, but not my first choice. Is this being > handled by apache? Do I need to add an entry in the virtual host > section of httpd.conf; or is this being handled by rack? I would > prefer that the logging be done in /var/puppet/log/masterhttp.log > > Any suggestions would be appreciated.Take a look at the configuration reference at [1], especially the httplog, logdir, rails_loglevel. railslog, report*, and syslogfacility. See [2] for details on reporting. Regards, DavidS [1] http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference [2] http://reductivelabs.com/trac/puppet/wiki/ReportReference --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Aug 7, 12:50 am, David Schmitt <da...@dasz.at> 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 file which defines the owner, group and permissions on > > several files. Changes to those files on the two client nodes are > > reverted according to the site.pp file as expected. > > > I have a question about logging, though. Puppet now logs through /var/ > > log/messages. This is fine, but not my first choice. Is this being > > handled by apache? Do I need to add an entry in the virtual host > > section of httpd.conf; or is this being handled by rack? I would > > prefer that the logging be done in /var/puppet/log/masterhttp.log > > > Any suggestions would be appreciated. > > Take a look at the configuration reference at [1], especially the > httplog, logdir, rails_loglevel. railslog, report*, and syslogfacility. > > See [2] for details on reporting. > > Regards, DavidS > > [1]http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference > [2]http://reductivelabs.com/trac/puppet/wiki/ReportReferenceThank you for the reply. Unfortunately, I still cannot change where puppetmasterd logs when used as a rack app. The cofig.ru file has the following lines: # startup code stolen from bin/puppetmasterd Puppet.parse_config Puppet::Util::Log.level = :info Puppet::Util::Log.newdestination(:syslog) Commenting out the last two lines has the effect of stopping logging altogether even though logdir and httplog are specified in /etc/puppet/ puppet.conf Doing the following causes the clients to report: Could not call puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500 Internal Server Error> mylog = File.new("/var/puppet/log/myhttp.log", "a+") Puppet::Util::Log.newdestination(mylog) I am clearly missing something. Any further clues would be appreciated. Cheers-- Charles --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 <gm.johns276@gmail.com> wrote:> > On Aug 7, 12:50 am, David Schmitt <da...@dasz.at> 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 file which defines the owner, group and permissions on > > > several files. Changes to those files on the two client nodes are > > > reverted according to the site.pp file as expected. > > > > > I have a question about logging, though. Puppet now logs through /var/ > > > log/messages. This is fine, but not my first choice. Is this being > > > handled by apache? Do I need to add an entry in the virtual host > > > section of httpd.conf; or is this being handled by rack? I would > > > prefer that the logging be done in /var/puppet/log/masterhttp.log > > > > > Any suggestions would be appreciated. > > > > Take a look at the configuration reference at [1], especially the > > httplog, logdir, rails_loglevel. railslog, report*, and syslogfacility. > > > > See [2] for details on reporting. > > > > Regards, DavidS > > > > [1]http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference > > [2]http://reductivelabs.com/trac/puppet/wiki/ReportReference > > Thank you for the reply. Unfortunately, I still cannot change where > puppetmasterd logs when used as a rack app. The cofig.ru file has the > following lines: > > # startup code stolen from bin/puppetmasterd > Puppet.parse_config > Puppet::Util::Log.level = :info > Puppet::Util::Log.newdestination(:syslog) > > Commenting out the last two lines has the effect of stopping logging > altogether even though logdir and httplog are specified in /etc/puppet/ > puppet.conf > > Doing the following causes the clients to report: Could not call > puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500 Internal > Server Error> > > mylog = File.new("/var/puppet/log/myhttp.log", "a+") > Puppet::Util::Log.newdestination(mylog) > > I am clearly missing something. Any further clues would be > appreciated. > > Cheers-- > > Charles > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Christian Hofstaedtler
2009-Aug-10 09:35 UTC
[Puppet Users] Re: puppet logging with passenger
On Aug 8, 6:14 am, Ohad Levy <ohadl...@gmail.com> 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 the details. Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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
/etc/puppet/site/id_api_cd/prd/modules/:/etc/puppet/site/id_api_cd/public/modules/
logdir = /etc/puppet/site/id_api_cd/logs
usecacheonfailure = true
[math_keyC_dev]
manifest = /etc/puppet/site/math/dev/site.pp
modulepath
/etc/puppet/site/math/dev/modules/:/etc/puppet/site/math/public/modules/
logdir = /etc/puppet/site/math/logs
usecacheonfailure = false
Like I''m using several environments it''s imported that each
environment
logs to separate directory ...
Under 0.25 the /etc/puppet/rack/config.ru looks like:
$0 = "puppetmasterd"
require ''puppet''
# if you want debugging:
# ARGV << "--debug"
ARGV << "--rack"
require ''puppet/application/puppetmasterd''
# we''re usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Application[:puppetmasterd].run
May somebody has ans answer?
Ohad Levy schrieb:> 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 <gm.johns276@gmail.com
> <mailto:gm.johns276@gmail.com>> wrote:
>
>
> On Aug 7, 12:50 am, David Schmitt <da...@dasz.at
> <mailto:da...@dasz.at>> 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 file which defines the owner, group and
> permissions on
> > > several files. Changes to those files on the two client nodes
are
> > > reverted according to the site.pp file as expected.
> >
> > > I have a question about logging, though. Puppet now logs
> through /var/
> > > log/messages. This is fine, but not my first choice. Is this
being
> > > handled by apache? Do I need to add an entry in the virtual
host
> > > section of httpd.conf; or is this being handled by rack? I
would
> > > prefer that the logging be done in
/var/puppet/log/masterhttp.log
> >
> > > Any suggestions would be appreciated.
> >
> > Take a look at the configuration reference at [1], especially the
> > httplog, logdir, rails_loglevel. railslog, report*, and
> syslogfacility.
> >
> > See [2] for details on reporting.
> >
> > Regards, DavidS
> >
> >
[1]http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference
> > [2]http://reductivelabs.com/trac/puppet/wiki/ReportReference
>
> Thank you for the reply. Unfortunately, I still cannot change where
> puppetmasterd logs when used as a rack app. The cofig.ru
> <http://cofig.ru> file has the
> following lines:
>
> # startup code stolen from bin/puppetmasterd
> Puppet.parse_config
> Puppet::Util::Log.level = :info
> Puppet::Util::Log.newdestination(:syslog)
>
> Commenting out the last two lines has the effect of stopping logging
> altogether even though logdir and httplog are specified in
> /etc/puppet/
> puppet.conf
>
> Doing the following causes the clients to report: Could not call
> puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500 Internal
> Server Error>
>
> mylog = File.new("/var/puppet/log/myhttp.log",
"a+")
> Puppet::Util::Log.newdestination(mylog)
>
> I am clearly missing something. Any further clues would be
> appreciated.
>
> Cheers--
>
> Charles
>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
Joshua Anderson
2010-Jan-08 01:45 UTC
Re: [Puppet Users] Re: puppet logging with passenger
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 in your RUBYLIB:
# $:.unshift(''/opt/puppet/lib'')
$0 = "puppetmasterd"
require ''puppet''
# if you want debugging:
# ARGV << "--debug"
ARGV << "--rack"
# Log to a file in addition to syslog
ARGV << "--logdest" <<
"/var/puppet/log/puppetmaster.log"
require ''puppet/application/puppetmasterd''
# we''re usually running inside a Rack::Builder.new {} block,
# therefore we need to call run *here*.
run Puppet::Application[:puppetmasterd].run
----------------------------------------
-Josh
On Oct 28, 2009, at 7:14 AM, philipp Hanselmann wrote:
>
> 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 >
/etc/puppet/site/id_api_cd/prd/modules/:/etc/puppet/site/id_api_cd/public/modules/
> logdir = /etc/puppet/site/id_api_cd/logs
> usecacheonfailure = true
> [math_keyC_dev]
> manifest = /etc/puppet/site/math/dev/site.pp
> modulepath >
/etc/puppet/site/math/dev/modules/:/etc/puppet/site/math/public/modules/
> logdir = /etc/puppet/site/math/logs
> usecacheonfailure = false
>
>
>
> Like I''m using several environments it''s imported that
each environment
> logs to separate directory ...
>
> Under 0.25 the /etc/puppet/rack/config.ru looks like:
>
> $0 = "puppetmasterd"
> require ''puppet''
>
> # if you want debugging:
> # ARGV << "--debug"
>
> ARGV << "--rack"
> require ''puppet/application/puppetmasterd''
> # we''re usually running inside a Rack::Builder.new {} block,
> # therefore we need to call run *here*.
> run Puppet::Application[:puppetmasterd].run
>
>
> May somebody has ans answer?
>
>
> Ohad Levy schrieb:
>> 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 <gm.johns276@gmail.com
>> <mailto:gm.johns276@gmail.com>> wrote:
>>
>>
>> On Aug 7, 12:50 am, David Schmitt <da...@dasz.at
>> <mailto:da...@dasz.at>> 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 file which defines the owner, group and
>> permissions on
>>>> several files. Changes to those files on the two client nodes
are
>>>> reverted according to the site.pp file as expected.
>>>
>>>> I have a question about logging, though. Puppet now logs
>> through /var/
>>>> log/messages. This is fine, but not my first choice. Is this
being
>>>> handled by apache? Do I need to add an entry in the virtual
host
>>>> section of httpd.conf; or is this being handled by rack? I
would
>>>> prefer that the logging be done in
/var/puppet/log/masterhttp.log
>>>
>>>> Any suggestions would be appreciated.
>>>
>>> Take a look at the configuration reference at [1], especially the
>>> httplog, logdir, rails_loglevel. railslog, report*, and
>> syslogfacility.
>>>
>>> See [2] for details on reporting.
>>>
>>> Regards, DavidS
>>>
>>> [1]http://reductivelabs.com/trac/puppet/wiki/ConfigurationReference
>>> [2]http://reductivelabs.com/trac/puppet/wiki/ReportReference
>>
>> Thank you for the reply. Unfortunately, I still cannot change where
>> puppetmasterd logs when used as a rack app. The cofig.ru
>> <http://cofig.ru> file has the
>> following lines:
>>
>> # startup code stolen from bin/puppetmasterd
>> Puppet.parse_config
>> Puppet::Util::Log.level = :info
>> Puppet::Util::Log.newdestination(:syslog)
>>
>> Commenting out the last two lines has the effect of stopping logging
>> altogether even though logdir and httplog are specified in
>> /etc/puppet/
>> puppet.conf
>>
>> Doing the following causes the clients to report: Could not call
>> puppetmaster.getconfig: #<RuntimeError: HTTP-Error: 500 Internal
>> Server Error>
>>
>> mylog = File.new("/var/puppet/log/myhttp.log",
"a+")
>> Puppet::Util::Log.newdestination(mylog)
>>
>> I am clearly missing something. Any further clues would be
>> appreciated.
>>
>> Cheers--
>>
>> Charles
>>
>>
>>
>>>
>
>
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.