[systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory
David Lambert
dave at lambsys.com
Fri Mar 30 09:55:44 PDT 2012
Lennart,
I think I found another clue. I noticed that the directory
/var/log/journal was being used in addition to /var/run/log/journal. I
do not want persistent logging, so I removed /var/log/journal. When I
did this, systemd-journalctl appeared to work correctly.
Obviously I am mis-understanding (and mis-using) the journaling
features of systemd. Could you please point me to any overview of where
and how the journaling sub-system stores its data?
Best regards,
Dave.
On 03/29/2012 03:42 PM, David Lambert wrote:
> Thanks Lennart, it looks like your guess was spot on! See attached
> trace. Any suggestions on how to narrow this down further?
>
> On 03/29/2012 09:38 AM, Lennart Poettering wrote:
>>
>> Hmm, my guess is that we might have too many mem maps open? Can you
>> check strace? Anything suspicious there?
>>
>> Lennart
>>
>
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20120330/0a83edae/attachment.htm>
More information about the systemd-devel
mailing list