Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQn2O-00BdwD-M6 for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jul 2024 12:00:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sQn2N-005FNr-DX for pgsql-hackers@arkaria.postgresql.org; Mon, 08 Jul 2024 12:00:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQn2N-005FNh-3c for pgsql-hackers@lists.postgresql.org; Mon, 08 Jul 2024 12:00:07 +0000 Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sQn2K-0011OT-BU for pgsql-hackers@postgresql.org; Mon, 08 Jul 2024 12:00:05 +0000 Received: by mail-lj1-x235.google.com with SMTP id 38308e7fff4ca-2ee7885aa5fso41456171fa.1 for ; Mon, 08 Jul 2024 05:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720440003; x=1721044803; darn=postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=iW2IAIYCr7ge/h+x5D20dEE+60ITp9v+sjb8AmU3t9o=; b=Bl0JAr7aYS3l9s+C1CrArlRktsdLp+cmv0lh7T+bwhbWaigoye1MML0hnC4imPUGQq uvOHu1CPSNYIfglWfOfVk+IDwwJIiYP9Eey7ANgEXKRyuIxOZ96Y2VoZfKPe4wrgSAIn jZY4Eo1NAPpYgb+MxMuox43+IlH7tO8B59Iu9ORDtSJ2WHiQPVg3HeEpVjAPLEjZ/ciJ EY7xX1yDw4AcpwM3ORB9EFbWD0f26MsdegoiHifhHd2o0I1PZsoUz6jB8lh2bm1HTNt5 iIgbpoZV41ZoP+OUfPBpGRxAFbt4bGqTmGPOuhcVnXtEIhujaIIdxBxNLX8TfHUTbmAE YnOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720440003; x=1721044803; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=iW2IAIYCr7ge/h+x5D20dEE+60ITp9v+sjb8AmU3t9o=; b=EGUKpa/gXte1zUIaDK/IUcgSgE0CUs1nkgPz2CzQT42UiV8Dk5vg76t/LrAFX+zXO2 SkT6NSpfyCaqRKDF0BriqYCfG1wfZ2V6Zx56uKjyUffOZSwN7syI2SfHEsBSVAJxozs5 Sd+z54mvRxOdveOn4CrsQOK5oRlZzN/3FflgF7RcG6MS4nrhAWtINMbCRg3Vej+Guxmt qhaP8TZwOGSZjbPzr7PJ7xjy/eubZV2/29NU2BccFlfuzRwuFFe2A7okVn+WrkO2KHLf L3IGXOg5MGChEtfvKqEmFZnDcKKBxDrK1D2Ae5F2gjwWW5o82DIvnIAOPHrDiye980rq cyrA== X-Forwarded-Encrypted: i=1; AJvYcCVaAL57dL//bg8sw/Lhd/vvdbgy6Dor5X+RmcttO+/uS69jWUuNs6iRyNLkXoM83vxsElwoPuLPp2mgxuHZgGkx+c4bofMCpwiI3+q1 X-Gm-Message-State: AOJu0YxxZs3kGOXbPSHhYbbNbzKSVflPHzRSUJDsB2z9q7Icx/8esrzV Me8M0r3uGbT6zWVhoBm/5sxCp0sx7ZQQ8c3mYWaUMdRoyF5wvHJv X-Google-Smtp-Source: AGHT+IE7bhxEHAj4JYKTH+F53HqNHERti9qq6yFWbbFuTMYQhvBnynr6MAZxiuBgo4gqr6xXGnBQOA== X-Received: by 2002:a2e:7218:0:b0:2ee:88d8:e807 with SMTP id 38308e7fff4ca-2ee8ed8860emr77384161fa.16.1720440002420; Mon, 08 Jul 2024 05:00:02 -0700 (PDT) Received: from [1.0.0.7] ([178.155.22.46]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-2ee806ce45asm15774441fa.115.2024.07.08.05.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Jul 2024 05:00:01 -0700 (PDT) Message-ID: <954baf13-e850-c9a8-8deb-747dd096233e@gmail.com> Date: Mon, 8 Jul 2024 15:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: ssl tests fail due to TCP port conflict Content-Language: en-US To: Tom Lane , Andrew Dunstan Cc: Jelte Fennema-Nio , pgsql-hackers References: <6756fb60-aa5f-442c-90fb-5f29cd1658f0@dunslane.net> <914151.1717623435@sss.pgh.pa.us> <1244734.1717770345@sss.pgh.pa.us> From: Alexander Lakhin In-Reply-To: <1244734.1717770345@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello, 07.06.2024 17:25, Tom Lane wrote: > Andrew Dunstan writes: >> I still think my patch to force TCP mode for the SSL test makes sense as >> well. > +1 to both things. If that doesn't get the failure rate down to an > acceptable level, we can look at the retry idea. I'd like to add that the kerberos/001_auth test also suffers from the port conflict, but slightly differently. Look for example at [1]: krb5kdc.log contains: Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](info): setting up network... Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Address already in use - Cannot bind server socket on 127.0.0.1.55853 Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Failed setting up a UDP socket (for 127.0.0.1.55853) Jul 02 09:29:41 andres-postgres-buildfarm-v5 krb5kdc[471964](Error): Address already in use - Error setting up network As far as I can see, the port for kdc is chosen by PostgreSQL::Test::Kerberos, via PostgreSQL::Test::Cluster::get_free_port(), which checks only for TCP port availability (with can_bind()), but not for UDP, so this increases the probability of the conflict for this test (a similar failure: [2]). Although we can also find a failure with TCP: [3] (It's not clear to me, what processes can use UDP ports while testing, but maybe those buildfarm animals are running on the same logical machine simultaneously?) [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=rorqual&dt=2024-07-02%2009%3A27%3A15 [2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=mylodon&dt=2024-05-15%2001%3A25%3A07 [3] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=grassquit&dt=2024-07-04%2008%3A28%3A19 Best regards, Alexander