[rsyslog-notify] Forum Thread: Re: Strange linebreak with Jboss access logs - (Mode 'reply')
noreply at adiscon.com
noreply at adiscon.com
Fri Feb 28 12:21:34 CET 2014
User: Chriss.ko
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24276#p24276
Message:
----------
Hi Rainer,
well, the time foo I did is a workaround to get rid of a strange date
format which I had in the all.log:
[code:2hn9crog]
Feb 27 15:16:22 devfe1.example.de .288229+01:00
devfe1 JB1access-log 10.0.0.30
[27/Feb/2014:15:16:15 +0100] 0 HTTP/1.1 11001
http-executor-threads - 2817 /bkg.gif 200 GET 51660
[/code:2hn9crog]
So I googled a bit and fount a "solution" by putting the
"%TIMESTAMP:::date-rfc8601A%" into the template. I have no deeper know how
about that, it was just working. ;)
I replaces the "<188>" in the meantime with "<%PRI%>" and configured
"$InputFileFacility local2" and "$InputFileSeverity info", I have "PRI:
150" in both logs on the server site right now, so this is solved now.
There is no error message from the rsyslog about any misconfiguration till
now. Well, not with the current configuration. ;)
I played a bit with your template line and it is working now! :) So it
looks like all the errors are gone with the new template. I think that I
have to read a bit more about all the template magic.
Do you still want to have the debug log for deeper analysis or is it
obsolete since my problems are solved so far?
Cheers,
Chriss
More information about the rsyslog-notify
mailing list