i assume it was working fine before?

yes

The 503 error lasted for about a few tens of seconds

does it still return 503, or have you since fixed it?

It recovered on its own, I didn't do anything

I would like to understand the reason for the 503 error in the project. I hope you can investigate thoroughly to prevent such errors from happening again in the future

did your app not log any errors?

I couldn't find it, or maybe I just don't know how to search for it

I learned about the 503 error from the uptime monitoring

unfortunately there isnt much to look into without error logs, going forward i would recommend adding more verbose logging to your app so that you can pinpoint any failures easier

During a 503 error, the server is unable to respond, so the app should not be able to log the error

a 503 error means your app didnt respond, it does not indicate a failure with the platform

I have provided the project ID and the specific time of the error, hoping that you can help me investigate

im sorry but if your app did not log the error it ran into there is unfortunately nothing to look into

I found some unusual logs

please share!

one-api/controller.AutomaticallyTestDisabledChannels(0x0?)

/build/controller/channel-test.go:363 +0x95

created by main.main in goroutine 1

/build/main.go:103 +0x5eb

goroutine 81 [sleep]:

time.Sleep(0x2540be400)

/usr/local/go/src/runtime/time.go:195 +0x115

one-api/controller.UpdateMidjourneyTask()

/build/controller/midjourney.go:39 +0x3e

created by main.main in goroutine 1

/build/main.go:104 +0x5f7

goroutine 98 [IO wait]:

internal/poll.runtime_pollWait(0x7fcc1079e198, 0x72)

/usr/local/go/src/runtime/netpoll.go:345 +0x85

internal/poll.(*pollDesc).wait(0xc004c59700?, 0xc0038ec000?, 0x0)

/usr/local/go/src/internal/poll/fdpollruntime.go:84 +0x27

internal/poll.(*pollDesc).waitRead(…)

/usr/local/go/src/internal/poll/fdpollruntime.go:89

internal/poll.(*FD).Read(0xc004c59700, {0xc0038ec000, 0x1000, 0x1000})

that looks like a stack, but it's missing the useful information

The log is very long, I'll just copy it

send as a file

1235401292407373824

If you need to view more logs in my project, you can retrieve the logs from May 2, 2024 8:10 AM - May 2, 2024 8:11 AM

I don't work for Railway so I am unable to do such things

Okay

the team would not be able to provide you with any more information than what is in your deployment logs on account of this not being an issue with the platform