[tmpfs] /run full
[tmpfs] /run full
Hi,
I have a problem with /run, its size doesn't decrease so when it's full, I have to reboot.
[root@SRV ~]# df -h
tmpfs 5,9G 2,4G 3,6G 41% /run
The size of /run/log/journal decrease but doesn't decrease /run
[root@SRV ~]# du -k /run | sort -nr
606984 /run
606208 /run/log/journal/d5b1a7595c414aef867926a90584852b
606208 /run/log/journal
606208 /run/log How to decrease the size of /run ?
Thanks for your help.
I have a problem with /run, its size doesn't decrease so when it's full, I have to reboot.
[root@SRV ~]# df -h
tmpfs 5,9G 2,4G 3,6G 41% /run
The size of /run/log/journal decrease but doesn't decrease /run
[root@SRV ~]# du -k /run | sort -nr
606984 /run
606208 /run/log/journal/d5b1a7595c414aef867926a90584852b
606208 /run/log/journal
606208 /run/log How to decrease the size of /run ?
Thanks for your help.
Re: [tmpfs] /run full
It's more likely that you've run across a bug that occurs when systemd packages are updated and you do not reboot afterwards. It loses its dbus connection and stops cleaning up old data in /run. For now the safe way to proceed is to reboot every time the systemd packages are updated, in the same way that you would if glibc were.
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
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
Re: [tmpfs] /run full
Thanks for your reply.
I don't have old log in /run/log/
(du_run.png)
I reboot the server each time /run is full
I don't have old log in /run/log/
(du_run.png)
I reboot the server each time /run is full
Re: [tmpfs] /run full
How can I resolve this problem?
Why the size of /run increase (90%) with df while the size seems to be stable with du?
I have to reboot the server to decrease the size of /run
Thanks.
Why the size of /run increase (90%) with df while the size seems to be stable with du?
I have to reboot the server to decrease the size of /run
Thanks.
Re: [tmpfs] /run full
99%, I have to reboot again to free tmpfs /run
du of /run is stable. du -h /run/log/journal/
408M /run/log/journal/d5b1a7595c414aef867926a90584852b
408M /run/log/journal/
journalctl --disk-usage
Archived and active journals take up 408.0M on disk.
[root@PWCFEM31 d5b1a7595c414aef867926a90584852b]# df -h
tmpfs 5,9G 5,8G 112M 99% /run
What I expect is 408M instead of 5.8G
Is there an another way instead rebooting server to free space in /run ?du of /run is stable. du -h /run/log/journal/
408M /run/log/journal/d5b1a7595c414aef867926a90584852b
408M /run/log/journal/
journalctl --disk-usage
Archived and active journals take up 408.0M on disk.
[root@PWCFEM31 d5b1a7595c414aef867926a90584852b]# df -h
tmpfs 5,9G 5,8G 112M 99% /run
What I expect is 408M instead of 5.8G
Re: [tmpfs] /run full
what I try:
In /etc/systemd/journald.conf, I set these parameters:
RuntimeMaxUse=400M
RuntimeKeepFree=2G
systemctl kill --signal=SIGUSR2 systemd-journald.service
journalctl --vacuum-size=400M
journalctl --vacuum-time=1d
In /etc/systemd/journald.conf, I set these parameters:
RuntimeMaxUse=400M
RuntimeKeepFree=2G
systemctl kill --signal=SIGUSR2 systemd-journald.service
journalctl --vacuum-size=400M
journalctl --vacuum-time=1d
Re: [tmpfs] /run full
It doesn't resolve the problem
Please help...
Please help...
-
- Posts: 2019
- Joined: 2015/02/17 15:14:33
- Location: Bulgaria
- Contact:
Re: [tmpfs] /run full
Run a full update and reboot.