2 months ago
Not seeing any logs / memory usage out of the ordinary. This is the second time something like this has happened to this service.
2026-03-26T00:00:02.688089958Z [inf] 2026-03-26T00:00:02.688095339Z [inf] > unison@1.1.0 db:migrate /app 2026-03-26T00:00:02.688100431Z [inf] > tsx src/db/migrate.ts 2026-03-26T00:00:02.688105803Z [inf] 2026-03-26T00:00:02.688111722Z [inf] [36mINFO [0m [35m[db][0m migration completed successfully 2026-03-26T00:00:04.885220702Z [inf] 2026-03-26T00:00:04.885229940Z [inf] > unison@1.1.0 start /app 2026-03-26T00:00:04.885235956Z [inf] > tsx src/index.ts 2026-03-26T00:00:04.885241068Z [inf] 2026-03-26T00:00:05.858882546Z [inf] [36mINFO [0m [37m[app][0m listening on port 8080 2026-03-26T03:54:16.136545578Z [inf] [36mINFO [0m [36m[http][0m HEAD / 200 2.6ms [2m|[0m [2mmethod[0m=HEAD [2mpath[0m=/ [2mstatus[0m=200 [2mlatency_ms[0m=2.6 2026-03-26T03:54:25.976742083Z [inf] [36mINFO [0m [36m[http][0m GET / 200 0.6ms [2m|[0m [2mmethod[0m=GET [2mpath[0m=/ [2mstatus[0m=200 [2mlatency_ms[0m=0.6 2026-03-26T04:49:38.474583515Z [err] [33mWARN [0m [36m[http][0m GET /robots.txt 404 0.5ms 2026-03-26T04:49:38.474592346Z [inf] [36mINFO [0m [36m[http][0m GET / 200 0.3ms [2m|[0m [2mmethod[0m=GET [2mpath[0m=/ [2mstatus[0m=200 [2mlatency_ms[0m=0.3
Attachments
6 Replies
2 months ago
This question appears to be about your application code rather than the Railway platform, which is outside the scope of what we can help with.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 2 months ago
2 months ago
think you might be spot on with the DB connection pool issue, let me try to get that going + adding unhandled rejection listeners
2 months ago
Hello,
the crash is completely silent which in node.js means its almost certainly an unhandled promise rejection killing the process before anything can be logged. add these two listeners right after your app starts and it will tell you exactly whats crashing next time:
process.on('unhandledRejection', (reason) => { console.error('unhandled rejection:', reason); process.exit(1); });
process.on('uncaughtException', (err) => { console.error('uncaught exception:', err); process.exit(1); });
2 months ago
this wont fix it yet but it will finally give us the actual error in your logs so you know what youre dealing with, let me know the result
2 months ago
Just got it deployed
I’m 90% certain its a db connection issue but ill get back with logs if it happens again, appreciate it!
2 months ago
nice, fingers crossed the listeners catch it if it happens again, good luck!
