Skip to content

Commit 2531af2

Browse files
Update custom-script-linux.md
1 parent 098149b commit 2531af2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/virtual-machines/extensions/custom-script-linux.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -390,13 +390,13 @@ We recommend that you use [PowerShell](/powershell/module/az.Compute/Add-azVmssE
390390
When the Custom Script Extension runs, the script is created or downloaded into a directory that's similar to the following example. The command output is also saved into this directory in `stdout` and `stderr` files.
391391

392392
```bash
393-
ls -l /var/lib/waagent/custom-script/download/0/
393+
sudo ls -l /var/lib/waagent/custom-script/download/0/
394394
```
395395

396396
To troubleshoot, first check the Linux Agent Log and ensure that the extension ran:
397397

398398
```bash
399-
cat /var/log/waagent.log
399+
sudo cat /var/log/waagent.log
400400
```
401401

402402
Look for the extension execution. It will look something like:
@@ -420,7 +420,7 @@ In the preceding output:
420420
The Azure Script Extension produces a log, which you can find here:
421421

422422
```bash
423-
cat /var/log/azure/custom-script/handler.log
423+
sudo cat /var/log/azure/custom-script/handler.log
424424
```
425425

426426
Look for the individual execution. It will look something like:

0 commit comments

Comments
 (0)