From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTP id 13711645 for ecs-isp@2rosenthals.com; Tue, 29 Jul 2025 02:47:10 -0400 Received: from secmgr-va.2rosenthals.com ([50.73.8.217]:33581 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1uge72-000000002Rd-19tT for ecs-isp@2rosenthals.com; Tue, 29 Jul 2025 02:47:00 -0400 Received: from mta-201a.earthlink-vadesecure.net ([51.81.229.180]:48919) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.97.1) (envelope-from ) id 1uge6z-000000001ks-0o12 for ecs-isp@2rosenthals.com; Tue, 29 Jul 2025 02:46:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; bh=d6UVU0mDLJguwdwP7H/J47owdr1B/7yoO8rbSD sPOuk=; 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-unsubscribe-post: list-subscribe:list-post:list-owner:list-archive; q=dns/txt; s=dk12062016; t=1753771616; x=1754376416; b=KI+cbrb4fhmG2dlxHsIpQld3dMS AMzqq9O+Unokfl5Bsv/9CxE4eUsKyTfBcm1vOUJ3mdbdEHexs1pe8SE1gQNPVKdEkZgP9wc 4jGZ+djzXFVZNVaocl6aadn1OF9Alvso8/NxjMXwfuqxPNhh8yTlb54KGW+BRG52FDfiuy4 1yyd+B06Lvv2qIOlhbcrPXkefWvY+s13bzbkpojabyxXrkX7ZKN6RQX94jUZm9P5pZIvc+e MdhD3EWUonjyRR3yYwA7fTccd73xQDv5UrcZZJroR5de2XDcuHV3xPhr86RlpG+rfN2XC/k PsUgQ2J+UiH3h+8WBCN7bBMQ2gC6YLA== Received: from slamain ([172.58.119.142]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id a897cb7a-1856a5fe205fc128; Tue, 29 Jul 2025 06:46:56 +0000 Message-ID: <68886dab.50.mr2ice.fgrirsq@earthlink.net> Date: Mon, 28 Jul 2025 23:43:55 -0700 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] socket - no buffer space availble X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 07/29/25 at 10:15 AM, "Peter Moylan" said: Hi all, >Just because Apache was the one to report the problem, that doesn't mean >that Apache caused the socket starvation. You have to use Lewis's >approach of closing one application at a time, to see which "close" >fixed the problem. Agreed. Another useful took for tracking down the source of this kind of issue is netstat -s There's often enough information in the port numbers to track down the offending application. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------