proc_retry question

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

proc_retry question

Maninmoon
I have set proc_retry = 10.

I still get the following error message but showing rety 10:


      0 [main] sh 35392 fork: child -1 - forked process 35736 died
unexpectedly, retry 10, exit code 0xC0000005, errno 11
/q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable

Does this mean it got an error and cygwin will now retry 10 times?

OR does it mean it retry-ed 10 and failed?

Moon

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2
On Dec  8 12:40, xmoon 2000 wrote:

> I have set proc_retry = 10.
>
> I still get the following error message but showing rety 10:
>
>
>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
> unexpectedly, retry 10, exit code 0xC0000005, errno 11
> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>
> Does this mean it got an error and cygwin will now retry 10 times?
>
> OR does it mean it retry-ed 10 and failed?
It tried 10 times and failed.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Maninmoon
Are you certain about that?

Judging from the results - it appears to have worked. I consistently
get the same final results, whereas before, when CYGWIN was unset
completely, I got random results.

On 8 December 2014 at 14:40, Corinna Vinschen <[hidden email]> wrote:

> On Dec  8 12:40, xmoon 2000 wrote:
>> I have set proc_retry = 10.
>>
>> I still get the following error message but showing rety 10:
>>
>>
>>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
>> unexpectedly, retry 10, exit code 0xC0000005, errno 11
>> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>>
>> Does this mean it got an error and cygwin will now retry 10 times?
>>
>> OR does it mean it retry-ed 10 and failed?
>
> It tried 10 times and failed.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2


Please don't top-post.  Thank you.


On Dec  8 14:48, xmoon 2000 wrote:

> On 8 December 2014 at 14:40, Corinna Vinschen <[hidden email]> wrote:
> > On Dec  8 12:40, xmoon 2000 wrote:
> >> I have set proc_retry = 10.
> >>
> >> I still get the following error message but showing rety 10:
> >>
> >>
> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
> >>
> >> Does this mean it got an error and cygwin will now retry 10 times?
> >>
> >> OR does it mean it retry-ed 10 and failed?
> >
> > It tried 10 times and failed.
>
> Are you certain about that?
No.  Sorry, it's the other way around.  If retry is 10, no retry
occured.  AFAICS that's because you get an C000005 status code, which is
STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
explicitely not retry.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Maninmoon
On 8 December 2014 at 15:50, Corinna Vinschen <[hidden email]> wrote:

>
>
> Please don't top-post.  Thank you.
>
>
> On Dec  8 14:48, xmoon 2000 wrote:
>> On 8 December 2014 at 14:40, Corinna Vinschen <[hidden email]> wrote:
>> > On Dec  8 12:40, xmoon 2000 wrote:
>> >> I have set proc_retry = 10.
>> >>
>> >> I still get the following error message but showing rety 10:
>> >>
>> >>
>> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
>> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
>> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>> >>
>> >> Does this mean it got an error and cygwin will now retry 10 times?
>> >>
>> >> OR does it mean it retry-ed 10 and failed?
>> >
>> > It tried 10 times and failed.
>>
>> Are you certain about that?
>
> No.  Sorry, it's the other way around.  If retry is 10, no retry
> occured.  AFAICS that's because you get an C000005 status code, which is
> STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
> explicitely not retry.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Do this suggest that I need to do the rebaseall - as documented in:
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2
On Dec  8 16:03, xmoon 2000 wrote:

> On 8 December 2014 at 15:50, Corinna Vinschen <> wrote:
> > On Dec  8 14:48, xmoon 2000 wrote:
> >> On 8 December 2014 at 14:40, Corinna Vinschen <> wrote:
> >> > On Dec  8 12:40, xmoon 2000 wrote:
> >> >> I have set proc_retry = 10.
> >> >>
> >> >> I still get the following error message but showing rety 10:
> >> >>
> >> >>
> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
> >> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
> >> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
> >> >>
> >> >> Does this mean it got an error and cygwin will now retry 10 times?
> >> >>
> >> >> OR does it mean it retry-ed 10 and failed?
> >> >
> >> > It tried 10 times and failed.
> >>
> >> Are you certain about that?
> >
> > No.  Sorry, it's the other way around.  If retry is 10, no retry
> > occured.  AFAICS that's because you get an C000005 status code, which is
> > STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
> > explicitely not retry.
>
> Do this suggest that I need to do the rebaseall - as documented in:
> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures
You can try, but this looks a bit different.  A SEGV at fork time could
be a bug in Cygwin or a result of having another Cygwin DLL in the path
for some reason.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Maninmoon
On 8 December 2014 at 16:27, Corinna Vinschen <[hidden email]> wrote:

> On Dec  8 16:03, xmoon 2000 wrote:
>> On 8 December 2014 at 15:50, Corinna Vinschen <> wrote:
>> > On Dec  8 14:48, xmoon 2000 wrote:
>> >> On 8 December 2014 at 14:40, Corinna Vinschen <> wrote:
>> >> > On Dec  8 12:40, xmoon 2000 wrote:
>> >> >> I have set proc_retry = 10.
>> >> >>
>> >> >> I still get the following error message but showing rety 10:
>> >> >>
>> >> >>
>> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
>> >> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
>> >> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>> >> >>
>> >> >> Does this mean it got an error and cygwin will now retry 10 times?
>> >> >>
>> >> >> OR does it mean it retry-ed 10 and failed?
>> >> >
>> >> > It tried 10 times and failed.
>> >>
>> >> Are you certain about that?
>> >
>> > No.  Sorry, it's the other way around.  If retry is 10, no retry
>> > occured.  AFAICS that's because you get an C000005 status code, which is
>> > STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
>> > explicitely not retry.
>>
>> Do this suggest that I need to do the rebaseall - as documented in:
>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures
>
> You can try, but this looks a bit different.  A SEGV at fork time could
> be a bug in Cygwin or a result of having another Cygwin DLL in the path
> for some reason.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Corinna,

I tried "rebasing" but with no luck.

The problem appears when I am running 60 scripts in parallel on a 32
core machine. Plus, each script runs subscripts with several pipes.
So, I think this is a "too many processes" type of issue.

Usually, windows handle my "over-coring" well and my machine just
works through what it needs to do. But when I try this from Cygwin, it
seems to cause issues.

Any thoughts or suggest for how I could get around this?

Moon

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2
On Dec 11 09:02, xmoon 2000 wrote:

> On 8 December 2014 at 16:27, Corinna Vinschen <[hidden email]> wrote:
> > On Dec  8 16:03, xmoon 2000 wrote:
> >> On 8 December 2014 at 15:50, Corinna Vinschen <> wrote:
> >> > On Dec  8 14:48, xmoon 2000 wrote:
> >> >> On 8 December 2014 at 14:40, Corinna Vinschen <> wrote:
> >> >> > On Dec  8 12:40, xmoon 2000 wrote:
> >> >> >> I have set proc_retry = 10.
> >> >> >>
> >> >> >> I still get the following error message but showing rety 10:
> >> >> >>
> >> >> >>
> >> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
> >> >> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
> >> >> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
> >> >> >>
> >> >> >> Does this mean it got an error and cygwin will now retry 10 times?
> >> >> >>
> >> >> >> OR does it mean it retry-ed 10 and failed?
> >> >> >
> >> >> > It tried 10 times and failed.
> >> >>
> >> >> Are you certain about that?
> >> >
> >> > No.  Sorry, it's the other way around.  If retry is 10, no retry
> >> > occured.  AFAICS that's because you get an C000005 status code, which is
> >> > STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
> >> > explicitely not retry.
> >>
> >> Do this suggest that I need to do the rebaseall - as documented in:
> >> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures
> >
> > You can try, but this looks a bit different.  A SEGV at fork time could
> > be a bug in Cygwin or a result of having another Cygwin DLL in the path
> > for some reason.
>
> I tried "rebasing" but with no luck.
>
> The problem appears when I am running 60 scripts in parallel on a 32
> core machine. Plus, each script runs subscripts with several pipes.
> So, I think this is a "too many processes" type of issue.
It's a SEGV.  It's probably not related to having too many processes.
Cygwin processes only care for their immediate child processes usually
and there's a restriction to 256 or so.

> Usually, windows handle my "over-coring" well and my machine just
> works through what it needs to do. But when I try this from Cygwin, it
> seems to cause issues.
>
> Any thoughts or suggest for how I could get around this?

Apart from BLODA influence, or apart from debugging what causes the
SEGV, no.  If you can provide a simple testcase, stripped to the bare
minimum of code to reproduce the issue, it may help.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Maninmoon
On 11 December 2014 at 10:33, Corinna Vinschen
<[hidden email]> wrote:

> On Dec 11 09:02, xmoon 2000 wrote:
>> On 8 December 2014 at 16:27, Corinna Vinschen <[hidden email]> wrote:
>> > On Dec  8 16:03, xmoon 2000 wrote:
>> >> On 8 December 2014 at 15:50, Corinna Vinschen <> wrote:
>> >> > On Dec  8 14:48, xmoon 2000 wrote:
>> >> >> On 8 December 2014 at 14:40, Corinna Vinschen <> wrote:
>> >> >> > On Dec  8 12:40, xmoon 2000 wrote:
>> >> >> >> I have set proc_retry = 10.
>> >> >> >>
>> >> >> >> I still get the following error message but showing rety 10:
>> >> >> >>
>> >> >> >>
>> >> >> >>       0 [main] sh 35392 fork: child -1 - forked process 35736 died
>> >> >> >> unexpectedly, retry 10, exit code 0xC0000005, errno 11
>> >> >> >> /q/onlyPastEnd.sh: fork: retry: Resource temporarily unavailable
>> >> >> >>
>> >> >> >> Does this mean it got an error and cygwin will now retry 10 times?
>> >> >> >>
>> >> >> >> OR does it mean it retry-ed 10 and failed?
>> >> >> >
>> >> >> > It tried 10 times and failed.
>> >> >>
>> >> >> Are you certain about that?
>> >> >
>> >> > No.  Sorry, it's the other way around.  If retry is 10, no retry
>> >> > occured.  AFAICS that's because you get an C000005 status code, which is
>> >> > STATUS_ACCESS_VIOLATION.  In case of this error code, Cygwin does
>> >> > explicitely not retry.
>> >>
>> >> Do this suggest that I need to do the rebaseall - as documented in:
>> >> http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-fork-failures
>> >
>> > You can try, but this looks a bit different.  A SEGV at fork time could
>> > be a bug in Cygwin or a result of having another Cygwin DLL in the path
>> > for some reason.
>>
>> I tried "rebasing" but with no luck.
>>
>> The problem appears when I am running 60 scripts in parallel on a 32
>> core machine. Plus, each script runs subscripts with several pipes.
>> So, I think this is a "too many processes" type of issue.
>
> It's a SEGV.  It's probably not related to having too many processes.
> Cygwin processes only care for their immediate child processes usually
> and there's a restriction to 256 or so.
>
>> Usually, windows handle my "over-coring" well and my machine just
>> works through what it needs to do. But when I try this from Cygwin, it
>> seems to cause issues.
>>
>> Any thoughts or suggest for how I could get around this?
>
> Apart from BLODA influence, or apart from debugging what causes the
> SEGV, no.  If you can provide a simple testcase, stripped to the bare
> minimum of code to reproduce the issue, it may help.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Corinna,

I can't do a SCSE because it relies on files and a whole data structure here.

Any chance you could RemoteView my system?

Moon

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2
On Dec 11 13:05, xmoon 2000 wrote:
> On 11 December 2014 at 10:33, Corinna Vinschen wrote:
> > Apart from BLODA influence, or apart from debugging what causes the
> > SEGV, no.  If you can provide a simple testcase, stripped to the bare
> > minimum of code to reproduce the issue, it may help.
>
> I can't do a SCSE because it relies on files and a whole data structure here.
>
> Any chance you could RemoteView my system?

This goes a bit beyond what I'd do voluntarily, sorry.


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Maninmoon
On 11 December 2014 at 16:42, Corinna Vinschen
<[hidden email]> wrote:

> On Dec 11 13:05, xmoon 2000 wrote:
>> On 11 December 2014 at 10:33, Corinna Vinschen wrote:
>> > Apart from BLODA influence, or apart from debugging what causes the
>> > SEGV, no.  If you can provide a simple testcase, stripped to the bare
>> > minimum of code to reproduce the issue, it may help.
>>
>> I can't do a SCSE because it relies on files and a whole data structure here.
>>
>> Any chance you could RemoteView my system?
>
> This goes a bit beyond what I'd do voluntarily, sorry.
>
>
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Maintainer                 cygwin AT cygwin DOT com
> Red Hat


Corinna,

I can understand that!

Is there paid-for support available from any group?

Moon

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

marco atzeri-4
On 12/12/2014 9:57 AM, xmoon 2000 wrote:

>>> Any chance you could RemoteView my system?
>>
>> This goes a bit beyond what I'd do voluntarily, sorry.
>>
>> Corinna
>>
>> --
>> Corinna Vinschen                  Please, send mails regarding Cygwin to
>> Cygwin Maintainer                 cygwin AT cygwin DOT com
>> Red Hat
>
>
> Corinna,
>
> I can understand that!
>
> Is there paid-for support available from any group?
>
> Moon
>

I presume Redhat has the competence.

Regards
Marco

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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Warren Young-2
In reply to this post by Maninmoon
On Dec 11, 2014, at 6:05 AM, xmoon 2000 <[hidden email]> wrote:

> I can't do a SCSE because it relies on files and a whole data structure here.

Specialised Cleanup Service Europe?
Symantec Certified Systems Engineer?
State Compulsory Standards of Education?
Society of Civil and Structural Engineers?
School of Computing Science and Engineering?


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

Reply | Threaded
Open this post in threaded view
|

RE: proc_retry question

Cooper, Karl (US SSA)
>From: Warren Young
>Sent: Friday, December 12, 2014 2:49 PM
>To: cygwin
>Subject: Re: proc_retry question
>
>On Dec 11, 2014, at 6:05 AM, xmoon wrote:
>
> > I can't do a SCSE because it relies on files and a whole data structure here.
>
>Specialised Cleanup Service Europe?
>Symantec Certified Systems Engineer?
>State Compulsory Standards of Education?
>Society of Civil and Structural Engineers?
>School of Computing Science and Engineering?

Judging from this earlier description by the original poster:

'The problem appears when I am running 60 scripts in parallel on a 32 core machine. Plus, each script runs subscripts with several pipes.
So, I think this is a "too many processes" type of issue.'

. . . I would guess SCSE is "Single Core Single Execution" or something similar.

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


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

Reply | Threaded
Open this post in threaded view
|

Re: proc_retry question

Corinna Vinschen-2
In reply to this post by Maninmoon
On Dec 12 08:57, xmoon 2000 wrote:

> On 11 December 2014 at 16:42, Corinna Vinschen
> <[hidden email]> wrote:
> > On Dec 11 13:05, xmoon 2000 wrote:
> >> On 11 December 2014 at 10:33, Corinna Vinschen wrote:
> >> > Apart from BLODA influence, or apart from debugging what causes the
> >> > SEGV, no.  If you can provide a simple testcase, stripped to the bare
> >> > minimum of code to reproduce the issue, it may help.
> >>
> >> I can't do a SCSE because it relies on files and a whole data structure here.
> >>
> >> Any chance you could RemoteView my system?
> >
> > This goes a bit beyond what I'd do voluntarily, sorry.
> >
> >
> > Corinna
> >
> > --
> > Corinna Vinschen                  Please, send mails regarding Cygwin to
> > Cygwin Maintainer                 cygwin AT cygwin DOT com
> > Red Hat
>
>
> Corinna,
>
> I can understand that!
>
> Is there paid-for support available from any group?
Yes, Red Hat provides developer and user support for Cygwin:

  http://www.redhat.com/services/custom/cygwin/


Corinna

--
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

attachment0 (836 bytes) Download Attachment