Sometimes I get a "ERRO[0000] failed to send system signal to the process" #16
Comments
|
got the same issue. |
|
@jonatiao can you attach Pod yaml and commands to reproduce the problem? |
|
Oh. I'm not working anymore for the company I implemented a solution based on secrets-init. Still, I have the deployment manifest template.. but I cannot simulate it anymore since I'm not there. deployment-with-gcp_svc_account.txt ps. Can´t attach yaml files. So here it goes as .txt, please rename it. |
n-e
added a commit
to n-e/secrets-init
that referenced
this issue
May 26, 2023
Since go 1.14, SIGURG is emitted internally by the fo runtime, see: - golang/go#37942 - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md#other-considerations "Choosing a signal" This causes two problems: - This will interfere with processes that use SIGURG for a real purpose (though this is unlikely) - If SIGURG is emitted after the child process has exited but before secrets-init, there will be a spurious error message (see doitintl#16)
n-e
added a commit
to n-e/secrets-init
that referenced
this issue
Jun 5, 2023
Since go 1.14, SIGURG is emitted internally by the fo runtime, see: - golang/go#37942 - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md#other-considerations "Choosing a signal" This causes two problems: - This will interfere with processes that use SIGURG for a real purpose (though this is unlikely) - If SIGURG is emitted after the child process has exited but before secrets-init, there will be a spurious error message (see doitintl#16)
n-e
added a commit
to n-e/secrets-init
that referenced
this issue
Jun 5, 2023
Since go 1.14, SIGURG is emitted internally by the fo runtime, see: - golang/go#37942 - https://go.googlesource.com/proposal/+/master/design/24543-non-cooperative-preemption.md#other-considerations "Choosing a signal" This causes two problems: - This will interfere with processes that use SIGURG for a real purpose (though this is unlikely) - If SIGURG is emitted after the child process has exited but before secrets-init, there will be a spurious error message (see doitintl#16)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
secrets-init:0.4.0
Sometimes, I don't know why, I get these errors:
kubectl exec --stdin --tty mypod-init -- /bin/ash Defaulted container "mypod-cm" out of: mypod-cm, writefile (init) / # /tmp/bin/secrets-init --provider google envGOOGLE_APPLICATION_CREDENTIALS=/credential/credentials.jsonPASS=It worked!ERRO[0000] failed to send system signal to the process args="[env]" error="no such process" path=/usr/bin/env pid=23 signal=SIGURGsecrets-init is doing its job, the PASS was translated. Still, I get the error below sometimes, pretty rare, but it happens.
ERRO[0000] failed to send system signal to the process args="[env]" error="no such process" path=/usr/bin/env pid=23 signal=SIGURG
The text was updated successfully, but these errors were encountered: