Re: [systemd-devel] [rsyslog] Rsyslog & newlines
Hi Lennart, I tested this on Systemd v229 & observed this behavior. Thanks, RV On Fri, Jun 16, 2017 at 1:03 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Thu, 15.06.17 15:17, Renjith Vijayan (renjith...@gmail.com) wrote: > > > + Systemd-dev > > > > Hi, > > > > Does journal ignore the forwarding of logs ending with newline(\n) to > > rsyslog? In my system there are some logs send directly via > > sd_journal_send() API and ending with newline. > > These logs are present in journal, but not in /var/log/messages. > > > > Rainer confirmed that rsyslog does accept logs with newline as seen in > mail > > below. So is this the case where journal not forwarding the logs due to > > newline? > > Note that the behaviour of journald regarding embedded newlines > changed a couple of times in the past. Have you tested this with a > current systemd version? > > Lennart > > -- > Lennart Poettering, Red Hat > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [rsyslog] Rsyslog & newlines
+ Systemd-dev Hi, Does journal ignore the forwarding of logs ending with newline(\n) to rsyslog? In my system there are some logs send directly via sd_journal_send() API and ending with newline. These logs are present in journal, but not in /var/log/messages. Rainer confirmed that rsyslog does accept logs with newline as seen in mail below. So is this the case where journal not forwarding the logs due to newline? Thanks, RV On Thu, Jun 15, 2017 at 1:27 PM, Rainer Gerhards <rgerha...@hq.adiscon.com> wrote: > I assume that journal does not forward them. A debug log might help to > validate this assumption. Rsyslog does not reject logs with newlines albeit > they usually cause huge problems in many subsystems and thus it is strongly > recommended to not use them. > > Rainer > > Sent from phone, thus brief. > > Am 15.06.2017 05:00 schrieb "Renjith Vijayan via rsyslog" < > rsys...@lists.adiscon.com>: > > Hi, > > I am working on a system where both systemd-journal & rsyslog(7.6.1) are > there. Systemd-journal is configured to forward logs to rsyslog routinely. > I have some logs which ends with newlines & that are directly sent to > journal using sd_journal_send() API's. > > I see that although these logs are present in journal, it's not present in > /var/log/messages which is populated by rsyslog. Is rsyslog rejecting these > logs due to the ending newline? > > Further, based on some search results on this topic, I tried adding the > following lines to rsyslog.conf, but this didn't help either. > > # global directives > $EscapeControlCharactersOnReceive off > $EscapeControlCharactersCStyle off > $ActionFileDefaultTemplate RSYSLOG_SysklogdFileFormat > $SpaceLFOnReceive on > $DropTrailingLFOnReception off > > Could you please let me know how can I make rsyslog to accept these logs > ending with newline? > > Thanks, > RV > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > > > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Regarding Journal crash patch
Thanks Susant! But it seems the function in which the patch you pointed to is applied is missing in systemd-219 source. So i may need to back port more patches in order to get around this issue. Thanks, Renjith On Mon, May 16, 2016 at 2:10 PM, Susant Sahani <sus...@redhat.com> wrote: > > commit: > https://github.com/systemd/systemd/commit/4de2402b603ea2f518f451d06f09e15aeae54fab > > Susant > > On Mon, May 16, 2016 at 12:05 PM, Renjith Vijayan <renjith...@gmail.com> > wrote: > >> Hi, >> >> I am getting the exact journal service crash as mentioned in the link >> below. >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805042 >> (journal is killed every minute by watchdog) >> >> We are using systemd-219. >> >> This bug seems to be fixed in latest versions of systemd. >> >> We will not be able to upgrade to latest versions of systemd for some >> reasons in our platform. >> >> Could you please point out the systemd patches i need to back port to fix >> this issue? >> >> Regards, >> Renjith >> >> >> >> ___ >> systemd-devel mailing list >> systemd-devel@lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/systemd-devel >> >> > ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Regarding Journal crash patch
Hi, I am getting the exact journal service crash as mentioned in the link below. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805042 (journal is killed every minute by watchdog) We are using systemd-219. This bug seems to be fixed in latest versions of systemd. We will not be able to upgrade to latest versions of systemd for some reasons in our platform. Could you please point out the systemd patches i need to back port to fix this issue? Regards, Renjith ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Journal Log Persistence without restart of service
Hi All, I am trying to make journal logs persistent across reboots in my platform. Currently /var/log is mounted on volatile partition in the platform. I have a non-volatile partition mounted at /var/diagnostics. So i made the following change in tmpfile.d service config file(volatile.conf) to create a symlink. L+ /var/log/journal 0666 root root - /var/diagnostics/logs Also, the following changes to make logs persistent is done in journald.conf file. Storage=persistent But still when the system boots up it takes the run time journal path & no files are present in /var/log/journal directory.. *systemd-journal[114]: Runtime journal is using 8.0M (max allowed 392.4M, trying to leave 588.6M free of 3.8G available â current limit 392.4M).* *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using 8.0M (max allowed 392.4M, trying to leave 588.6M free of 3.8G available â current limit 392.4M).* *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Journal started* *Jan 09 05:18:58 ops-as5712 systemd-journal[114]: Runtime journal is using 8.0M* After i restart the systemd-journald service, the logs are becoming persistent & getting stored in the permanent partition. Could somebody point out what needs to be done to make it persistent without the restart of systemd-journald service? TIA, Renjith ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
