[systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory
David Lambert
dave at lambsys.com
Thu Mar 29 06:22:41 PDT 2012
I am getting the message: "Failed to iterate through journal: Cannot
allocate memory" when attempting to run systemd-journalctl. Although I
am running an embedded system (Android on Beaglebone) I appear to have
plenty of resources as witnessed by "free" and "df":
total used free shared buffers cached
Mem: 254024 145168 108856 0 29264 60876
-/+ buffers/cache: 55028 198996
Swap: 0 0 0
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 7678396 1582904 5710336 22% /
/dev/root 7678396 1582904 5710336 22% /
devtmpfs 126900 0 126900 0% /dev
tmpfs 127012 0 127012 0% /dev/shm
tmpfs 127012 1576 125436 2% /run
tmpfs 127012 0 127012 0% /sys/fs/cgroup
tmpfs 127012 1576 125436 2% /var/run
tmpfs 127012 0 127012 0% /media
tmpfs 127012 1576 125436 2% /var/lock
tmpfs 127012 12 127000 1% /tmp
The output of "status" commands appears to be normal, and my
/etc/systemd/systemd-journald.conf contains:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# See system-journald.conf(5) for details
[Journal]
#Compress=yes
#RateLimitInterval=10s
#RateLimitBurst=200
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMinFileSize=
RuntimeMaxUse=1M
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMinFileSize=
ForwardToSyslog=no
#ForwardToKMsg=no
ForwardToConsole=yes
#ImportKernel=yes
More information about the systemd-devel
mailing list