From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 7173214 for ecs-isp@2rosenthals.com; Sun, 21 May 2023 13:10:51 -0400 Received: from [192.168.200.201] (port=45102 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1q0mZs-0004yM-2W for ecs-isp@2rosenthals.com; Sun, 21 May 2023 13:10:40 -0400 Received: from mta-102a.earthlink-vadesecure.net ([51.81.61.66]:54557) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1q0mZp-00052N-1S for ecs-isp@2rosenthals.com; Sun, 21 May 2023 13:10:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=B4JGPalZ+VQAoQNPOnjPAmAjJusqx1iLTooalc 6CWQk=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1684689037; x=1685293837; b=bX6fpVlQv1RHRiBiGaM0b2H3xSd5hlLJml2yMeaHpw1dIYbkPEcj+1k EGqeKlIvbtHWDafLSCo1Ho44JGb/BHxFKKj9zfl5+PlHomzGdyyDf14ha3YMxELmr8YGBhE 5SSOiTfckIVb5TD4SanEX91F4bH4IgY0P9CPwxZYLuav7jDsAPxIhS3JJOIwRasr1mPwL/E E+00DAs29aqTolmctIW31Qfl6SinFjw58zUJMeh4w6Zj5nImW4f3e6RdVVAhDCIgzYK4hmh MmRB/ah9qRhF7l/zD3uKzxnmv8RGvfjxnF4fjTdGXzmGPBTJwKzq22Xu2gGXgfPMOtXKfZj BYA== Received: from slamain ([108.193.252.151]) by vsel1nmtao02p.internal.vadesecure.com with ngmta id 3909e157-176137c0c4ddccf6; Sun, 21 May 2023 17:10:36 +0000 Message-ID: <646a4f43.14.mr2ice.fgrirsq@earthlink.net> Date: Sun, 21 May 2023 10:05:07 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Fwd: New BIND Releases are available: 9.11.37, 9.16.27, and 9.18.1 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 05/17/23 at 10:27 AM, "Massimo S." said: Hi there, >if i upgrade to 9.11.36 >https://smedley.id.au/tmp/bind-9.11.36-os2-20220304.zip or 9.11.37 >https://smedley.id.au/tmp/bind-9.11.37-os2-20220318.zip >cpu usage go to 100% on named process, that becomes "unkillable zombi" >and can't be killed/closed I noticed similar behavior with dig and suspect that bind has the same issue. See my message to the list. Dig can be killed with top's forced kill. The same is probably true for bind. It does not solve the problem, but it avoids the need to reboot while testing. To see where the hang occurs, try 9.11.37's dig with dig -dddd pmoylan.org 9.12.4 does not hang, so fixing 9.11.37 might be any easy short term fix. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------