Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I received the following error trying to view logs on an embedded ARM board running Angstrom Linux with systemd.

# journalctl -f    
Failed to iterate through journal: Bad message

I searched the systemd documentation and didn't find any useful reference to this message or what to do to resolve it.

The filesystem is on an sdcard, so it's possible that it's caused by file corruption, although the system displays no other signs of this. Going in to /var/log/journal and removing all the files in there fixed the problem. This has got logging working again at the cost of losing all my previous log message.

What can be the underlying cause of this?

share|improve this question

closed as not a real question by Michael Hampton, Magellan, voretaq7 Dec 6 '12 at 21:08

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Is your disk full? – Tom O'Connor Dec 6 '12 at 11:28
no, it isn't full – ndyer Dec 6 '12 at 13:58
Any sign of disk errors in syslog? Will it pass a SMART check? – Tom O'Connor Dec 6 '12 at 14:21
No sign of filesystem errors, it's on an SD card so SMART is impossible. – ndyer Dec 6 '12 at 15:11
Oh, and -1 for not using a search engine, and for not including relevant details. – Michael Hampton Dec 6 '12 at 16:00

It is a bug in your version of systemd that has since been fixed upstream.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.