Puppet users - Apr 2010 - Logging on Puppetmaster 0.25.4/Passenger-2.2.8

I just upgraded my puppetmaster from 0.25.1 to 0.25.4 using the EPEL
packages.  Now, I can''t see any of the logging when hosts connect to
my puppetmaster except for in the passenger/apache logs.  The only
exception to this rule is when the puppetmaster connects to itself,
then I can see the normal messages in the logs.  I''ve bounced Apache
numerous times.

I could see the logs I need  before I did the upgrade in /var/log/
messages which was not ideal, but fine.

config.ru:
$:.unshift(''/var/lib/puppet'')
$0 = "puppetmasterd"
require ''puppet''
ARGV << "--trace"
ARGV << "--rack"
ARGV << "--logdest" <<
"/var/log/puppet/puppetmaster.log"
require ''puppet/application/puppetmasterd''
run Puppet::Application[:puppetmasterd].run

The puppetmaster.log seems like it is only updated in batches every
few hours and it is only really logging the hostname it compiled.
Nothing about the manifests/classes, etc.

My puppet.conf only really has:
# The Puppet log directory.
    # The default value is ''$vardir/log''.
    logdir = /var/log/puppet

But nothing really even happens there.  The masterhttp.log is always
zero length.

Any ideas how I can get my old logging back?

Cheers,

-Dave

-- 
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.

If you''re using passenger, you won''t get a masterhttp.log;
that''s from webrick.

I''ve noticed the logging to a ''--logdest=file'' is
buffered with a pretty giant buffer, which can be extremely annoying/confusing
because it looks like nothing is happening.

You can either set ''autoflush=true'' (but beware this will
fsync after every message) or use --logdest=syslog and edit syslog.conf to
include ''daemon.* /var/log/puppetmaster.log'' for speedy
realtime logging.


-=Eric

On Apr 19, 2010, at 10:43 PM, dmangot wrote:
> I just upgraded my puppetmaster from 0.25.1 to 0.25.4 using the EPEL
> packages.  Now, I can''t see any of the logging when hosts connect
to
> my puppetmaster except for in the passenger/apache logs.  The only
> exception to this rule is when the puppetmaster connects to itself,
> then I can see the normal messages in the logs.  I''ve bounced
Apache
> numerous times.
> 
> I could see the logs I need  before I did the upgrade in /var/log/
> messages which was not ideal, but fine.
> 
> config.ru:
> $:.unshift(''/var/lib/puppet'')
> $0 = "puppetmasterd"
> require ''puppet''
> ARGV << "--trace"
> ARGV << "--rack"
> ARGV << "--logdest" <<
"/var/log/puppet/puppetmaster.log"
> require ''puppet/application/puppetmasterd''
> run Puppet::Application[:puppetmasterd].run
> 
> The puppetmaster.log seems like it is only updated in batches every
> few hours and it is only really logging the hostname it compiled.
> Nothing about the manifests/classes, etc.
> 
> My puppet.conf only really has:
> # The Puppet log directory.
>    # The default value is ''$vardir/log''.
>    logdir = /var/log/puppet
> 
> But nothing really even happens there.  The masterhttp.log is always
> zero length.
> 
> Any ideas how I can get my old logging back?
> 
> Cheers,
> 
> -Dave
> 
> -- 
> 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.