7 Replies Latest reply on Jul 28, 2011 12:21 PM by Gerad Cruz

    File deploy Jobs fail with Multiple app servers

    Gerad Cruz

      We are seeing that when a file runs and is forked out to another app server the job fails because it is looking for the file locally on the server that it was started on and does not exist on the app server that the job was forked to. Logs below show the job was run exacuted against appserver1-js2. When it was forked to our second app server appserver2 the job looks for the file in the local directory but it isn't on appserver2.

       

      Info    Jul 21, 2011 1:33:48 PM    Started running the job 'Copy Dumpsec Utility' with priority 'NORMAL' on application server 'appserver1-JS2'(2,003,000)

      Info    Jul 21, 2011 1:33:51 PM    Executing work item File Deploy Job:Copy Dumpsec Utility; Server:UTMSA104;  on application server: appserver1-JS2

      Info    Jul 21, 2011 1:33:52 PM    Executing work item File Deploy Job:Copy Dumpsec Utility; Server:TXMSA059;  on application server: appserver1-JS1

      Info    Jul 21, 2011 1:33:52 PM    Executing work item File Deploy Job:Copy Dumpsec Utility; Server:TXMSA062;  on application server: appserver1-JS1

      Info    Jul 21, 2011 1:33:52 PM    Executing work item File Deploy Job:Copy Dumpsec Utility; Server:UTMSAP45;  on application server: appserver2

      Info    Jul 21, 2011 1:33:59 PM    The job 'Copy Dumpsec Utility' has failed

       

       

      Error    Jul 21, 2011 1:33:52 PM    nsh:1: no such file or directory: /usr/nsh/NSH/tmp/appserver1-JS2/scripts/job__f1e30913-3c59-4972-a744-614da04f732e/master_3aaee244-ea21-417b-9a5d-1be049179f61

      Error    Jul 21, 2011 1:33:53 PM    Error running master script on server UTMSAP45

       

      Is there a setting that needs to be changed or is this a bug that we need to put a request to be fixed.

       

      appserver