From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8152 invoked by alias); 21 Mar 2018 22:07:32 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 8144 invoked by uid 89); 21 Mar 2018 22:07:32 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=D*nexgo.de, spin, stays, watched X-HELO: mail-pl0-f46.google.com Received: from mail-pl0-f46.google.com (HELO mail-pl0-f46.google.com) (209.85.160.46) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 21 Mar 2018 22:07:30 +0000 Received: by mail-pl0-f46.google.com with SMTP id x4-v6so3989969pln.7 for ; Wed, 21 Mar 2018 15:07:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=yNrfWLaSwrVt6X+fjYseem71c0FKSlp2M0AWp6SL8jc=; b=kHA7AsZWsQx23OF9jOnwnE19ZkZh072k8AExq9OVcwxUizByGVQsvLhbhDeqAQFjQd /0PYkzD+0MhUY0UB/XwsEour5uUzYc5mnbyXG3uePRPwjv1O45OdjHJU3k0IITHekYzJ UdXXauBchESYB3H/i8+Dv69i9Q3fyZmKq9S+nRQ6qLEIgA3L+KaGzPNrTBZaRmDpEVyU +EvnfNuzvUtwr7XtL+91HLS92HlmORPoE81eWg4hJDhwL+3AcVeezwfmMhHr97J6qwQL Y+dupZ3mlNwbFrQJG7ctI36rEv9F22MJA24GVkCoW3ex2kz0th33mUad8MaVbx0XEat6 e4Fw== X-Gm-Message-State: AElRT7EyYPJqf+6zsKJwwwNwQ7iXsNd2G4S/LiOexnbNPiIzWxkdRV3c 9e1hCnTyZS2THO0o+4Hnkz3pYEJJ/w34hLeRJIY= X-Google-Smtp-Source: AG47ELu2aKfGIpY72x10zZKlAYQ5CufUIiV0Zyh5D4Dk3kBts7S4qWWMqegSvZ6Zd6rToHYJPBD46oCuMpZcPKyZKls= X-Received: by 2002:a17:902:8602:: with SMTP id f2-v6mr22138519plo.6.1521670048812; Wed, 21 Mar 2018 15:07:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.154.86 with HTTP; Wed, 21 Mar 2018 15:07:28 -0700 (PDT) In-Reply-To: <877eq5fedf.fsf@Rainer.invalid> References: <877eq5fedf.fsf@Rainer.invalid> From: Dan Kegel Date: Wed, 21 Mar 2018 22:09:00 -0000 Message-ID: Subject: Re: Odd hang in python waiting for child; strace wakes hung process? To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-03/txt/msg00339.txt.bz2 On Wed, Mar 21, 2018 at 11:54 AM, Achim Gratz wrote: > Well, with the sporadic hanging/defunct processes at work my routine is > to send CONT to all Cygwin processes, then HUP/KILL to anything that's > still not live or gone and then another round of CONT. This works > _most_ of the time, anything more stubborn I /bin/kill -f usually. Since I wrote, both bots hung again. This time I verified: 0) both had the defunct git process as expected 1) kill -CONT the-pid doesn't do anything, nor does kill -9. It's truly wedged. 2) the process stays in its spin hang until you ^C strace -p the-pid 3) ^C-ing the strace causes the process to terminate (strace alone doesn't) 4) taskkill /pid the-task /f also kills the process successfully. So I could write a script that watched for defunct git processes and taskkilled their parent. Build jobs would fail, but at least the bot would stay up. Of course it would be much nicer if the cygwin python process didn't get wedged. Alternately, I suppose I could try running native python... or cygwin's python3... but dangit, kill -9 should work. - Dan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple