Railway•6mo ago

I got an email to say a build had failed but there are no errors in the logs

email came at 6am, there are no errors in the last 24 hours, it built many times and all logs look normal

Solution:

ah I can see there was an incident in #🚨｜incidents

Jump to solution

8 Replies

Percy•6mo ago

Project ID: 61398dc5-6b4a-40c8-a31f-d56ffd752011

Joe LanmanOP•6mo ago

61398dc5-6b4a-40c8-a31f-d56ffd752011 ah, found a couple of errors, but both around 1am, and doesnt look like my code

Backup started

node:internal/process/promises:289

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect EHOSTUNREACH 35.212.174.161:52533

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) {

errno: -113,

code: 'EHOSTUNREACH',

syscall: 'connect',

address: '35.212.174.161',

port: 52533

}

Node.js v20.14.0

Backup started

node:internal/process/promises:289

triggerUncaughtException(err, true /* fromPromise */);

^

Error: connect EHOSTUNREACH 35.212.174.161:52533

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) {

errno: -113,

code: 'EHOSTUNREACH',

syscall: 'connect',

address: '35.212.174.161',

port: 52533

}

Node.js v20.14.0

(the other error is the same)

Solution

Joe Lanman•6mo ago

ah I can see there was an incident in #🚨｜incidents

Brody•6mo ago

once the incident has resolved let me know if you continue to experience this, but you should be using the private network to connect to your database

Joe LanmanOP•6mo ago

thanks, I'll look into that, out of interest whats the difference? Quicker?

Brody•6mo ago

yes and there no egress on private network traffic

Joe LanmanOP•6mo ago

closing this one as it is from the earlier incident

Brody•6mo ago

sounds good

Gaming

Programming

I got an email to say a build had failed but there are no errors in the logs