[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist

[gregory.picot....@gmail.com (JIRA)]

Title: Message Title

Gregory PICOT edited a comment on JENKINS-59790   Re: Container cannot connect to node because it doesn't exist Hi, Thank [~akom] for the retry bit, we tried it on our end to secure the jnlp connexion. The retry in itself seem seems to work great, but since we implemented it, our containers are not stopped properly on jobs doesn't end properly : The kill -15 sent on job termination is not correctly interpreted by the container, and we have to wait 10 sec for the a kill -9 to really put an end to the container. This is problematic because we have a small window where the master believe the container (and the agent related) is free to use. It could then try to start a job in it, with no chance to last long. What I could figure out is that since the entrypoint is the new script, when the $ACTUAL_ENTRYPOINT is run, it is not the PID1 PID 1, and the jar is not linked to our new entrypoint (since is it started by exec command) . When the kill -15 occur, not every process are killed, so the container stays alive. I tried to add the exec command before runnning the $ACTUAL_ENTRYPOINT, it resolve the issue of the sigterm interpretation, but we loose the retry logic... I'm still trying to figure out a solution to torward properly sigterms and keep the retry. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8455.1579082760512%40Atlassian.JIRA.