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:
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
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?
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/
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