public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dale Lobb <Dale.Lobb@bryanhealth.org>
To: Jose Isaias Cabrera <jicman@outlook.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: EXTERNAL SENDER: RE: Fork errors
Date: Fri, 8 Sep 2023 21:30:08 +0000	[thread overview]
Message-ID: <PH0PR16MB47823B6D5F25330F24FC2316F5EDA@PH0PR16MB4782.namprd16.prod.outlook.com> (raw)
In-Reply-To: <DB9P251MB0063852385996D0778710E15DEEFA@DB9P251MB0063.EURP251.PROD.OUTLOOK.COM>

> -----Original Message-----
> From: Jose Isaias Cabrera <jicman@outlook.com>
> Sent: Wednesday, September 6, 2023 4:01 PM
> To: Dale Lobb <Dale.Lobb@bryanhealth.org>; tryandbuy via Cygwin
> <cygwin@cygwin.com>
> Subject: EXTERNAL SENDER: RE: Fork errors
>
> On September 6, 2023 2:52 PM, Dale Lobb expressed:
> >
> > Since upgrading to the latest version of Cygwin a few weeks ago on a
> > server I manage, I've been experiencing an issue with fork errors.
> > The Cygwin installation had not been updated for almost a year
> > before that.
> >
> > The issue happens every time a script is invoked that purges files
> > from some temporary directories, but never in the same place in the
> > script.  The script uses multiple calls to find -exec to remove
> > files over 10 days old from the directories.  Here is a typical
> > error.  Sometime the issue will assert after just a  few tens of
> > files deleted, sometimes after hundreds or thousands of files have
> > been deleted:
> >
> > removed '/cygdrive/d/.../obfuscated.datedata.txt'
> > 1 [main] find 20066 dofork: child -1 - forked process 4068 died
> > unexpectedly, retry 0, exit code 0xC0000142, errno 11
> > find: cannot fork: Resource temporarily unavailable
> >
> > It also happens randomly at other times.  I've seen the bash shell
> > itself fail on the invocation of a mintty.  I've seen it happen on
> > all sorts of interactive commands entered from bash.
> >
> > Today, as a test, I updated all the installed Cygwin components.
> > One of the post installation scripts failed, so I re-exec'd it:
> >
> > $ ./postinstall/0p_update-info-dir.dash
> > Rebuilding info directory
> > 2 [main] dash 2059 dofork: child -1 - forked process 7676 died
> > unexpectedly, retry 0, exit code 0xC0000142, errno 11
> > ./postinstall/0p_update-info-dir.dash: 22: Cannot fork
> >
> > A second re-exec then worked fine.
> >
> > I've tried reinstalling all the components, and I've tried
> > rebaseall.
> >
> > Is there anything else I can try, or troubleshooting steps to
> > take?
> >
> > Best Regards,
>
> Take a look at this:
>
> https://stackoverflow.com/questions/36399041/cygwin-update-cause-error-could-not-fork-child-process-resource-temporarily-u
>
> it may not help, but it's something to look into.
>
> ________________________________________
>
> 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.


Hello Jose,

  Thank you for the reply.

  I read through the Stack Overflow post.  Unfortunately, Windows Server
2016 is based on an early version of Windows 10, which does not have the
"Windows Defender Security Center" app.  Only 2019 and later versions have
that feature.

  I did find this article and used the group policy editor to disable ASLR for
several Cygwin executables (ash, bash, find, rm), but that didn't make any
difference.

https://learn.microsoft.com/en-us/windows/security/threat-protection/override-mitigation-options-for-app-related-security-policies

Best Regards,

Dale Lobb



________________________________

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.

  parent reply	other threads:[~2023-09-08 21:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 18:51 Dale Lobb
2023-09-06 21:00 ` Jose Isaias Cabrera
2023-09-06 21:03   ` Jose Isaias Cabrera
2023-09-08 21:35     ` EXTERNAL SENDER: " Dale Lobb
2023-09-08 21:30   ` Dale Lobb [this message]
2023-09-06 23:32 ` Mark Geisert
2023-09-07 15:20   ` Bill Stewart
2023-09-08  5:02     ` Mark Geisert
2023-09-08 22:02   ` EXTERNAL SENDER: " Dale Lobb
2023-09-09  7:26     ` Mark Geisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=PH0PR16MB47823B6D5F25330F24FC2316F5EDA@PH0PR16MB4782.namprd16.prod.outlook.com \
    --to=dale.lobb@bryanhealth.org \
    --cc=cygwin@cygwin.com \
    --cc=jicman@outlook.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).