Running Go Enterprise 2.2 on RedHat Linux. Agnt installed on same server as server, one of my pipelines has started failing because it is not loading the artifact generated.
This pipeline has been running successfully for sometime now, it has only started behaving like this since yesterday.
I have verified that the artifact exists in the go-agent directory structure, and that it's less than 1Gb.
I can see the following error in the go-agent log file:
2011-07-20 09:04:40,676 [loopThread] ERROR thoughtworks.cruise.publishers.CruiseArtifactsManipulator:75 - Failed to upload /customer/product/go/go-agent-2/pipelines/Oldstack_CI/target/britishgas.ear.tar
java.io.IOException: No space left on device
Which points to a disk being full. However the disk go is installed on has 150Gb free (as reported both by the Agent menu in Go, and directly on the server).
My question therefore is what device does go think has reached capacity?