We've recently began seeing these errors when running jobs against some of our Linux servers.
Info 08/29/2014 09:00:26 The job 'Linux Test BLPackage->Linux Test BLPackage' has failed on server linuxserver
Error 08/29/2014 09:00:26 Could not find a mount point containing path: /var/tmp/stage/
Info 08/29/2014 09:00:26 Package on server bmcappserver is 346 bytes in size.
Info 08/29/2014 09:00:26 Checking size of '//linuxserver/var/bmc/depot/blpackages/38e11dce-8023-4783-ba7a-637d1345b094'
Info 08/29/2014 09:00:26 Started running the deploy step job 'Linux Test BLPackage->Linux Test BLPackage' on application server 'bmcappserver-job1'(5) against target server linuxserver
Info 08/29/2014 09:00:26 Deploy Staging Job:Linux Test BLPackage; Server:linuxserver; PkgID:"38e11dce-8023-4783-ba7a-637d1345b094-626016.2"; UUID:b2db06270ba63bc9ae201d589af40bd3
This is puzzling to us, because we can log in to the "linuxserver" and verify that /var/tmp/stage is indeed mounted (in fact, /var is the mount point - we do not have a separate mount for tmp or stage at all). I can also cd over to it and create files (as a normal, non-privileged user) etc.
The BLPackage I'm deploying is a simple test job, all it does is execute a basic built-in command and terminate. I created it specifically to reproduce this issue, but we've seen it on a variety of deployment jobs.
The application server is 8.5.1, and the RSCD agent on the "linuxserver" is also 8.5.1 (build 96). Though we're also seeing this on servers running the 8.5.0 (build 469) agent as well.
Oddly enough, we were able to successfully deploy an agent upgrade bundle to the server and successfully upgrade the agent. That too writes out a directory on /var/tmp/stage and I can verify it both creates it and subsequently executes from it successfully. Yet when I go back and run a generic deploy job, it fails with the above message.
These errors seem to have started shortly after we updated to the 8.5.1 application server. However, this doesn't appear to me to have anything to do with the appserver itself, but something on the machine, and like I said above - we're experiencing the issue on agents running 8.5.1 and 8.5.0....
Has anyone else experienced this issue and can recommend a fix action or workaround? Any help would be appreciated ,thank you!