-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have aproplem with SLAC #1651
Comments
every time i try the server give me this massege |
Dear @Zienabmosaad, Can you please include the URL to one of the jobs that is failing and provide more detail on when the system fails. Best, |
Dear @Zienabmosaad, Thanks for reporting this issue. Can you please try again? Regards, |
thx
…On Mon, Oct 2, 2023 at 4:45 PM Stephen Shank ***@***.***> wrote:
Dear @Zienabmosaad <https://github.com/Zienabmosaad>,
Thanks for reporting this issue. Can you please try again?
Regards,
Stephen
—
Reply to this email directly, view it on GitHub
<#1651 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BC4XFTFZCWRRFRXDIVQCVKTX5LAQFAVCNFSM6AAAAAA5LI7ZYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGA2DOMBTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*Dr-zienab mosaad *
*Researcher - Virology department-Genomic sequencing and Gene analysis unit*
*Reference Laboratory for veterinary quality control on poultry production
(RLQP)*
*Animal Health Research Institute, (AHRI) - DOKKI- GIZA*
*P.O. Box 264-Dokki, Giza-12618, Egypt *
*Tel: 002 01118616896*
*Fax: 002 33370957, **002 33380121*
|
This appears to happen during the weekend when there are scheduled tasks performing on our cluster's head node. Datamonkey cannot spawn
The issue is two-pronged. 1) We need to identify what is the source of the head node's irresponsiveness, and 2) catch the exception and intermittently retry until successful within the application. |
Fixed!
…On Mon, Oct 16, 2023 at 8:47 PM Steven Weaver ***@***.***> wrote:
This appears to happen during the weekend when there are scheduled tasks
performing on our cluster's head node. Datamonkey cannot spawn qstat due
to an EAGAIN system error.
Error: spawn qstat EAGAIN
at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
at onErrorNT (internal/child_process.js:467:16)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
errno: -11,
code: 'EAGAIN',
syscall: 'spawn qstat',
path: 'qstat',
The issue is two-pronged. 1) We need to identify what is the source of the
head node's irresponsiveness, and 2) catch the exception and intermittently
retry until successful within the application.
—
Reply to this email directly, view it on GitHub
<#1651 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/BC4XFTFD4U4MTJ44LTBR2KDX7VXLZAVCNFSM6AAAAAA5LI7ZYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRUHE3TMNBTHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
*Dr-zienab mosaad *
*Researcher - Virology department-Genomic sequencing and Gene analysis unit*
*Reference Laboratory for veterinary quality control on poultry production
(RLQP)*
*Animal Health Research Institute, (AHRI) - DOKKI- GIZA*
*P.O. Box 264-Dokki, Giza-12618, Egypt *
*Tel: 002 01118616896*
*Fax: 002 33370957, **002 33380121*
|
Patch to handle |
No description provided.
The text was updated successfully, but these errors were encountered: