Deploy Successful, Then SIGTERM and app stops.
phsemple
HOBBYOP

a year ago

========================================================

I am adding this part after reading some earlier problems with SIGTERM:

Is my app deploying and I am just seeing the SIGTERM to show the clearing of earlier deploys?

If so, how do I find the URL to start my app? I have tried:

https://tts2-production.up.railway.app

and https://beneficial-peace-production.up.railway.app/, but no luck.

if not, then read on!

Thanks

========================================================

Brand new to deploying a project, so first time battling the beasts.

Node.js/express.

MySql database.

Deployed through github repository

Deploy marked as successful: but here it the log from Observability

==================================================
Starting Container

npm warn config production Use --omit=dev instead.

> tts2@1.0.0 start

> node app.js

** these are my console logs

host: mysql.railway.internal

user: root

database: railway

Express Static is: /app/public

Running on the railway this is my PORT 8080

Listening on Port 8080

Connected to MySQL database: railway

=================================================

** at this point I appear to be properly listening on the port.

** but now things head south

** The following lines do not show up in the Project Deployment Log,

** I only found them after going to Observability Logs

=================================================

Stopping Container

npm error path /app

npm error command failed

npm error signal SIGTERM

npm error command sh -c node app.js

npm error A complete log of this run can be found in: /root/.npm/_logs/2025-04-04T23_49_22_150Z-debug-0.log

Solved

4 Replies

a year ago

Hello,

Those logs are only happening on your old deployments when a new deployment goes live, there is no functional issue here and nothing to worry about.

Best,
Brody


Status changed to Awaiting User Response Railway 11 months ago


Status changed to Solved brody 11 months ago


brody

Hello,Those logs are only happening on your old deployments when a new deployment goes live, there is no functional issue here and nothing to worry about.Best,Brody

phsemple
HOBBYOP

a year ago

Thanks, I appreciate it.

Now I have the question that started me looking for an error that wasn't there: what is the URL? I have tried https://tts2-production.up.railway.app and https://beneficial-peace-production.up.railway.app/, It doesn't seem to appear anywhere on the project services.

The first test app I deployed a few days ago did not node.js or a database. It gave me the URL on the project as: abundant-analysis africastories-production.up.railway.app.


Status changed to Awaiting Railway Response Railway 11 months ago


a year ago

The linked service does not have a URL, you would need to go into the service settings to generate one!


Status changed to Awaiting User Response Railway 11 months ago


Status changed to Solved phsemple 11 months ago


brody

The linked service does not have a URL, you would need to go into the service settings to generate one!

phsemple
HOBBYOP

a year ago

Thank you. Everything works much better.


Status changed to Awaiting Railway Response Railway 11 months ago


Status changed to Solved brody 11 months ago


Loading...