Systemd - Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd.

hopeful

Sorry for abusing the LES forum for asking for technical help, but hey, this is an issue I encountered on LES, so who knows, maybe someone else has run into this issue too?

Basically, I upgraded my Ubuntu installation to Ubuntu 19.10 (I know, 128MB is no longer a supported config). And now systemctl daemon-reload won't work because /run has less than 16M.

It seems that the size of /run is not something I can control easily. Should I raise a ticket and have it bumped (at least temporarily)?

root@uk1:/tmp# systemctl daemon-reload
Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 12.6M are free, but a safety buffer of 16.0M is enforced.
root@uk1:/tmp# free -m
              total        used        free      shared  buff/cache   available
Mem:            128          17           0           0         109         110
Swap:             0           0           0
root@uk1:/tmp# df -h
Filesystem         Size  Used Avail Use% Mounted on
/dev/ploop14426p1  2.9G  563M  2.2G  21% /
none                64M     0   64M   0% /sys/fs/cgroup
none                64M     0   64M   0% /dev
tmpfs               64M     0   64M   0% /dev/shm
tmpfs               13M  124K   13M   1% /run
tmpfs              5.0M     0  5.0M   0% /run/lock
none                64M     0   64M   0% /run/shm
tmpfs               13M     0   13M   0% /run/user/0
root@uk1:/tmp# cat /etc/fstab
proc  /proc       proc    defaults    0    0
none  /dev/pts    devpts  rw,gid=5,mode=620    0    0
none  /run/shm    tmpfs   defaults    0    0
root@uk1:/tmp# free -m
              total        used        free      shared  buff/cache   available
Mem:            128          17           0           0         109         110
Swap:             0           0           0
root@uk1:/tmp# cat /etc/os-release 
NAME="Ubuntu"
VERSION="19.10 (Eoan Ermine)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 19.10"
VERSION_ID="19.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan

PHP_Backend

append to /etc/fstab
none /run tmpfs defaults,size=64M 0 0

mount /run again
mount -o remount /run

now check df again
df -h /run

Don't worry, increasing /run size to 64M won't reduce your Ram, as long as you keep your /run clean.

I know, 128MB is no longer a supported config

Who said that? In server environment, you can squish a lot from 128 MB.

Should I raise a ticket and have it bumped (at least temporarily)?

If your OS installation was provided by them, you should notify them that such lower /run size does not work for systemctl enforced restriction. So, they should edit their OS template.