From owner-freebsd-bugs@freebsd.org Sat Mar 19 03:56:39 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21FE8AD4F7E for ; Sat, 19 Mar 2016 03:56:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ED4EA1C55 for ; Sat, 19 Mar 2016 03:56:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u2J3ucEL073088 for ; Sat, 19 Mar 2016 03:56:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 208132] releng/10.3 (RC3) strange SIGTERM behaviour Date: Sat, 19 Mar 2016 03:56:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.3-BETA2 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: John.Marshall@riverwillow.com.au X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 03:56:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208132 Bug ID: 208132 Summary: releng/10.3 (RC3) strange SIGTERM behaviour Product: Base System Version: 10.3-BETA2 Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: John.Marshall@riverwillow.com.au FreeBSD 10.3-RC3 #0 r297005: Fri Mar 18 21:14:17 AEDT 2016 i386 FreeBSD 10.3-RC3 #0 r297005: Fri Mar 18 16:13:17 AEDT 2016 amd64 As reported to -stable@... I've just upgraded two local servers from 10.3-RC2 to 10.3-RC3. One is i386 (Pentium 4) with 1.5GB memory; the other is amd64 (Xeon E5 x 2) with 16GB. Something seems to be swallowing SIGTERM sometimes. I've never seen this before. rc scripts and service(8) hang when trying to stop some services. If I break out of the script or service command (via ctrl-C) and invoke kill(1), passing the relevant PID, the shell prompt returns immediately but the process doesn't terminate. Sending SIGKILL to the process via kill(1) does its job. I am seeing this with: squid (on both servers) ircd-ratbox (on both servers) git_daemon I am not seeing this (all seems normal) with: cupsd sendmail (on both servers) Looking back through the commits between -RC2 and -RC3, I've decided to try backing out r296976 to see if that may be related. Building now. Will take several hours. --=20 You are receiving this mail because: You are the assignee for the bug.=