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 9673518 for ecs-isp@2rosenthals.com; Wed, 15 May 2024 03:50:44 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:46576 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1s79PM-0007W9-1c for ecs-isp@2rosenthals.com; Wed, 15 May 2024 03:50:40 -0400 Received: from mta-201b.earthlink-vadesecure.net ([51.81.229.181]:39109 helo=mta-201a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1s79PB-0001uU-1P for ecs-isp@2rosenthals.com; Wed, 15 May 2024 03:50:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=FtZAifEQ0BI99xmMDZKYc1Q545blAzuLE5jq3n KWrN0=; 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=1715759427; x=1716364227; b=ZCfyzWQP4fhAKRwMEfi6yHMNeduo4PlRaFh/hXuYNOGuVdmzumvqcBS zaqJwv3A7Qje3cVge4eMK9SKnxR+Y/enFzEsvt6OBbdx2PRnI95EPgGuLSy9U+2/zpDnmHd M2SWr2c4KpRrrHk1cOzMHCk7Sh84wofhjbRm4+fHH49fMkzorAYa1fJw6OU9WKZMr19503w 20E7gFm4+NpwhxoTHpz8vQXo1xIpGjiibS5dYDNbNMXQe2TGy68Xzb9WfMmrbm+pjZQjmDf xbTRIBKrW/Ff8RcAPv86HDm8fUrZkPoqZmz0SX/kfw1vju1NuMKnJQ9EsTq16ph+bav/oDh j2g== Received: from slamain ([172.56.185.0]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id 92d8366c-17cf9a1bde0fce05; Wed, 15 May 2024 07:50:27 +0000 Message-ID: <66446069.21.mr2ice.fgrirsq@earthlink.net> Date: Wed, 15 May 2024 00:12:41 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] Bind 9.11.37 issue - ticket #784 X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 05/11/24 at 11:02 AM, "Massimo S." said: Hi Massimo, I've reviewed the testlog and the yum output uploaded to the ticket. There's nothing obvious in the data that would explain the bind errors. FWIW, against my wishes, Massimo has chosen to edit the testlog and remove items that he believes are sensitive data and that, without sufficient technical knowledge, he believes have nothing to do with the issue. Hopefully, for his sake he has guessed right. If not, I will unassign myself from the ticket and let him resolve the bind hang on his own or with help from others. Massimo, I recommend you review the testlog and correct the reported PATH typo. The server is basically running eCS 2.2b with some updated drivers and some really old drivers. This means the server is running a kernel and PSD combo that have many SMP defects which have been fixed in newer kernel and PSD releases. Whether this is the reason for the named hangs is unknown at this time. The server is running a circa 2018 of the mmlem.os2 network driver. Whether or not this is contributing to the hangs is unknown at this time. Next time bind hangs, please capture a process dump and send me a link to the 7z archive. Try to remember to capture the process dump before attempting to kill named. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------