Azure HDInsight脚本操作失败，如何查看对应错误日志？

Got it, let's walk through how you can dig into the error logs for that failed createLivyFolder custom script action on your Azure HDInsight cluster. The error points to a customization failure, so here are the key ways to debug this:

• Navigate to your HDInsight cluster in the Azure Portal.
• From the left menu, under Monitoring, select Script actions.
• You'll see a list of all script actions run on the cluster. Look for the createLivyFolder entry marked with a Failed status.
• Click on the failed script action, then select View logs. This will display the stdout and stderr outputs from the script execution across all target nodes, which often contains direct error details.

First, connect to your cluster using SSH (replace placeholders with your cluster details):

ssh sshuser@<your-cluster-name>-ssh.azurehdinsight.net

Once connected, you can find relevant logs in these critical directories:

• Custom script action logs: Check /var/log/custom-script-action/ – each script run gets its own subdirectory with stdout and stderr files. Look for the folder tied to the createLivyFolder action.
• Ambari agent logs: Since the error references Ambari, examine /var/lib/ambari-agent/data/ for logs related to script execution, or /var/log/ambari-agent/ambari-agent.log to see how Ambari processed the script action.
• Livy-specific logs: If the script modifies Livy configurations, you can also check Livy's logs at /var/log/livy/ to see if the folder creation failure impacted Livy's setup.

• Open the Ambari UI for your cluster (you can grab the URL from the Azure Portal's cluster overview page – it follows the format https://<your-cluster-name>.azurehdinsight.net).
• Log in with your cluster credentials.
• From the top menu, go to Actions > Script Actions. Here you'll find the full history of script actions, including the failed createLivyFolder run.
• Click on the failed entry to expand details, which may include links to node-specific logs or Ambari-generated error messages explaining why the action failed.
• Additionally, head to the Services tab, navigate to Livy, and use the Logs dropdown to check if the folder creation issue caused downstream errors in Livy.

These methods should help you pinpoint exactly where the createLivyFolder script went wrong – whether it's a permission issue, missing path, typo in the script, or another runtime error.

内容的提问来源于stack exchange，提问作者dassum