Thursday, 20 April 2017

why netstat not listing server.js service in the output?

[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2

[PM2] PM2 Successfully daemonized

[PM2] Starting /tmp/server.js in fork_mode (1 instance)

[PM2] Done. ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬───────────┬──────────┐ │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │ ├──────────┼────┼──────┼─────┼────────┼─────────┼────────┼─────┼───────────┼──────────┤ │ server │ 0 │ fork │ 22 │ online │ 0 │ 0s │ 26% │ 27.2 MB │ disabled │ └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴───────────┴──────────┘

Use pm2 show <id|name> to get more details about an app

root@1c11163d76ae:/tmp# netstat -ltnp

Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name

root@1c11163d76ae:/tmp# netstat -at

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State

My server.js script started successfully in the container. but when i run command netstat -ltnp , it is giving me empty output, rather than listing service on particular port.

why netstat not listing server.js service in the output?



via Govind Jadhav

No comments:

Post a Comment