Skip to content

Commit c3f75d5

Browse files
committed
Update docs to align with #5893
1 parent 53b3038 commit c3f75d5

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

docs/templates.md

+9-8
Original file line numberDiff line numberDiff line change
@@ -385,7 +385,7 @@ has failed on the resource.
385385

386386
```console
387387
$ coder ssh myworkspace
388-
⢄⡱ Waiting for [agent] to connect...
388+
⢄⡱ Waiting for connection from [agent]...
389389
```
390390

391391
While troubleshooting steps vary by resource, here are some general best
@@ -399,22 +399,23 @@ practices:
399399
- The Coder agent startup script logs are typically stored in
400400
`/tmp/coder-startup-script.log`
401401

402-
### Agent startup issues
402+
### Agent does not become ready
403403

404-
If the agent does not start, it means the [startup script](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script) is still running or has exited with a non-zero status. This also means the [delay login until ready](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#delay_login_until_ready) option is enabled.
404+
If the agent does not become ready, it means the [startup script](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#startup_script) is still running or has exited with a non-zero status. This also means the [login before ready](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/agent#login_before_ready) option hasn't been set to true.
405405

406406
```console
407407
$ coder ssh myworkspace
408-
⢄⡱ Waiting for [agent] to finish starting up...
408+
⢄⡱ Waiting for [agent] to become ready...
409409
```
410410

411-
To troubleshoot startup issues, check the agent logs as suggested above. For startup issues you can connect to the workspace using SSH with the `--no-wait` flag. Please note that while this makes login possible, the workspace may be in an incomplete state.
411+
To troubleshoot readiness issues, check the agent logs as suggested above. You can connect to the workspace using `coder ssh` with the `--no-wait` flag. Please note that while this makes login possible, the workspace may be in an incomplete state.
412412

413413
```console
414414
$ coder ssh myworkspace --no-wait
415415

416-
> The workspace agent is taking longer than expected to
417-
start. See troubleshooting instructions at: [...]
416+
> The workspace is taking longer than expected to get
417+
ready, the agent startup script is still executing.
418+
See troubleshooting instructions at: [...]
418419

419420
user@myworkspace $
420421
```
@@ -424,7 +425,7 @@ If the startup script is expected to take a long time, you can try raising the t
424425
```tf
425426
resource "coder_agent" "main" {
426427
# ...
427-
delay_login_until_ready = true
428+
login_before_ready = false
428429
startup_script_timeout = 1800 # 30 minutes in seconds.
429430
}
430431
```

0 commit comments

Comments
 (0)