a year ago
[Nest] 27 - 03/31/2025, 5:49:28 AM LOG [NestApplication] Nest application successfully started
Stopping Container
Starting Container
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c nest start
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-03-31T05_49_18_864Z-debug-0.log
npm warn config production Use --omit=dev instead.
> dog-grooming-bot@0.0.1 start
> nest start
[Nest] 27 - 03/31/2025, 5:59:02 AM LOG [NestFactory] Starting Nest application...
5 Replies
a year ago
how can i reach to the npm logs? i dont think i have access to that actual container..
a year ago
You can use Railway-SSH to login into your container: https://docs.railway.com/reference/cli-api#ssh
a year ago
Thanks!
I tried it, I did railway link (to my service) then railway ssh and god:
Expected welcome message, received: error
note: railway logs working as expected.
update:
when i try to build with RailPacki got:
> railway ssh
Connected to interactive shell
Error: Session error
a year ago
Were you able to check your logs? We might have had deploys that caused the session error transiently
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
First, regarding to the main question, The crashes started after I've activated the serverless option, now, I've disabled the serverless option and seems that the service is not crashes (which should be only on sleep).
I'm trying to understand why when I'm turning on the serverless options its considered as 'crashed' in somepoint.
Regarding the logs, yes when i ran railway logs i could see the logs which indicates the railway CLI is configured and linked successfully.
I will try today to run railway ssh again and let you know if it worked or not.
Status changed to Awaiting Railway Response Railway • 12 months ago
Status changed to Solved brody • 12 months ago