The log is actually logged - I had some wrong assumptions how systemd/journald logs.
journalctl -u puppetserver.service only contains logs until the systemd service is started. To get the STDOUT output of the puppetserver java process one can use: journalctl -t puppetserver or in case of CentOS/RHEL 7 this is normally also available in /var/log/messages - Thomas Am Montag, 9. Juli 2018 11:32:53 UTC+2 schrieb Thomas Müller: > > Hi > > I wan't my puppetserver 5.3 to log to STDOUT in addition or as replacement > for /var/log/puppetlabs/puppetserver/puppetserver.log. > > I've added the following to the /etc/puppetlabs/puppetserver/logback.xml > config file: > > <configuration> > ... > <root level="info"> > ... > *<appender-ref ref="STDOUT" />* > </root> > </configuration> > > I can see that after a service restart some of the messages get printed to > stdout - but not all. > > All the puppet compiler messages are not added to STDOUT but they are in > puppetserver.log. > > Example messages not added to STDOUT: > > Pupppet The function 'xy' is deprecated in favor of using 'lookup' ... > Puppet This method is deprecated, please use the ... > Puppet Undefined variable '...' ... > Puppet Compiled catalog for ... in environment .... in ... seconds > > Same if I remove the F1 appender-ref to disable logging to > puppetserver.log. > > Is there some additional config required to log everything that is logged > to the file also to STDOUT? > > - Thomas > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/903d84e7-606c-46b6-ad66-ebea1077387f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
