Any tips on diagnosing NATS config issues in fly-log-shipper?
Starting the latest version from git (0.0.6/9c71cd56dabe2a71243ea855aee658096b0f98b3), I see the following:
[info]Machine started in 828ms
[info]Configured sinks:
[info]aws_s3
[info]2025-06-09T05:57:59.271112Z INFO vector::app: Log level is enabled. level="vector=info,codec=info,vrl=info,file_source=info,tower_limit=trace,rdkafka=info,buffers=info,lapin=info,kube=info"
[info]2025-06-09T05:57:59.279616Z INFO vector::app: Loading configs. paths=["/etc/vector/vector.toml", "/etc/vector/sinks"]
[info]2025/06/09 05:57:59 INFO SSH listening listen_address=[...]:22
[info]2025-06-09T05:58:00.584705Z ERROR vector::topology: Configuration error. error=Source "nats": NATS Connect Error: unexpected line while connecting: Err("Authorization Violation")
[info] INFO Main child exited normally with code: 78
[info] INFO Starting clean up.
[info] WARN could not unmount /rootfs: EINVAL: Invalid argument
I tried to use fly ssh to connect to the machine, but I receive:
Error: app ... has no started VMs.
It may be unhealthy or not have been deployed yet.
I have the following env vars & secrets (from fly config):
Secrets
NAME
ACCESS_TOKEN
AWS_SECRET_ACCESS_KEY
Environment Variables
NAME
ORG
S3_ENDPOINT
AWS_ACCESS_KEY_ID
AWS_BUCKET
AWS_REGION
Is there a simple way to test the NATS config on the log-shipper instance? Or to see more details about exactly what is wrong?