DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 17CA4385828E
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
        Nicholas Williams
 <nicholas.williams@zaxiom.com>
Subject: Re: Cygwin outputting message to stderr on dofork EAGAIN failure even
 when Python exception is caught and handled
Thread-Topic: Cygwin outputting message to stderr on dofork EAGAIN failure
 even when Python exception is caught and handled
Thread-Index: AQHawM/YSL3ZX/QYzEKz7ZlVkfXXWw==
Date: Mon, 17 Jun 2024 16:03:08 +0000
Message-ID: <PH0PR16MB4782ED8A31ADDFE5A3AC6ABAF5CD2@PH0PR16MB4782.namprd16.prod.outlook.com>
References: <DC419F64-5E24-493F-AFB7-9B31062A3FB6@zaxiom.com>
 <1399464798.20240617105808@yandex.ru>
In-Reply-To: <1399464798.20240617105808@yandex.ru>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-antispam-messagedata-chunkcount: 1
x-ms-exchange-antispam-messagedata-0: =?utf-8?B?TEhEWERHYWlMb3ZxLy9qTWxRaTE0VFFLUGc1MG1UQ0RzUmFtOEVuL0FwNGp0?=
 =?utf-8?B?cmtVeUNHb2JiWkk2WGYwZURBUkdTRlhOWEN3SmR3S0Q3alZGczJwS09XeGox?=
 =?utf-8?B?Sk9tcjBFOTBCTDJDNGIvdHdMQnpVRWxzR0JHbEZsWDgzNFpXRnpUajJ4WWpl?=
 =?utf-8?B?VVJqLytXOStxb1Uwd0IzOXU2U3l5VUMvQllvamFUcy9pbTlDSGRoZHRUNGZ3?=
 =?utf-8?B?OHdPUE5wY1dkM2ZlOUhjdFNUTEx1L1BoVnQxZW81eWtHOU05Mm5NODBlbDZv?=
 =?utf-8?B?dVAvNU1rUXlKWnAzU3Y2S3RoR296ZUtydHl1U0pkWm9nNjJsajRneFQvem9I?=
 =?utf-8?B?Vk1Xc2U1bUhYbExncFoveHJKMUlpZUVUdGpteFpDVmFITFFnQVJMcHFsc0s4?=
 =?utf-8?B?UEc0clY1WVMyVmhvcyt4YnRlM2lyTHFRYm5pVFNSaFVCS0hMcjlyV2ZqSVFB?=
 =?utf-8?B?SnE4RXg4YlkrbVI2aG95KzlveE5VV0tjektva1JOQXVURXJDbnVxY2JRN3Zp?=
 =?utf-8?B?WXkveU81NU15ZHQxVFRjeHoyTUh3cmNMSzFUcnNUVk9SRzFRNlRVSEVOV0t6?=
 =?utf-8?B?bGVjVW91K3AzamExTDlTRUliZWZPOEV3L2k5N0VEMHZQbEdQcExzcCtqTVRx?=
 =?utf-8?B?aFRRSldVMW1naUhDSktlNGtlNXh3dGhGWTdmS3AzelFuaE9ya3hhTDVwLzZw?=
 =?utf-8?B?ckJKR1ptbDdTWU5DZjQwTlZGazF3MzAvUUtCL0I4SXNmMG15OGJkMStzNlNR?=
 =?utf-8?B?bnJacGg1bWdMRmRadlJQMmpxV0ZoUjUvNnArcHdrVWN3R2tZQjRvTXdmWDhI?=
 =?utf-8?B?RGZnZHRMK3BWZ3ZnZWFUYlR6bWM4QTRoZ3FtUDNMUVFjWE9DNlYxV1BjR00v?=
 =?utf-8?B?N2VYQ2pFVjVBRmZTRXVtQmY1a0VHQlQwc2sxVm5ZYlpKY2JHRmhaVmhmZkEw?=
 =?utf-8?B?NmlUamxUdDZXZHZzdTcvK1NsWkNnYkZWL3pSMXJpVkJNQ3llZ0xNQ0l1a1NI?=
 =?utf-8?B?RmRkVndodWd1bHRjWjZYbWNYMzVOVnptTkFrMnVKbXRJNGwyLzlvOUZQRUh1?=
 =?utf-8?B?cDRwRnU3YkpLY0lJamszUHBzWFJaMGk0S1dkYi9VU0RzV2dIMXd5cnVadVBq?=
 =?utf-8?B?ZTdpNmpmQXhoejVBby9PZS83R2piSGtyc3VhWWYrUTZrMFd4M3luZWI2VWlq?=
 =?utf-8?B?OUNWbzNtZ0NGWnB6QitrcEpTQndRZGIrVFRJL0Y1bTNwU01LanVWN25LQnB3?=
 =?utf-8?B?RU9tZSsrQUZ2bDMxNE9YTGRLWVVnNzJYRzE4WHh4ekdWdHQvbUxobnVDOWlX?=
 =?utf-8?B?Tm9XTnV4Qm9JTWlLOXdrcmVkQ1NrM3dRNjBPbkdkOWVUVHBZUHhlUXk5T2VN?=
 =?utf-8?B?bGtUT3hudUN0ZVkwNXZHMWtwY3MrTHhkTWo4VmFDTER0UUx4eG1UeHpRakRE?=
 =?utf-8?B?aHl2dUsrTGhPZ1RGTmtaUFZxNzdYMUdVME5iaVYzRGZxeHF1RnZHOEZxMHl2?=
 =?utf-8?B?WWtNNVFBYnVxVXNURnJpcFVBNVRvUXBTQStPdVBnQnhtdzc3K0g4b2MrNlpU?=
 =?utf-8?B?MGRNL0tyZFZ5ZHpJOWt3YzNTVnFya1EyaGZBbFkxYm5kcmNHT3pjQklGTkRU?=
 =?utf-8?B?cEp5emlDOXk3ME5uVjI5QlcyNWhnZE5BYTlNNlpUL0tIZGUzUVpJOXBxdDBW?=
 =?utf-8?B?V29zcmZVU1Y1UTlJbzd5NjkwVHJYaVhjR0ZqY1dPVm5pbS84OFhwbDFCZHBv?=
 =?utf-8?B?WC9qK3d2WXNGcDRBaHRvVVRNZ01NMi9FaU10eHVidWdiNTRxZ3RBaHZja0Iy?=
 =?utf-8?B?RkgwalVvenJBU1gvVlQ5WjNTdndHY2ZZRWxNSyttVHYrc2ZPWWV6MHpSMXNn?=
 =?utf-8?B?U1lNeTcxWGtoaVJPMHI4disyd2VuZXNuYU1iZlV1Wlk3amdBYmYyYlNnVHZn?=
 =?utf-8?B?dVRiN0FzM2UyMWxDWkJ1Z0RUWXlzeXVMNWhacG9odHZxUy9BMU0wOXVYN01p?=
 =?utf-8?B?ZmVpWG5zWmNyZ21POVA5WWRCTmVuSHZjUWF2enoyYzhCdVA3OXZDUDIvWndN?=
 =?utf-8?B?QXhCaXRIb2JwbCs3bkU3NElsLzI2S1pPQXJKM0xCeVRheXZ3R25GeGc1ZEg5?=
 =?utf-8?Q?mVBY+yIZBrHy/EAedUcHWFVB+?=
MIME-Version: 1.0
X-OriginatorOrg: bryanhealth.org
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: PH0PR16MB4782.namprd16.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c9321412-07fe-4d33-ef51-08dc8ee6fb45
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jun 2024 16:03:08.8904 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 09b11d70-e37c-4120-b532-c13f0e4aa18f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 96hIh1DnitKRe/GfhEwKkIz30DTrodYgtiBfWRga+r7E0XCNI1XMFiGpxFSgaMYFF4KXlz0Yovv76qQRftigTA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LV3PR16MB5978
X-Proofpoint-ORIG-GUID: MOXIl3EDgJ2Aht3xPZ80J2tOIXkMxoJR
X-Proofpoint-GUID: MOXIl3EDgJ2Aht3xPZ80J2tOIXkMxoJR
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0
 priorityscore=1501
 adultscore=0 lowpriorityscore=0 impostorscore=0 bulkscore=0 spamscore=0
 mlxscore=0 suspectscore=0 phishscore=0 malwarescore=0 mlxlogscore=999
 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.19.0-2405170001 definitions=main-2406170124
X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, LIKELY_SPAM_FROM, SPF_HELO_NONE,
 SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.30
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: "Dale Lobb \(Sys Admin\) via Cygwin" <cygwin@cygwin.com>
Reply-To: "Dale Lobb \(Sys Admin\)" <Dale.Lobb@bryanhealth.org>
Content-Type: text/plain; charset="utf-8"
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 45HG4JMh2269876

Greetings, Nicholas;

> From: Cygwin <cygwin-bounces+dale.lobb=bryanhealth.org@cygwin.com> On Behalf Of Andrey Repin via Cygwin
> Sent: Monday, June 17, 2024 2:58 AM
> To: Nicholas Williams <nicholas.williams@zaxiom.com>; cygwin@cygwin.com
> Cc: Andrey Repin <anrdaemon@yandex.ru>
> Subject: EXTERNAL SENDER: Re: Cygwin outputting message to stderr on dofork EAGAIN failure even when Python exception is caught and handled
>
> Greetings, Nicholas Williams! > We have a Python (installed and run through Cygwin) process running on > Windows Server 2022 that was very, very occasionally failing when subprocess. check_output was called: > 0 [main] python3 28481
> 
> Greetings, Nicholas Williams!
>
> > We have a Python (installed and run through Cygwin) process running on
> > Windows Server 2022 that was very, very occasionally failing when subprocess.check_output was called:
>
> > 0 [main] python3 28481 dofork: child -1 - forked process 16856 died
> > unexpectedly, retry 0, exit code 0xC0000142, errno 11
> > …
> >     subprocess.check_output(["cygpath", "-w", directory.name], encoding="utf-8").strip()
> > File "/usr/lib/python3.9/subprocess.py", line 424, in check_output <>
> >      <>return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, <>
> > File "/usr/lib/python3.9/subprocess.py", line 505, in run <>
> >      <>with Popen(*popenargs, **kwargs) as process: <>
> > File "/usr/lib/python3.9/subprocess.py", line 951, in __init__ <>
> >      <>self._execute_child(args, executable, preexec_fn, close_fds, <>
> > File "/usr/lib/python3.9/subprocess.py", line 1754, in _execute_child
> >     self.pid = _posixsubprocess.fork_exec(
> > BlockingIOError: [Errno 11] Resource temporarily unavailable
>
> > Setting aside for a minute the various reasons this might be happening
> > occasionally, which we cannot solve for at this moment, the error number
> > (EAGAIN) indicates that you should “try again.” So that’s exactly what we
> > did. We added a try/catch to the Python code to catch the BlockingIOError
> > and, if and only if the error number is EAGAIN, we try up to two more times.
> > This fixed the problem and caused the application to stop quitting. We
> > output a warning to our log so that we don’t forget about the problem, but
> > the warning only ever appears once, so retrying a single time seems to help.
>
> > However … even though Python handles the dofork error, turns it into a
> > Python exception, and our code catches the Python exception and handles it
> > properly, Cygwin (not Python … Cygwin) still outputs a message to stderr
> > right before our warning message. This Cygwin error message shows up as an error in our log tracking:
>
> > 0 [main] python3 15042 dofork: child -1 - forked process 6780 died
> > unexpectedly, retry 0, exit code 0xC0000142, errno 11
> > 06/16 13:57:53. 87520: WARNING: Retrying command in 2 seconds due to EAGAIN: [the command we’re running]
>
> > I’m sure there could be any number of things I might be missing, but IMO,
> > if the process calling dofork properly handles the error raised by dofork,
> > Cygwin should not be outputting an error message to stderr.
>
> > Thoughts?
>
> My inexperienced and uneducated thought would be that forking code is fragile
> and some parts of it prone to misbehavior. When an unforeseen error is
> detected, it's better to report it sooner, than to get bitten by it later.
>
> Regarding your specific issue, if you create a STC[1] (a minimally enough
> version of your code that, say, fork a process thousands of times, which
> reliable reproduce the issue) somebody else could run to test the cause, that
> would be wonderful.
>
> (If, however, you could find and fix the cause, that would be even more wonderful!)
>

  I have seen this exact issue on every Windows  2019 or 2022
server where I have installed new versions of Cygwin since fall of 2023.
Admittedly, that has only been 3 or 4 machines, but it sure seems like
a pattern.  I have resisted upgrading old Cygwin installations for fear
that they also would start to exhibit this fork problem.

https://cygwin.com/pipermail/cygwin/2023-September/254417.html

  The only thing I have found that decreases the frequency of the
errors is to increase the amount of RAM assigned to the machine.
It does not eliminate the issue.  I've tried a ton of different
options with re-basing the Cygwin executables, to no avail.


Best Regards,

Dale


________________________________

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple