What happened to `release_command` logs?

1

We used to be able to see the output of php artisan migrate (Laravel app) in our release_command, but it’s not visible anymore. I am not sure where this went wrong. Maybe it’s gone since v2?

Running salonbase release_command: php artisan migrate --force
  Created release_command machine 6e82957cd27987
  Waiting for 6e82957cd27987 to have state: started
  Machine 6e82957cd27987 has state: started
  Waiting for 6e82957cd27987 to have state: destroyed
  Machine 6e82957cd27987 has state: destroyed
  Waiting for 6e82957cd27987 to get exit event
  release_command 6e82957cd27987 completed successfully

I used to be able to see the output, like:


   INFO  Running migrations.  

  2023_06_28_164709_remove_unused_fields ................................................................................................ 346ms DONE

cc @fideloper-fly might this be something caused by the new Docker containers?

1 Like
2

Anythings possible but I’d be surprised if the output was hiding from stdout (or stderr) in a way that the logs couldn’t capture.

How “new” are we talking? The Docker containers in use right now on a new app have been the same for a bunch of months. (roughly this past December/January)

3

I did a bit of a binary search on our Github actions and found this: May 24th we got some logs, May 26 they were gone, so probably does not have to do with the new containers!

4

I see I added the primary_region key to fly.toml on 26/05. I think that was a fix for the v2 migration. Maybe something that changed v1 → v2?

5

Hi!

Is this the output of flyctl we’re talking about, or fly logs? I’m curious if that output is in fly logs but not shown in the fly deploy command.

I just learned that in v2, the output may only be output during the fly deploy... command if the release_command exits with a non-zero status code.

Do you see the expected output in fly logs?

6

Is this the output of flyctl we’re talking about, or fly logs? I’m curious if that output is in fly logs but not shown in the fly deploy command.

It seems to be the case indeed that they show up in fly logs. It’s impractical to need to look at those logs to see the output of the release command because it’s also flooded with logs from other VMs.

Would be great if we could see it in the fly deploy.

the output may only be output during the fly deploy... command if the release_command exits with a non-zero status code.

I don’t think we return non-zero status code. And this is only known after the release command ran, right? Our release_command can take a looong time, so it would only know to output after the whole thing ran? I look at it to see how far it is. If it only gives output after finishing it, then it’s much less useful.

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.