-
Notifications
You must be signed in to change notification settings - Fork 3
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
Runtime error caused by full pipe to child process when lots of L1 nodes are started at once #34
Comments
Hmm, not sure what's going on! |
I don't think there is anything particular about this node, it's just the first one I found when checking the logs. I believe this is the reason why tsars can start up L1 too quickly across the can, or even start it all at once, but have to go approx. a rack at a time. Anyways,
I'm not sure exactly about the config being used. I think it's "bonsai_production_noups_nbeta2_v4.hdf5", which I found in |
You can find the configs etc in /home/l1operator/ch-frb-l1-dispatch.sh
…On Tue, Sep 3, 2019 at 5:08 PM Davor Cubranic ***@***.***> wrote:
cc @chitrangpatel <https://github.com/chitrangpatel>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#34?email_source=notifications&email_token=AAIEH7IRQG2RYBA6TZ6H3KLQH3G4BA5CNFSM4ITJXWLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ZSURY#issuecomment-527641159>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIEH7JDHBCM5KBFQPGLE6TQH3G4BANCNFSM4ITJXWLA>
.
|
From the logs (as shared in
#frb-ops
):The text was updated successfully, but these errors were encountered: