#How to debug using cloud trace?

1 messages · Page 1 of 1 (latest)

tepid haven
#

I am using dagger after a few weeks' break and I encountered the following error:

✘ Service.up: Void 2.9s
! failed to start host service: start upstream: start dependent services: start 75sppapgp3d5m

Error: response from query: input: container.from.withNewFile.withNewFile.withNewFile.withServiceBinding.withExposedPort.withNewFile.withServiceBinding.withExposedPort.withNewFile.withServiceBinding.withExposedPort.withExec.asService.up resolve: failed to start host service: start upstream: start dependent services: start 75sppapgp3d5m (aliased as monolith): exited: exit code: 1

Trace: https://dagger.cloud/esafak/traces/261dade85f2982349b577ce3a79815b5

quartz nexus
tepid haven
#

The CLI, yes, to 0.13.5. Do I need to do it in a particular way not to break the scripts?

quartz nexus
#

seems like your monolith service is not being able to start

#

if you have a function that returns that service, what I generally do is dagger call monolith up and check why the service failed to start

#

also try adding -vvv as that might output some more relevant information

#

silently pinging @past cipher to double check if this error tracking is handled in the upcoming trace UI version

#

where when a service fails, it's hard to pin-point which exec failed exactly

tepid haven
quartz nexus
tepid haven
#

The problem is that the user naturally digs in to the failed, 'red' events, but that's not where the error was, unless I'm using the product incorrectly. How did you zero in on it?

quartz nexus
tepid haven
#

It refers to start 75sppapgp3d5m (aliased as monolith) but I do not know how to find it. Is there a search feature?

quartz nexus
tepid haven
#

I'm trying to understand the color coding. Is this entry's expansion icon (top left in your screenshot) colored red to indicate a failure? Yet, the monolith withService has a green checkmark.

The UI is giving me unclear signals.

quartz nexus
tepid haven
#

How to debug using cloud trace?

past cipher
#

yeah the UI is not great around services right now - there are improvements ready to ship, I'll make sure to check on this specific case too where the service fails to start. Is the repo for this public by any chance so I can try running it and confirm the UX is solid?

past cipher