Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SIGTERM, SIGINT seemingly ignored sometimes

See original GitHub issue

Hey, so I have this issue where, for some reason when I stop the process with ctrl + c (when debugging in vs:code) or (sometimes) restart the service with systemctl the shutdown function isnt triggered at all. When I stop the service with systemctl stop or using the UI button (break button) (when in vs:code) it works. Logs dont show any errors, or anything. Any idea?

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (8 by maintainers)

github_iconTop GitHub Comments

Pirulaxcommented, Sep 1, 2022

Hey! You can keep it closed. I haven’t encountered the issue recently. I’m still unsure what the issue was. It was quite random, as sometimes it worked (tbh, it might not’ve been an issue with the lib at all, since it seemed like the program straight out crashed, I just assumed it might be the lib, because there was no log output, but othertime there was). Anyways, I did try running the code you posted, and it worked as expected, so I don’t know what the issue was.

I’m also using Nutika, who knows, maybe a weird combo of things caused it.

Thank you for the work you put in, appreciate it!

cjrhcommented, Sep 1, 2022

I couldn’t reproduce so I’ll close the issue for now. If someone finds a reproducer we can reopen and investigate further.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Sending SIGINT to process groups sometimes gets ignored
1) Start the process group in the background and wait on the leader. SIGINT gets ignored. Execute the following command: $ bash -c...
Read more >
Why do Linux processes become unresponsive to SIGTERM ...
SIGKILL signal cannot be caught or ignored and the receiving process cannot perform any clean-up upon receiving this signal. SIGABRT signal can be...
Read more >
Catching SIGTERM vs catching SIGINT - node.js
The SIGTERM signal is sent to a process to request its termination. Unlike the SIGKILL signal, it can be caught and interpreted or...
Read more >
SIGINT And Other Termination Signals in Linux - Baeldung
However, some signals can't be ignored nor handled differently and the default action is always executed.
Read more >
Signals in prod: dangers and pitfalls - Meta for Developers
The default state for signals is not "ignored," but signal-specific. So, for example, programs don't have to configure SIGTERM manually to terminate their ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found