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 1swD0f-002QqH-MN for buildfarm-members@arkaria.postgresql.org; Thu, 03 Oct 2024 04:00:14 +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 1swD0d-008IhL-0h for buildfarm-members@arkaria.postgresql.org; Thu, 03 Oct 2024 04:00:11 +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 1swD0c-008IhD-Jp for buildfarm-members@lists.postgresql.org; Thu, 03 Oct 2024 04:00:10 +0000 Received: from mail-lj1-x234.google.com ([2a00:1450:4864:20::234]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1swD0Z-002EZu-St for buildfarm-members@postgresql.org; Thu, 03 Oct 2024 04:00:09 +0000 Received: by mail-lj1-x234.google.com with SMTP id 38308e7fff4ca-2fac60ab585so5480971fa.0 for ; Wed, 02 Oct 2024 21:00:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727928006; x=1728532806; darn=postgresql.org; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=ZebEJROLfGIfGEcyl6SqfKK5x+to/18UX/aFhcxG4oo=; b=llbv+WPQ1uQ1WERmuTZ3khyzlbFGjtv3ABMAaKklLBdeKxRhpxPnShQDn4hHWLkOqS mtKWumMn+xrIrrlwuOkPebUSNvQDfeVP0Ex5BJ/j0ayerTTN1PtDO+qemFOy4W70+Xbu dvB1S86Hq5AMao39XKlC9FTIQc6vZ2jSoDTyJDD8f5tzrn12OaJafxoGADSios3dx5Bj 3O78VGwTxEs3Km2b6EuShH7CPzESIecZgPEfXYtsieMhqXK4/j3UBkCWct5hTgq5yuyF PHtlMeut8nptROVubl4OLkSY325zWDgxRDEf1mbXCHL16e33T6ZZ8M+b3b/coQjyiqwZ tg3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727928006; x=1728532806; h=content-transfer-encoding:subject:from:to:content-language :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=ZebEJROLfGIfGEcyl6SqfKK5x+to/18UX/aFhcxG4oo=; b=jBU1+UxrjWqV4bqElzrzgS0SU2PT56oeobEgudVrI3io9FIG+3O00oboA8HH/ilBcz 2JtSWjHCApHmbc7xfcrEkU9vBKFYEYMGYY+aUw2ZHD5W5c8VEGTlMdi2HgqV/2s1LbDG RMZJGVXTh39TO0Qc6eJnP2MH1GuGhlofq+OTYyc+rXH/RZrjIc3ZwLnxXussuUwmzSxn KyjxftGtSQxgvdVe9xf8PRXSfhWy5IxynpHkaUY2VSN/elclf+azgvkODSPE7Rujvc4r iDKWcrVQo4SEIYHfguktPWSoLR26J0jKUNBgZJVn8KMGNA5vyFuaKlI8+wm3yHO7CWtf sHHw== X-Forwarded-Encrypted: i=1; AJvYcCVcPvH9ZlaYLYaqEa3UDDrLBxZaLAhECmbpO0JA6kVUoPlMNZgMnuTu1QznfQf+BmAHzX2cAhidLtnYrRVbK1wvxA==@postgresql.org X-Gm-Message-State: AOJu0Yz7pvqecj4zWQEUkq48PfcU0EFVAxCAgdzfQSjD7QBsbeMmH1oX mIRTgCnF04r6kyh3eJfSs1/zlAMJnYzxfr+/A9/B3+Vn1l2aap0ae2zESg== X-Google-Smtp-Source: AGHT+IHlboCX1uFpPyHOxfG5DTGiw02hwEiqj6prRW4iXsldQx2aAcYgHIu6yzjItsZzChgP9HMyNg== X-Received: by 2002:a2e:a586:0:b0:2f6:5f0a:9d00 with SMTP id 38308e7fff4ca-2fae1002373mr34921441fa.1.1727928005741; Wed, 02 Oct 2024 21:00:05 -0700 (PDT) Received: from [1.0.0.7] ([91.185.78.236]) by smtp.gmail.com with ESMTPSA id 38308e7fff4ca-2faecc067cfsm874611fa.34.2024.10.02.21.00.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Oct 2024 21:00:04 -0700 (PDT) Message-ID: Date: Thu, 3 Oct 2024 07: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 Content-Language: en-US To: Noah Misch , buildfarm-members@postgresql.org From: Alexander Lakhin Subject: shmat() fails with Not enough space on wrasse Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Noah, Could you please look at sporadic test failures occurring on wrasse? Yesterday wrasse failed pg_rewindCheck ([3]) and it's the third failure of the same kind since July. The failure log regress_log_001_basic contains: # Running: pg_rewind --debug --source-server port=17304 host=/home/nm/farm/tmp/sbGTlHPVwD dbname='postgres' user=rewind_user --target-pgdata=/export/home/nm/farm/studio64v12_6/REL_14_STABLE/pgsql.build/src/bin/pg_rewind/tmp_check/t_001_basic_primary_remote_data/pgdata --no-sync --write-recovery-conf pg_rewind: executing ".../inst/bin/postgres" for target server to complete crash recovery 2024-10-03 01:32:24.149 CEST [29411:1] FATAL:  shmat(id=1392509011, addr=0, flags=0x4000) failed: Not enough space pg_rewind: error: postgres single-user mode in target cluster failed pg_rewind: fatal: Command was: ".../inst/bin/postgres" --single -F -D "...src/bin/pg_rewind/tmp_check/t_001_basic_primary_remote_data/pgdata" template1 < "/dev/null" not ok 11 - pg_rewind remote I don't know SPARC Solaris, but I've found a recommendation to increase zone.max-locked-memory [4] in a similar situation. As wrasse tests REL_16_STABLE and I hope it will continue doing that for another 4 years, maybe you would find it sensible to fix this issue if it's not more complicated... [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-07-22%2023%3A48%3A35 [2] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-09-15%2000%3A40%3A56 [3] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2024-10-02%2023%3A12%3A02 [4] https://www.ibm.com/support/pages/db2-activate-database-fails-sql1084c-solaris Best regards, Alexander