System logging using systemd journal (not syslogd or klogd)

[Smatt]

I've been researching syslog (syslogd, klogd, syslog-ng) to turn on logging functionality on the Beaglebone.  I couldn't find very good documentation.  After a lot of research, I found that this is all handled through systemd journaling.  The problem I have is, when I create the /var/log/journal directory to persist the journal files, I see the following problems:

1. systemd-journalctl does not appear to work properly (does not show all log contents).  If I delete /var/log/journal, then there is no problem

2. systemd-journalctl --follow fails with "Failed to iterate through journal: Cannot allocate memory".   I believe this is due to a bug in systemd-journalctl when persisting the journal.

Can anyone tell me if they have successfully used journaling with systemd for application/system level logging?  Have you persisted the log files and handled log rotation?

My research can be found here:

http://www.mattlmassey.com/2012/07/10/explorations-into-angstrom-syslog-and-systemd/

[Koen Kooi]

Op 10 jul. 2012, om 09:33 heeft Smatt het volgende geschreven:

> I've been researching syslog (syslogd, klogd, syslog-ng) to turn on logging functionality on the Beaglebone. I couldn't find very good documentation. After a lot of research, I found that this is all handled through systemd journaling. The problem I have is, when I create the /var/log/journal directory to persist the journal files, I see the following problems:
> 1. systemd-journalctl does not appear to work properly (does not show all log contents). If I delete /var/log/journal, then there is no problem
> 2. systemd-journalctl --follow fails with "Failed to iterate through journal: Cannot allocate memory". I believe this is due to a bug in systemd-journalctl when persisting the journal.
>
> Can anyone tell me if they have successfully used journaling with systemd for application/system level logging? Have you persisted the log files and handled log rotation?

Are you using the latest software/image?

regards,

Koen

[Smatt]

Angstrom v2012-01-core Kernel 3.2.5+

systemd v40-r15

Looks like systemd can upgrade: systemd - v40-r15 - v44-45-g3eff420-r27

Is this to be expected for v40-r15?

[Koen Kooi]

Op 10 jul. 2012, om 16:05 heeft Smatt het volgende geschreven:

> Angstrom v2012-01-core Kernel 3.2.5+
> systemd v40-r15
>
> Looks like systemd can upgrade: systemd - v40-r15 - v44-45-g3eff420-r27
>
> Is this to be expected for v40-r15?

Yes, but it's recommended to install a new image using a .img file, the 3.2.5+ image is not using the release feeds, but the unstable feeds. the 06.xx and 07.xx images are using the release feeds. E.g. http://dominion.thruhere.net/koen/angstrom/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.07.06.img.xz has a fixed journald.

regards,

Koen

>
>
> On Tuesday, July 10, 2012 4:28:51 AM UTC-7, Koen Kooi wrote:
>
> Op 10 jul. 2012, om 09:33 heeft Smatt het volgende geschreven:
>
> > I've been researching syslog (syslogd, klogd, syslog-ng) to turn on logging functionality on the Beaglebone. I couldn't find very good documentation. After a lot of research, I found that this is all handled through systemd journaling. The problem I have is, when I create the /var/log/journal directory to persist the journal files, I see the following problems:
> > 1. systemd-journalctl does not appear to work properly (does not show all log contents). If I delete /var/log/journal, then there is no problem
> > 2. systemd-journalctl --follow fails with "Failed to iterate through journal: Cannot allocate memory". I believe this is due to a bug in systemd-journalctl when persisting the journal.
> >
> > Can anyone tell me if they have successfully used journaling with systemd for application/system level logging? Have you persisted the log files and handled log rotation?
>
> Are you using the latest software/image?
>
> regards,
>
> Koen
>

> -- To join: http://beagleboard.org/discuss
> To unsubscribe from this group, send email to:
> beagleboard...@googlegroups.com
> Frequently asked questions: http://beagleboard.org/faq

[Smatt]

Confirmed the v44-45 systemd fixed the persistence issue.  I can read the entire log history using journalctl (not systemd-journalctl).  

Why aren't these newer images posted to the Angstom Beagleboard page?  I wanted to use a stock img for baseline testing and development, but it looks like the Angstrom stock images are not being kept up-to-date for the Beagleboard.  

http://beagleboard.org/project/angstrom/ 

> beagleboard+unsubscribe@googlegroups.com

[Koen Kooi]

Op 11 jul. 2012, om 06:06 heeft Smatt het volgende geschreven:

> Confirmed the v44-45 systemd fixed the persistence issue. I can read the entire log history using journalctl (not systemd-journalctl).
> Why aren't these newer images posted to the Angstom Beagleboard page? I wanted to use a stock img for baseline testing and development, but it looks like the Angstrom stock images are not being kept up-to-date for the Beagleboard.

They are being kept up to date, but on the angstrom website:

http://downloads.angstrom-distribution.org/demo/beagleboard/
http://downloads.angstrom-distribution.org/demo/beaglebone/

[Smatt]

Koen,

Thought I would let you that I installed the img from your link below, but after installing the eth0 interface wouldn't work.  ifup/down wouldn't work.  Unplugging and replugging the cable did nothing.  I found some posts on the A4 board with a similar problem that was around a hardware issue.  Considering I'm running A5, I wouldn't think this would apply though.  

https://groups.google.com/forum/?fromgroups#!topic/beagleboard/nlRDyDDrTrY 

I decided to download the img from  http://downloads.angstrom-distribution.org/demo/beaglebone/ , which is dated 2012.06.18 (yours was 2012.07.06) and the problem went away.  Just an FYI.

Matt

> beagleboard+unsubscribe@googlegroups.com