I have a rsyslog-based log server and would like to know how I can configure journalctl to send its logs to said log server.
On Thu, Jul 10, 2014 at 05:33:32PM -0400, Mauricio Tavares wrote:
I have a rsyslog-based log server and would like to know how I
can configure journalctl to send its logs to said log server.
You don't. You install rsyslog on your "client" server and set it up to forward as normal.
In the basic state, this just looks exactly like the traditional way. (In fact, you can even turn off persistent journald if you like.) Or, you can use 'imjournal' for more sophisticated integration if you like -- see http://www.rsyslog.com/doc/imjournal.html.
On 10 Jul 2014 23:26, "Matthew Miller" mattdm@mattdm.org wrote:
(In fact, you can even turn off persistent journald if you like.) Or, you can use 'imjournal' for more sophisticated integration if you like -- see http://www.rsyslog.com/doc/imjournal.html.
In fact in EL7 the default behaviour is no persistent journald since the logging is set to auto and there is no /var/log/journal ...
The default behaviour is to have journald collect the logs and forward them all to rsyslog to then be stored on disk or filtered or forwarded just the same as in EL6 ...
On a related note this does mean that if you want persistent journald logging you must remember to create that directory...
On Fri, Jul 11, 2014 at 3:00 AM, James Hogarth james.hogarth@gmail.com wrote:
On 10 Jul 2014 23:26, "Matthew Miller" mattdm@mattdm.org wrote:
(In fact, you can even turn off persistent journald if you like.) Or, you can use 'imjournal' for more sophisticated integration if you like -- see http://www.rsyslog.com/doc/imjournal.html.
Is it me who have not had coffee yet or that assumes you have to have rsyslog installed in the machine running systemd/journald? For the sake of this discussion, let's say that is not an option for whatever reason, so you must make journald talk to the rsyslog server. What would need to be done in both ends?
In fact in EL7 the default behaviour is no persistent journald since the logging is set to auto and there is no /var/log/journal ...
The default behaviour is to have journald collect the logs and forward them all to rsyslog to then be stored on disk or filtered or forwarded just the same as in EL6 ...
On a related note this does mean that if you want persistent journald logging you must remember to create that directory...
Now, let's say we are trying to prove journald is superior to rsyslog, so we must not use rsyslog in this machine (only in the syslog server since it is up and has to deal with others)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 11.07.2014 10:47, Mauricio Tavares wrote:
On Fri, Jul 11, 2014 at 3:00 AM, James Hogarth james.hogarth@gmail.com wrote:
On 10 Jul 2014 23:26, "Matthew Miller" mattdm@mattdm.org wrote:
(In fact, you can even turn off persistent journald if you like.) Or, you can use 'imjournal' for more sophisticated integration if you like -- see http://www.rsyslog.com/doc/imjournal.html.
Is it me who have not had coffee yet or that assumes you have to
have rsyslog installed in the machine running systemd/journald? For the sake of this discussion, let's say that is not an option for whatever reason, so you must make journald talk to the rsyslog server. What would need to be done in both ends?
That's a bit like saying "you must make mysql talk to the apache webserver". The journal has its own mechanism using systemd-journal-remote but that hasn't been included in CentOS7 because its fairly new.
In fact in EL7 the default behaviour is no persistent journald since the logging is set to auto and there is no /var/log/journal ...
The default behaviour is to have journald collect the logs and forward them all to rsyslog to then be stored on disk or filtered or forwarded just the same as in EL6 ...
On a related note this does mean that if you want persistent journald logging you must remember to create that directory...
Now, let's say we are trying to prove journald is superior to
rsyslog, so we must not use rsyslog in this machine (only in the syslog server since it is up and has to deal with others)
In this scenario you would set up systemd-journal-remote on the server in addition to rsyslog so syslog clients can keep using the rsyslog endpoint and journal client can use the journal-remote one. On the server you could then forward the data to the local rsyslog to have everything in one place/format.
The whole remote logging story is still pretty dodgy right now though so I would stick to rsyslog for now.
Regards, Dennis
On Fri, Jul 11, 2014 at 08:00:17AM +0100, James Hogarth wrote:
In fact in EL7 the default behaviour is no persistent journald since the logging is set to auto and there is no /var/log/journal ...
The default behaviour is to have journald collect the logs and forward them all to rsyslog to then be stored on disk or filtered or forwarded just the same as in EL6 ...
Oh, whoops. I'm living too far in the future over here. :)
Works in CentOS 6.5 and fedora 20. Not so much in CentOS 7. Thanks.
-rp
On Thu, Jul 10, 2014 at 5:07 PM, Richard Pierce richard@gopierce.com wrote:
Works in CentOS 6.5 and fedora 20. Not so much in CentOS 7. Thanks.
Probably affected by this known bug:
http://bugs.centos.org/view.php?id=7340
There is a workaround (temporary solution) in that report.
Akemi
Thanks, I will try it when I get this golf club out of my hand.
Original Message From: Akemi Yagi Sent: Thursday, July 10, 2014 7:35 PM To: CentOS mailing list Reply To: CentOS mailing list Subject: Re: [CentOS] 7 and Logitech K750 Keyboard.
On Thu, Jul 10, 2014 at 5:07 PM, Richard Pierce richard@gopierce.com wrote:
Works in CentOS 6.5 and fedora 20. Not so much in CentOS 7. Thanks.
Probably affected by this known bug:
http://bugs.centos.org/view.php?id=7340
There is a workaround (temporary solution) in that report.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Many thanks, yes indeed, kernel version 3.15.5-1.el7.elrepo.x86_64 does support the unified receiver used by the K750 and Logitech mouse.
Original Message From: Akemi Yagi Sent: Thursday, July 10, 2014 7:35 PM To: CentOS mailing list Reply To: CentOS mailing list Subject: Re: [CentOS] 7 and Logitech K750 Keyboard.
On Thu, Jul 10, 2014 at 5:07 PM, Richard Pierce richard@gopierce.com wrote:
Works in CentOS 6.5 and fedora 20. Not so much in CentOS 7. Thanks.
Probably affected by this known bug:
http://bugs.centos.org/view.php?id=7340
There is a workaround (temporary solution) in that report.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Jul 10, 2014 at 9:18 PM, Richard Pierce richard@gopierce.com wrote:
Many thanks, yes indeed, kernel version 3.15.5-1.el7.elrepo.x86_64 does support the unified receiver used by the K750 and Logitech mouse.
Good news. As noted in that bug report, when the next kernel update is released, the centosplus kernel will have the patch that is supposed to fix the issue.
Akemi
Original Message From: Akemi Yagi Sent: Thursday, July 10, 2014 7:35 PM To: CentOS mailing list Reply To: CentOS mailing list Subject: Re: [CentOS] 7 and Logitech K750 Keyboard.
On Thu, Jul 10, 2014 at 5:07 PM, Richard Pierce richard@gopierce.com wrote:
Works in CentOS 6.5 and fedora 20. Not so much in CentOS 7. Thanks.
Probably affected by this known bug:
http://bugs.centos.org/view.php?id=7340
There is a workaround (temporary solution) in that report.
Akemi _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos