-
Notifications
You must be signed in to change notification settings - Fork 12
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
minknow_api onremote machines implemented? #17
Comments
Hello @neuropathbasel, When communicating with remote hosts, you must use tls (the examples dont support that in order to be concise). You will also need to use port 9502 for the manager. For example:
|
Thanks for the information. I just wonder if every MinKNOW instance has its own certificate or if the certificate is the same on every remote machine? Thanks |
The certificate is the same for the moment, this is something we are considering changing in the future. Thanks,
|
hello jorj1988, But instead of a device listing I did obtain: Any suggestion? |
Hi @neuropathbasel, Did you modify the example to use tls - as in the snippet above?
|
Hi George, During handling of the above exception, another exception occurred: Traceback (most recent call last): will go through this repo to find a HowTo Claus |
@george Currently I would prefer for a fist trial to use a insecure channel on port 9501 - at least for a first attempt. |
Thanks George! Please also consider a way to pull the certificate from the MinKNOW instance via some API calls when using different certificates for different instances of MinKNOW. Otherwise it would be pain in the ass to manually transfer and store each certificate from the remote machines to a local one. Cheers |
@neuropathbasel you can change how minknow binds insecure ports in the the |
Thanks for the rapid help. prompts: During handling of the above exception, another exception occurred: Traceback (most recent call last): I did find the https://github.com/nanoporetech/minknow_api/blob/2fad019ee71546c00f534bdd0ca37d885baf073a/README.md Any suggestion? |
Hi @neuropathbasel , The code above implies you are using tls still:
If you are using port 9501 you will need to not use tls. If you use tls you need to ensure you supply the certificate from the minknow sequencing device on the local machine. Thanks,
|
thanks for your rapid help. I did correct the code, but did not try to start the code from another terminal. On this headless system, I am accessing via VNC I feel that something (an editor?) is blocking some functions. I have not seen this before. Is there an example for supplying the certificate with the simple list_sequencing devices? In my hand the link to the API description files (https://github.com/nanoporetech/minknow_api/blob/2fad019ee71546c00f534bdd0ca37d885baf073a/protos/minknow_api) is not found. |
Please see this other issue where we discussed how to link CA certificates for minknow: |
Hello,
Many thanks for forwarding me here.
First step on the local linux machine worked fine and prompted:
~/minknow_api$ python ./python/examples/list_sequencing_positions.py --host localhost --port 9501
Available sequencing positions on localhost:9501:
MN32638: running
secure: 8001
insecure: 8000
However, issues started with the attempt to obtain a similar readout form an identical second machine in the same subnet running under 192.18.01.18.
On this machine MinKNOW GUI
Installed version: 4.1.22 is running and a Minion is attached to it via USB 3. This unit is “detected” by the local MinKNOW GUI.
Running on the first linux machine
~/minknow_api$ python ./python/examples/list_sequencing_positions.py --host 192.168.1.18 --port 9501
yields:
Traceback (most recent call last):
File "./python/examples/list_sequencing_positions.py", line 41, in
main()
File "./python/examples/list_sequencing_positions.py", line 23, in main
manager = Manager(host=args.host, port=args.port, use_tls=False)
File "/home/user/minknow_api/gRPC/lib/python3.7/site-packages/minknow_api/manager.py", line 108, in init
minknow_api.manager_service.GetVersionInfoRequest()
File "/home/user/minknow_api/gRPC/lib/python3.7/site-packages/grpc/_channel.py", line 946, in call
return _end_unary_response_blocking(state, call, False, None)
File "/home/user/minknow_api/gRPC/lib/python3.7/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAVAILABLE
details = "failed to connect to all addresses"
debug_error_string = "{"created":"@1618939002.979941782","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":5419,"referenced_errors":[{"created":"@1618939002.979938522","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":397,"grpc_status":14}]}"
ping to 192.168.1.18 yields an immediate reply.
Different attempts and the content of manager.py and manager_service.py imply to me that remote hosts are (so far ?) not supported.
Could you please let me know if gRPC calls to remote machine via the minknow_api are supported?
Many thanks
Claus
The text was updated successfully, but these errors were encountered: