This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Cygwin error: 1 [main] bash 5856 e:\cygwin64\bin\bash.exe: *** fatal error - add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1


RE: Cygwin error:  1 [main] bash 5856 e:\cygwin64\bin\bash.exe: ***
fatal error - add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1


I am looking for help on the following issue where I get an error
message from the cygwin1.dll or from the bash.exe program.  I am
hoping that the cygwin1.dll or the bash.exe have been, or can be,
fixed to alleviate this issue:

Invocations of various Shell Scripts, which are all trying to run the
Cygwin "bash.exe" program, at the same time frame produce the
following error for each of the invocations:

-----------------------
Cygwin error:
  1 [main] bash 5856 e:\cygwin64\bin\bash.exe: *** fatal error -
add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1
-----------------------

Tivoli Workload Scheduler return code or exit status:
= Exit Status           : 256
-----------------------



Do you know if anyone has been able to understand, and perhaps fix,
the error I have mentioned above.  It appears to be related to
invoking more than 2 Cygwin "bash.exe" program instances at nearly the
same second (time).  We have continuous issues with this and it can
cut 1 to 20 Tickets a week for us with the multitude of file transfers
we are doing on a daily basis.

I don't want to do any type of work-around to account for this
situation -- like calling my own "bash.exe" that throttles the
invocations of Cygwin's "bash.exe" program so that only one will be
run at a time – in other words, create a method to give each
invocation of Cygwin's "bash.exe" program separate from the other
invocations and therefore stagger them so that they do not try to run
at the exact same time (second).

See below to see an example of the Jobs that all failed near the same
time due to the supposed "bash.exe" concurrency issue.

http://stackoverflow.com/questions/28861237/bash-is-crashing-on-cygwin-add-item-c-cygwin
https://www.cygwin.com/ml/cygwin/2015-03/msg00139.html
https://www.bountysource.com/issues/27508535-several-different-operations-take-too-long-sometimes-end-up-crashing
http://superuser.com/questions/194529/cygwin-fatal-error-unable-to-remap-what-does-it-mean

--Michael




---------------------------------
APPENDIX A:

Invocations of various Shell Scripts which are all trying to run the
Cygwin "bash.exe" program at the same second (time) produce the
following error for each of the invocations:

$ egrep "= Exit Status" * | egrep -v "Exit Status           : 0" | cut
-f1 -d':' | xargs cat
====
= JOB       : X
= USER      : X
= JCLFILE   : e:\cygwin64\bin\bash.exe -l -c
"/cygdrive/e/interface/ecrm/bin/send_to_ecrm.sh -n"
= Job Number: 797669
= Fri 03/04/16 19:31:24 Mountain Standard Time
====
Tivoli Workload Scheduler (Windows)/JOBLNCH 9.2.0.01 (20141211)
X
Locale LANG set to the following: "en"
TWS for Windows NT/JOBMANRC.CMD 9.2
      1 [main] bash 5856 e:\cygwin64\bin\bash.exe: *** fatal error -
