Respond correctly to --killSignal (was: no logging after graceful shutdown)
See original GitHub issueWhenever I shutdown a script using --killSignal=SIGTERM
(cf. #320), all the operations executed after running forever stop
are not show in the logs anymore.
You can observe this problem on forever-monitor graceful exit example
- run
forever start --killSignal=SIGTERM graceful-exit.js
- run
forever stop graceful-exit.js
- check the produced produced log. The sentence ‘Exiting after some time.’ should appear, but it does not.
Am I missing something?
This is not a really big deal, as at least these instructions are being executed (only the logging in forever log file is not performed).
This happens to me on node 0.8.17, and current master version of forever and forever-monitor.
Issue Analytics
- State:
- Created 11 years ago
- Reactions:1
- Comments:15
Top Results From Across the Web
Respond correctly to --killSignal (was: no logging after graceful ...
Whenever I shutdown a script using --killSignal=SIGTERM (cf. #320), all the operations executed after running forever stop are not show in the logs...
Read more >In what order should I send signals to gracefully shutdown ...
BTW, the KILL: it is not wrong to send SIGKILL to a process, as other answer stated. Well, think what happens when you...
Read more >Waiting indefinitely for the logging system to shut down
A subsequent restart will recognise that the shutdown was not graceful and simply recommence processing the transaction log file locking you ...
Read more >952634 – RFE: We should have a way for KillSignal to apply ...
This means that httpd should shutdown gracefully [1]. However, systemd sends SIGTERM *right* after ExecStop execution without any configurable timeout.
Read more >Graceful Shutdown in NodeJS - Medium
After that, you can shut down your server with a quiet conscience. Graceful shutdown means when all your requests to the server is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1 Not only SIGTERM, all signals=(
Any workaround for console.log?