-
Notifications
You must be signed in to change notification settings - Fork 31
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
ru_generators sometimes fails when started before run starts, runs fine on restart of ru_generator #56
Comments
This is a frustrating issue which we think is caused by the MinKNOW RPC. It appears that the RPC reports that it is ready but actually isn't - and this may be millisecond timing. My advice at present would be to wait until the run is actually started before starting ru_generator. I'll tag @alexomics for any further comment. |
Thanks! Good to know it's probably not a configuration error on our side or something. If you check MinKNOW during a normal start, it actually gives a "Finishing up" status somewhere during the initialization (I added a screenshot). Could be related to that? In the meantime, maybe I missed it but it could be helpful to add that this situation can occur to the instructions? |
Yeah - these things should be caught. We will add somethign to the readme - (@alexomics) - unfortunately this particular scenario hasn't happened on any of our testing machines - it's just been reported to us. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because there has been no response for 5 days after becoming stale. |
If I start the ru_generator before the run has started it goes into a wait mode, starts when the run starts, and often immediately fails. Restarting ru_generator fixes the issue.
Once the flow cell starts running it often crashes as follows:
Then starting ru_generators again with the run already on its way, works just fine. Any idea what the problem is here? Could this be a timeout issue?
The text was updated successfully, but these errors were encountered: