Hudson fails with error "No space left on device" though there is enough space on the system [closed]

The "no space left on device" error isn't necessarily caused by running out of storage capacity, as it suggests, it can also be cause by running out of i-nodes on the filesystem. In other words, a given filesystem can only contain so many files. Running df will suggest everything's fine.

See this article for more info.

You either need to delete some files that you don't need any more, or put Hudson on a different filesystem.

It's not uncommon in situations where you know you'll have a lot of small files to build a filesystem with an explicitly larger i-node table.

It is due to overflow of memory.

run this command to check the available memory size

df

If you find 100% or near to 100% for any disk, please delete data from that directory, but be carefully, and then try again.

In most of cases, the /tmp directory will be 100%, so reboot your machine

sudo reboot

it will erase all files from tmp directory.

Also do ipcs -u and ipcs -p to see if the "out of space" is the SHM memory full and what apps is using it. If segments allocated are equal to sysctl kernel.shmmni, you are with a "full" shm. You can also compare with ipcs -l output, as this show the system limits.

Latest version of java might abuse the shm usage until it is none free. Either close the program that is abusing the shm or increase the kernel.shmmni and kernel.shmmax sysctl to increase the available shm space