Where could i find the stdout.txt and stderr.txt log files for the Start Task operation when the pool node reboots?

Dan 21 Reputation points
2020-07-08T16:39:21.51+00:00

I am trying to install some R packages globally on a Azure -> Batch Account -> Pool -> Node. I have the following lines in the Pool -> Start Task textarea:

cmd /c RScript.exe  -e "install.packages('rpart', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('dplyr', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('partykit', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('party', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('lme4', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('nlme', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('REEMtree', repos='https://cran.rstudio.com/')"  
cmd /c RScript.exe  -e "install.packages('rattle', repos='https://cran.rstudio.com/')"  

When remoting into the node using RDP to check that they were all installed. I found that partykit and REEMtree were not installed. So i want to find out why.

Where are the stdout.txt and stderr.txt logs located for the Start Task operation when a pool node reboots?

I read on this page: https://learn.microsoft.com/en-us/azure/batch/batch-pool-node-error-checking that there is a place:

"As with any task, there can be many causes for the start task failing. To troubleshoot, check the stdout, stderr, and any further task-specific log files."

Where is this place in the Azure Portal UI? I cannot seem to find a Run ID for the start task operation to look up in the Job Task View.

Thanks

Azure Batch
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
336 questions
{count} votes

Accepted answer
  1. prmanhas-MSFT 17,906 Reputation points Microsoft Employee
    2020-07-17T06:32:06.833+00:00

    @Dan-8327 Apologies for the delay in response and all the inconvenience caused because of this issue.

    stdout and stderr files are present in the temporary drive as mentioned in the documentation.

    Since you are not able to locate the logs of rscript command in stdout comand, I am suspecting this is not able to capture command line outputs. One of the way which I can think of to get the logs is to use redirection operator in the command itself so that output is logged into files directly.

    You can read about redirection of cmd output and error to file from here.

    By using above approach, your command could transform into

    cmd /c RScript.exe -e "install.packages('rpart', repos='https://cran.rstudio.com/';)"; >> routput.log 2>> rerror.log

    (Make sure to use >> operator instead of > operator which would override the file in next cmd command)

    After this, you will be able to see routput.log and rerror.log in the temporary storage and identify the cause of the actual problem.

    Hope this helps.

    Please 'Accept as answer' if it helped, so that it can help others in the community looking for help on similar topics

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.