You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've built the application and it's supposed to run on pm2. According to the pm2 status the application should be up and running. pm2 shows even 153MB memory usage. Hence, something must be happening.
But it's not or at least the nginx proxy can't reach the application and returns 503 "Gateway not reachable" error. That's all fine with me as long as I can find entries in some kind of log files.
But my logs are mute. No errors are being piped anywhere, neither to the nginx logs nor to pm2's general or application logs usually located in .pm2/logs .
A lot of thing could have gone wrong during this installation which is quite normal but I need to have a chance of getting informed about about problems, failures or crashes.
I have no clue how to tackle any runtime errors without being able to log them.
Here's the main part of the pm2 ecosystem.config.js:
I've used similar setups with a lot of other node applications. I'm not very fond of .env. Therefore I use the environment extensively.
Also when I run "pnpm start" the build seems to get started, like below, nothing responds on port http://localhost:3000. Again, no errors or warnings are being piped to the screen or to any log file whatsoever.
It's very likely at this early stage of my project, there might be configuration errors. But I need to be able to trace them somehow.
$ pnpm start
> [email protected] start /path/to/project/root
> solid-start start
solid-start start
version 0.2.26
adapter node
➜ Page Routes:
┌─ http://localhost:3000/*404
...
└─ http://localhost:3000/other
➜ API Routes:
┌─ http://localhost:3000/api/route1 POST
...
└─ http://localhost:3000/api/items/item:id GET | POST | DELETE | PATCH
What now, if the application doesn't listen on port 3000?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've built the application and it's supposed to run on pm2. According to the pm2 status the application should be up and running. pm2 shows even 153MB memory usage. Hence, something must be happening.
But it's not or at least the nginx proxy can't reach the application and returns 503 "Gateway not reachable" error. That's all fine with me as long as I can find entries in some kind of log files.
But my logs are mute. No errors are being piped anywhere, neither to the nginx logs nor to pm2's general or application logs usually located in .pm2/logs .
A lot of thing could have gone wrong during this installation which is quite normal but I need to have a chance of getting informed about about problems, failures or crashes.
I have no clue how to tackle any runtime errors without being able to log them.
Here's the main part of the pm2 ecosystem.config.js:
I've used similar setups with a lot of other node applications. I'm not very fond of .env. Therefore I use the environment extensively.
Also when I run "pnpm start" the build seems to get started, like below, nothing responds on port http://localhost:3000. Again, no errors or warnings are being piped to the screen or to any log file whatsoever.
It's very likely at this early stage of my project, there might be configuration errors. But I need to be able to trace them somehow.
What now, if the application doesn't listen on port 3000?
Beta Was this translation helpful? Give feedback.
All reactions