Exiting with status 15 (Received SIGTERM)
See original GitHub issueI have been using Lounge for a few months now and while I love it there is 1 problem that keeps bugging me. Every once and a while the IRC server will close the connection and there is (as far as I know) no option to reconnect. This means I should either remove the IRC server and connect again (resulting in me having te manually join all the channels again) or restart the whole Node process resulting me in disconnecting from all the servers.
Message in Lounge itself:
Exiting with status 15 (Received SIGTERM)
Result in the console:
Client#connect(): Error: This socket has been ended by the other party
So is there a way to auto reconnect or at the very least a quick manual way to reconnect?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
What is "Signal 15 received" - Stack Overflow
This indicates the linux has delivered a SIGTERM to your process. This is usually at the request of some other process (via kill()...
Read more >SIGTERM : Linux Graceful Termination | Exit code 143, Signal ...
SIGTERM (signal 15) is used in Unix-based operating systems, such as Linux, to terminate a process. The SIGTERM signal provides an elegant way...
Read more >When does the system send a SIGTERM to a process?
Nice explanation of how exit status is determined upon receiving a signal. However, this answer doesn't address OP's question. – codeforester.
Read more >Graceful Termination of Linux Containers (Exit Code 143)
SIGTERM (signal 15) is the Unix process termination signal. It's the first method the kernel uses when it needs to kill a process....
Read more >Process termination - IBM
SIGTERM, (signal 15) is a request to the program to terminate. If the program has a signal handler for SIGTERM that does not...
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
Fixed in 2.0.0. Hopefully we’ll get to a stable release very soon 😃
Aha. Reconnection support didn’t come until after that. See about having
npm install thelounge@next
for the latest prerelease.