No logs showing, unable to debug tcp issues

,
1

I launched a new Fly App tonight (Sign in to Your Account · Fly), evermind is also the organization slug.

Here is my fly.toml

app = 'evermind'
primary_region = 'yyz'

[build]
  [build.args]
    GO_VERSION = '1.22'

[env]
  PORT = '8080'

[[services]]
  internal_port = 8080
  protocol = 'tcp'
  auto_start_machines = true
  auto_stop_machines = 'suspend'
  min_machines_running = 0

  [[services.ports]]
    port = 8080

[[services.tcp_checks]]
  grace_period = "1s"
  interval = "15s"
  restart_limit = 0
  timeout = "2s"

[[vm]]
  size = 'shared-cpu-1x'

I am trying to spin up a server that accepts TCP connections.

The deploy works

--> Building image done
image: registry.fly.io/evermind:deployment-01JA20FA6QVPW25TP0XQCW4JM5
image size: 7.5 MB

Watch your deployment at https://fly.io/apps/evermind/monitoring

-------
Updating existing machines in 'evermind' with rolling strategy

-------
 ✔ Cleared lease for 287457df007548
-------

and the healthchecks pass apparently

image
image2488×530 57.7 KB

but the logs are not showing so I am unable to debug why I cannot nc to my server.

image
image1920×705 19.5 KB

when I do fly logs --app evermind I get nothing as well.

Trying to open Grafana 404s.

2

I have been having the same problem for a few days now. In my case is with all my node.js servers.

When I make fly logs -a app-name.
I get Error: 422 Unprocessable Entity

3

Added logs, proxy

4

If I destroy the app and recreate it I get some initial logs but then on subsequent deploys it fails and the logs say:

$ fly logs -a evermind

Waiting for logs...

[PU01] client problem: empty string
5

A machine restart did the trick, I am now getting logs :man_shrugging:

6

Back to not having logs, there is definitely something wrong with the Fly log shipper.

7

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