failed to open runtime journal: No space left on device

General support questions
Post Reply
thomas_cai
Posts: 2
Joined: 2021/04/12 07:32:16

failed to open runtime journal: No space left on device

Post by thomas_cai » 2021/04/12 07:39:03

Hello,

I have a Centos 7.9 server, but it keeps reporting the below message, even it has enough space:
failed to open runtime journal: No space left on device

Is there any way to fix this issue?

I tried to reboot the server, it fixed the issue temporarily, but the message comes again later.

Many thanks!!

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: failed to open runtime journal: No space left on device

Post by TrevorH » 2021/04/12 08:12:32

Are you sure it has enough space? The default location for teh journal files is under /run which is a separate tmpfs filesystem and can easily fill up. The default size of the journal files is set from /etc/systemd/journald.conf - look at RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize=. You'll also find that any systemd service that crashes and takes a core dump will write to their respective /run directories and that also uses up space.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

thomas_cai
Posts: 2
Joined: 2021/04/12 07:32:16

Re: failed to open runtime journal: No space left on device

Post by thomas_cai » 2021/04/12 10:04:26

Hello Trevorh,

Here is the details of the disk:

Filesystem Size Used Avail Use% Mounted on
/dev/root 4.0G 535M 3.3G 14% /
tmpfs 147M 84K 147M 1% /run
/dev 364M 0 364M 0% /dev
shmfs 367M 0 367M 0% /dev/shm
/dev/sda2 30G 1.8G 28G 7% /sysroot
/dev/sda1 494M 40M 455M 8% /sysroot/boot
/dev/sda15 495M 12M 484M 3% /sysroot/boot/efi

Here is the journald.conf:
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See journald.conf(5) for details.

[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitInterval=30s
#RateLimitBurst=1000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=yes
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: failed to open runtime journal: No space left on device

Post by TrevorH » 2021/04/12 12:10:08

tmpfs 147M 84K 147M 1% /run
Check that again when the problem exists.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

Post Reply