You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/extensions/custom-script-linux.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -390,13 +390,13 @@ We recommend that you use [PowerShell](/powershell/module/az.Compute/Add-azVmssE
390
390
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.
391
391
392
392
```bash
393
-
ls -l /var/lib/waagent/custom-script/download/0/
393
+
sudo ls -l /var/lib/waagent/custom-script/download/0/
394
394
```
395
395
396
396
To troubleshoot, first check the Linux Agent Log and ensure that the extension ran:
397
397
398
398
```bash
399
-
cat /var/log/waagent.log
399
+
sudo cat /var/log/waagent.log
400
400
```
401
401
402
402
Look for the extension execution. It will look something like:
@@ -420,7 +420,7 @@ In the preceding output:
420
420
The Azure Script Extension produces a log, which you can find here:
421
421
422
422
```bash
423
-
cat /var/log/azure/custom-script/handler.log
423
+
sudo cat /var/log/azure/custom-script/handler.log
424
424
```
425
425
426
426
Look for the individual execution. It will look something like:
0 commit comments