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: docs/templates.md
+9-8
Original file line number
Diff line number
Diff line change
@@ -385,7 +385,7 @@ has failed on the resource.
385
385
386
386
```console
387
387
$ coder ssh myworkspace
388
-
⢄⡱ Waiting for [agent] to connect...
388
+
⢄⡱ Waiting for connection from [agent]...
389
389
```
390
390
391
391
While troubleshooting steps vary by resource, here are some general best
@@ -399,22 +399,23 @@ practices:
399
399
- The Coder agent startup script logs are typically stored in
400
400
`/tmp/coder-startup-script.log`
401
401
402
-
### Agent startup issues
402
+
### Agent does not become ready
403
403
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.
405
405
406
406
```console
407
407
$ coder ssh myworkspace
408
-
⢄⡱ Waiting for [agent] to finish starting up...
408
+
⢄⡱ Waiting for [agent] to become ready...
409
409
```
410
410
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.
412
412
413
413
```console
414
414
$ coder ssh myworkspace --no-wait
415
415
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: [...]
418
419
419
420
user@myworkspace $
420
421
```
@@ -424,7 +425,7 @@ If the startup script is expected to take a long time, you can try raising the t
424
425
```tf
425
426
resource "coder_agent" "main" {
426
427
# ...
427
-
delay_login_until_ready = true
428
+
login_before_ready = false
428
429
startup_script_timeout = 1800 # 30 minutes in seconds.
0 commit comments