add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1
Stack trace:
Frame        Function    Args
0000022AACE  00180071FDE (00180260B02, 00180211E99, 00600010000, 00000228A30)
0000022AACE  00180046E82 (00000229A98, 0000022AACE, 1D176871D152D74,
00000000000)
0000022AACE  00180046EC2 (00000229AB0, 00000000001, 00600010000,
635C3A655C3F3F5C)
0000022AACE  001800DC0D4 (00000000000, 0000022CE00, 001800CE498,
1D1768726085D8D)
0000022CB00  00180125245 (00000000000, 00000000000, 00000000000, 00000000000)
0000022CBC0  00180047495 (00000000000, 0000009F000, 7FEFD71D000, 0000022D240)
00000000000  001800460DC (00000000000, 00000000000, 00000000000, 7FEFD680000)
00000000000  00180046174 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100472DD1 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076E759ED (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076FAB831 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace
====
= Exit Status           : 256
= System Time (Seconds) : 0     Elapsed Time (Minutes) : 0
= User Time (Seconds)   : 0
= Fri 03/04/16 19:31:40 Mountain Standard Time
====

====
= JOB       : X
= USER      : X
= JCLFILE   : e:\cygwin64\bin\bash.exe -l -c
"/cygdrive/e/interface/iriworldwide/bin/send_to_iriworldwide.sh -n"
= Job Number: 797670
= Fri 03/04/16 19:31:24 Mountain Standard Time
====
Tivoli Workload Scheduler (Windows)/JOBLNCH 9.2.0.01 (20141211)
X
Locale LANG set to the following: "en"
TWS for Windows NT/JOBMANRC.CMD 9.2
      1 [main] bash 4676 e:\cygwin64\bin\bash.exe: *** fatal error -
add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1
Stack trace:
Frame        Function    Args
0000022AACE  00180071FDE (00180260B02, 00180211E99, 00600010000, 00000228A30)
0000022AACE  00180046E82 (00000229A98, 0000022AACE, 1D176871D1EB6D8,
00000000000)
0000022AACE  00180046EC2 (00000229AB0, 00000000001, 00600010000,
635C3A655C3F3F5C)
0000022AACE  001800DC0D4 (00000000000, 0000022CE00, 001800CE498,
1D176872611E6F1)
0000022CB00  00180125245 (00000000000, 00000000000, 00000000000, 00000000000)
0000022CBC0  00180047495 (00000000000, 0000009F000, 7FEFD71D000, 0000022D240)
00000000000  001800460DC (00000000000, 00000000000, 00000000000, 7FEFD680000)
00000000000  00180046174 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100472DD1 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076E759ED (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076FAB831 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace
====
= Exit Status           : 256
= System Time (Seconds) : 0     Elapsed Time (Minutes) : 0
= User Time (Seconds)   : 0
= Fri 03/04/16 19:31:40 Mountain Standard Time
====

====
= JOB       : X
= USER      : X
= JCLFILE   : e:\cygwin64\bin\bash.exe -l -c
"/cygdrive/e/interface/kroger_go/bin/send_to_go.sh -n"
= Job Number: 797671
= Fri 03/04/16 19:31:25 Mountain Standard Time
====
Tivoli Workload Scheduler (Windows)/JOBLNCH 9.2.0.01 (20141211)
X
Locale LANG set to the following: "en"
TWS for Windows NT/JOBMANRC.CMD 9.2
      1 [main] bash 2380 e:\cygwin64\bin\bash.exe: *** fatal error -
add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1
Stack trace:
Frame        Function    Args
0000022AACE  00180071FDE (00180260B02, 00180211E99, 00600010000, 00000228A30)
0000022AACE  00180046E82 (00000229A98, 0000022AACE, 1D176871D28403C,
00000000000)
0000022AACE  00180046EC2 (00000229AB0, 00000000001, 00600010000,
635C3A655C3F3F5C)
0000022AACE  001800DC0D4 (00000000000, 0000022CE00, 001800CE498,
1D17687261B7055)
0000022CB00  00180125245 (00000000000, 00000000000, 00000000000, 00000000000)
0000022CBC0  00180047495 (00000000000, 0000009F000, 7FEFD71D000, 0000022D240)
00000000000  001800460DC (00000000000, 00000000000, 00000000000, 7FEFD680000)
00000000000  00180046174 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100472DD1 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076E759ED (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076FAB831 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace
====
= Exit Status           : 256
= System Time (Seconds) : 0     Elapsed Time (Minutes) : 0
= User Time (Seconds)   : 0
= Fri 03/04/16 19:31:40 Mountain Standard Time
====

====
= JOB       : X
= USER      : X
= JCLFILE   : e:\cygwin64\bin\bash.exe -l -c
"/cygdrive/e/interface/kroger_louisville_studio/bin/send_to_louisville_studio.sh
-n"
= Job Number: 797672
= Fri 03/04/16 19:31:25 Mountain Standard Time
====
Tivoli Workload Scheduler (Windows)/JOBLNCH 9.2.0.01 (20141211)
X
Locale LANG set to the following: "en"
TWS for Windows NT/JOBMANRC.CMD 9.2
      1 [main] bash 2016 e:\cygwin64\bin\bash.exe: *** fatal error -
add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1
Stack trace:
Frame        Function    Args
0000022AACE  00180071FDE (00180260B02, 00180211E99, 00600010000, 00000228A30)
0000022AACE  00180046E82 (00000229A98, 0000022AACE, 1D176871D2AA295,
00000000000)
0000022AACE  00180046EC2 (00000229AB0, 00000000001, 00600010000,
635C3A655C3F3F5C)
0000022AACE  001800DC0D4 (00000000000, 0000022CE00, 001800CE498,
1D17687261DD2AE)
0000022CB00  00180125245 (00000000000, 00000000000, 00000000000, 00000000000)
0000022CBC0  00180047495 (00000000000, 0000009F000, 7FEFD71D000, 0000022D240)
00000000000  001800460DC (00000000000, 00000000000, 00000000000, 7FEFD680000)
00000000000  00180046174 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100472DD1 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076E759ED (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00076FAB831 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace
====
= Exit Status           : 256
= System Time (Seconds) : 0     Elapsed Time (Minutes) : 0
= User Time (Seconds)   : 0
= Fri 03/04/16 19:31:40 Mountain Standard Time
====




---------------------------------
APPENDIX B:

Invocations of various Shell Scripts which are all trying to run the
Cygwin "bash.exe" program at the same second (time) produce the
following error for each of the invocations:


Eric Blake (Red Hat) wrote:
>
> Cygwin error:
>   1 [main] bash 5856 e:\cygwin64\bin\bash.exe: *** fatal error - add_item ("\??\e:\cygwin64", "/", ...) failed, errno 1

I'm not familiar with that particular error message, but it is MUCH
more likely to be a generic problem in cygwin1.dll, and not in the
code specifically in bash.exe.  What's more, if you are able to hit it
in bash.exe, it may be that someone else is hitting the same issue,
but perhaps with other binaries linked against cygwin1.dll, so
reporting it upstream and getting it fixed in cygwin1.dll will help
EVERYONE suffering from the problem.
...
...
It might also be that your systems are suffering from some sort of
https://cygwin.com/acronyms/#BLODA, where third-party code is
interfering with the attempts to start two simultaneous cygwin
applications.
>
> https://www.cygwin.com/ml/cygwin/2015-03/msg00139.html

That email is probably the most telling; Corinna is more familiar with
how to go about debugging the problem you are seeing than I am (...).
I don't know if she had enough details to solve it in the meantime
(where updating to newer cygwin will solve your issue), or if the fact
that you are still hitting it means that she will ask you to help
debug a potential fix in a new cygwin1.dll, but that's what posting to
the list will find out.

---------------------------------



Sincerely,
Michael J. Goydich
Kroger Co., Kroger Technology
Michael.Goydich@kroger.com
Office 513-387-7062

--
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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]