`func start` on Linux won't stop upon recieving SIGTERM
See original GitHub issueIf I execute func start
on Linux and then send a termination request (kill -s SIGTERM <pid>
), the local runner will ignore the request.
Sending a termination signal like this should result in the program closing. Instead, the process stays open indefinitely.
Interestingly, SIGINT works just fine.
I’m running Linux and I’ve tested this with both a Node project and a Java project.
This is currently preventing the Azure Functions Gradle Plugin from shutting down down the azureFunctionsRun
task correctly, which is a huge usability problem for that plugin. However, the root issue remains in func start
.
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:7
Top Results From Across the Web
Azure functions core tools: func start on linux agent won't ...
func start on linux agent won't stop after receiving a SIGTERM command: -We have a build pipeline that runs a node application
Read more >blocking function accept() restarts when SIGINT occurs ...
In one of the pthreads I have a call to accept() function. I have a signal handler which is invoked upon receiving of...
Read more >systemd killmode: send SIGTERM to child processes?
I'm trying to systemctl stop a shell script that runs a few subcommands. However, because the shell script traps several signals, the script ......
Read more >macos - Is there a way to prevent SIGKILL after SIGTERM ...
Yes, this is definitely possible. If you start your service properly via launchd, you can define the amount of time you need for...
Read more >When pressed ctrl+c only break out of current function and ...
E.g. asynchronous processes started in a script ignore SIGINT . This way they don't react to Ctrl + c despite being in the...
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
Is there any update on this issue? We are getting this issue as well in our build pipelines when trying to run integration tests
Link #3222