"no log output received from deployment" - unclear error message for template bugs #667

New Issue

cyrnel · 2025-09-15T02:23:57Z

cyrnel commented

2025-09-15 02:23:57 +00:00

I saw this error today during an abra app deploy:

? proceed? Yes
INFO initialising deployment
INFO polling deployment status
app: pending   (retries: 10, healthcheck: ?)
WARN logs: no log output received from deployment
FATA deploy in progress 🟠

It tried to start several times, but I ultimately cancelled it and couldn't find any logs.

The reason was that I had a syntax error in a templated config file (a missing {{end}} block) which prevented the config file from being rendered.

I was only able to tell this by checking journalctl -fu docker.service, which showed me this:

level=error msg="fatal task error" error="starting container failed: unable to get config from config store: failed to expand templated config mnzux0sw06du487laf0cx6tme: template: expansion:652: unexpected EOF" module=node/agent/taskmanager

Not sure if it's possible for abra to surface issues with config templating, so just documenting this issue to help people in the future :)

I saw this error today during an `abra app deploy`: ``` ? proceed? Yes INFO initialising deployment INFO polling deployment status app: pending (retries: 10, healthcheck: ?) WARN logs: no log output received from deployment FATA deploy in progress 🟠 ``` It tried to start several times, but I ultimately cancelled it and couldn't find any logs. The reason was that I had a syntax error in a templated config file (a missing `{{end}}` block) which prevented the config file from being rendered. I was only able to tell this by checking `journalctl -fu docker.service`, which showed me this: ``` level=error msg="fatal task error" error="starting container failed: unable to get config from config store: failed to expand templated config mnzux0sw06du487laf0cx6tme: template: expansion:652: unexpected EOF" module=node/agent/taskmanager ``` Not sure if it's possible for abra to surface issues with config templating, so just documenting this issue to help people in the future :)

cyrnel closed this issue

2025-09-15 02:23:59 +00:00

decentral1se commented

2025-09-15 07:37:32 +00:00

Fuck me, docker spits the errors out in the weirdest places... i think the tasks of a deployment (aka "fatal task error") can indeed be collected async and errors could be reported. This was also hinted at in #613 and I think we have to make some progress here because we're not seeing the real errors... let's open it and I'll try to hunt it down! Thanks for reporting!

Fuck me, docker spits the errors out in the *weirdest* places... i think the tasks of a deployment (aka "fatal task error") can indeed be collected async and errors could be reported. This was also hinted at in #613 and I think we have to make some progress here because we're not seeing the real errors... let's open it and I'll try to hunt it down! Thanks for reporting!

decentral1se reopened this issue

2025-09-15 07:37:32 +00:00

decentral1se added the

enhancement

label 2025-09-15 07:46:10 +00:00

decentral1se added this to the Abra "next" project 2025-09-15 07:46:23 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#667