Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-62923

ProcessTreeKiller killing off vagrant processes with multiple executors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • core
    • None
    • Jenkins 2.222.4 and have replicated on 2.235.1, Ubuntu 18.04/x64 java from AdoptOpenJDK

      Hi, I raised this in the gitter and didn't get any replies and it seems to be a bug of some sort so I'm raising here. Marked as critical as it is causing a "crash" - not in jenkins itself but in my jobs. Happy for that to be changed if it's wrong.

       

      I've got a jenkins agent on a machine which is running jobs that create ane manage VirtualBox machines using vagrant (NOT using the vagrant plugin). The agent has multiple executors each managing separate VMs but we frequently find that when one vagrant VM ends, others are killed by the jenkins agent. We've tried setting BUILD_ID=dontKillMe in the script that does the vagrant operations to bypass the process tree killer but that doesn't seem to work all the time - I'm still seeing the jenkins agent killing the VirtualBox processes when that is set in the environemnt (often just the VBoxXPCOMIPCD process which is used for IPC between VirtualBox processes but I have seen the agent hit others directly) Other than disabling the process task killer globally which I'd rather not do as it's using for most jobs is there anything else I can do to find out why this is happening or resolve it?

            Unassigned Unassigned
            sxa Stewart X Addison
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: