Is the file server on the same server as appserver1
Yes the files server is appserver1
And did you make you fileserver "localhost" when you installed the appserver?
No it is set to the host name, not "localhost" either way it is look for a local address not one on the file server as is designated by the path in the log file. "/usr/nsh/NSH/tmp/appserver1-JS2/scripts/job__f1e30913-3c59-4972-a744-614da04f732e/master_3aaee244-ea21-417b-9a5d-1be049179f61"
You need to have an alias for the fileserver and set this in the local hosts file on each of the appservers.
hosts file entry
depends on OS.
Set fileserver as blfs.
This way whenever it tries to find a file it will use:
Using an Alias also makes it much easier if you need to move the fileserver (in a disaster recovery situation for example).
This has nothing to do with our file server. The file it is looking for is in the applcations servers temp space in the NSH directory.
The problem appears to be that the job creates a file on one app server and then forks it to a thread on another app server where the file does not exist. This appears to be a bug we are wanting to know if anyone else has seen this or has a work around.
1 of 1 people found this helpful
Just got more information for BMC Support
I have found a Defect# QM001714008 has already beenlogged recently for the same issue. The description for the defect as follows:
"what is happening is that when the job is kickedoff on appserver A and the targets get processed from appserver A it worksfine, however when it shares out the work items to appserver B it does not copythe file being deployed to the /tmp/application_server/scripts directory to beable to process the targets associated with appserver B."
Hopefuly the fix will be out soon.