Table of contents
This page describes what to do in case of an Icinga alert. For more information you could search the govuk-puppet repo for the source of the alert

Low available disk inodes

The inode usage on a box can be checked using:

df -i

which will give an output like:

Filesystem           Inodes  IUsed   IFree IUse% Mounted on
/dev/mapper/os-root 3121152 151646 2969506    5% /

with a row for each filesystem currently mounted.

Low available disk inodes on Jenkins

If Jenkins is running out of inodes (rather than disk space) then it may be possible to free some by clearing out old workspaces:

find /var/lib/jenkins/workspace/ -maxdepth 1 -type d -mtime +1 -exec rm -rf {} \;

Which will find any directories that are older than 1 day and delete them.

Low available disk space on Jenkins

One possible cause of this is that the /var/lib/docker directory is consuming a large amount of disk space. This has been found to happen on the ci-agent machines.

Verify this:

cd /var/lib
sudo ncdu

If /var/lib/docker is consuming a large amount of disk space run the following as root:

docker rmi $(docker images --filter "dangling=true" -q --no-trunc)
docker volume rm $(docker volume ls -qf dangling=true)

This will remove ‘dangling’ images and volumes. A comprehensive set of instructions can be found is this Docker resource cleanup gist.

More about Icinga alerts

This page was last reviewed . It needs to be reviewed again by the page owner #2ndline.