Does the role performing this action have access to write to the bsa file server ? what is in the rscd.log on the file server when this happens ?
could you please share exports,users & users.local file contents.
also as Bill asked, log messages from rscd.log
And, just to be clear, you will cant to capture this from the BSA FileServer (blfs) - not the target servers right now as its not getting that far.
Yes , it's not getting far and I checked the exports and users file . Deploying to exact same server may work or not , now almost always not. Nothing in server rscd log file either.
BMC Software | Professional Services
Whats the ownership of these directories if you check with "ls -l"
the file server rscd log or the target server rscd log ?
can you attach the file server rscd log from when this happens ?
It appears that the problem happens when I use execute against but not when I add the servers or groups to the job and then run using execute.
Does that give you any ideas?
I will get the logs ASAP.
It sounds like the issue is intermittent in nature to begin with right? Perhaps it depends on which of the appservers picks it up or something like that. I would reproduce it again and capture the logs from the fileserver (blfs) but also capture those directory permissions I mentioned above.
Thank you so much guys for all your help, customer opened a case on this issue and we stopped using execute against in the interim.
Closing the loop on this thread. This issue was tracked down to a agent ACL issue on a specific appserver in the environment. For each appserver the fileserver is localhost and the storage is a mounted partition. One appserver had it's local ACLs configured incorrected so when jobs executing here would encounter the issue. Similar info also covered in KA351020.