docker exec miner miner info height Error: Usage information not found for the given command

[Heltec-Aaron-Lee]

Hello,
I upgrade image to miner-arm64_2021.06.09.0_GA, I get the error when get the height:
docker exec miner miner info height
Error: Usage information not found for the given command

It seems the "info" is not supported ?
I downgrade image to miner-amd64_2021.06.08.0_GA, that works ok.
Is that a bug?

[vihu]

miner-arm64_2021.06.09.0_GA -> miner-amd64_2021.06.09.0_GA

Not sure if it was a typo for you here, but try switching to the amd image (assuming you're running on some x64 and not on arm)?

[Heltec-Aaron-Lee]

sorry, it is my mistake, it is running on arm, I downgrade to miner-arm64_2021.06.08.0_GA is OK
but miner-arm64_2021.06.09.0_GA, has the error:
docker exec miner miner info height
Error: Usage information not found for the given command

[shawaj]

Having the same error here on several Nebra units with the latest GA

[shawaj]

[ryanteck]

This also looks still present in the 06.12 update, but also affects getting it from dbus too as well as the CLI command.

[shawaj]

@vihu any idea when it might be possible to fix this one?

[ryanteck]

Just to confirm, this looks like it affects the DBUS protocols for Diagnostics & Add hotspot which is causing users not to be able to setup their units.

[madninja]

Just to confirm, this looks like it affects the DBUS protocols for Diagnostics & Add hotspot which is causing users not to be able to setup their units.

usage for command not found is affecting dbus interaction? That seems.. odd?

[ryanteck]

@madninja I'm not 100% sure if it's the same issue, but from what I can gather it's fairly close that if this error.

We have 10-20 units where the miner is not communicating over DBUS for diagnostics or adding the hotspot.

When running the same command this error comes up which makes me think it's something that affects both.

[madninja]

@madninja I'm not 100% sure if it's the same issue, but from what I can gather it's fairly close that if this error.

We have 10-20 units where the miner is not communicating over DBUS for diagnostics or adding the hotspot.

When running the same command this error comes up which makes me think it's something that affects both.

Any miner logs indicating that the miner process is erroring or has wedged?

[ryanteck]

@madninja Here's the console log, error log just has some P2P issues.

2021-06-14 12:51:04.934 161 [info] <0.14689.0>@libp2p_multistream_client:negotiate_handler:18 Simultaneous connection detected with {"/ip4/172.17.0.3/tcp/42837","/ip4/44.236.95.167/tcp/2154"}, elected to server role
2021-06-14 12:51:04.934 161 [info] <0.14689.0>@libp2p_transport:start_client_session:164 Started simultaneous connection with {"/ip4/172.17.0.3/tcp/42837","/ip4/44.236.95.167/tcp/2154"} as <0.14810.0>
2021-06-14 12:51:09.935 161 [warning] <0.1244.0>@libp2p_group_worker:connecting:237 Failed to connect to "/ip4/44.236.95.167/tcp/2154": {exit,{normal,{gen_server,call,[<0.14810.0>,open]}}}
2021-06-14 12:51:19.817 161 [info] <0.14819.0>@libp2p_transport_proxy:connect:38 init proxy with ["/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU","/p2p/11288gJqrG1ysVZe3ZBRvBkX9ZToagjcwG19Ze7PuGWn3Jp9C6Nu"]
2021-06-14 12:51:21.827 161 [info] <0.14833.0>@libp2p_stream_proxy:init:63 init proxy client with {{connection,libp2p_yamux_stream,<0.14825.0>},[{swarm,<0.1229.0>},{p2p_circuit,"/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU/p2p-circuit/p2p/11288gJqrG1ysVZe3ZBRvBkX9ZToagjcwG19Ze7PuGWn3Jp9C6Nu"},{transport,<0.14819.0>},{id,<<126,160,239,233,181,115,116,7,190,22,47,45,230,91,168,76>>}]}
2021-06-14 12:51:23.223 161 [info] <0.14833.0>@libp2p_stream_proxy:handle_client_data:174 client got dial back request {libp2p_proxy_dial_back_pb}
2021-06-14 12:51:23.224 161 [info] <0.14833.0>@libp2p_stream_proxy:dial_back:226 Got port "44158" from peerbook for "/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU"
2021-06-14 12:51:24.605 161 [info] <0.14833.0>@libp2p_stream_proxy:handle_client_data:188 client got proxy resp {libp2p_proxy_resp_pb,true,<<"/ip4/73.158.37.175/tcp/51915">>}
2021-06-14 12:51:24.606 161 [info] <0.14819.0>@libp2p_transport_proxy:connect_rcv:110 proxy successful {connection,libp2p_transport_tcp,{tcp_state,{"/ip4/172.17.0.3/tcp/38227","/ip4/73.158.37.175/tcp/51915"},#Port<0.4035>,undefined,ranch_tcp}}
2021-06-14 12:51:41.449 161 [notice] <0.14870.0>@libp2p_stream_identify:handle_info:64 Identify timed out
2021-06-14 12:51:41.451 161 [warning] <0.1235.0>@libp2p_swarm_server:handle_info:66 ignoring session after failed identify "/ip4/35.155.234.98/tcp/443": timeout
2021-06-14 12:51:41.452 161 [notice] <0.1236.0>@libp2p_transport_tcp:handle_info:445 session identification failed for "/ip4/35.155.234.98/tcp/443": timeout
2021-06-14 12:51:50.249 161 [info] <0.14796.0>@libp2p_multistream_client:negotiate_handler:18 Simultaneous connection detected with {"/ip4/172.17.0.3/tcp/36459","/ip4/3.248.105.103/tcp/2154"}, elected to server role
2021-06-14 12:51:50.249 161 [info] <0.14796.0>@libp2p_transport:start_client_session:164 Started simultaneous connection with {"/ip4/172.17.0.3/tcp/36459","/ip4/3.248.105.103/tcp/2154"} as <0.14883.0>
2021-06-14 12:51:55.251 161 [warning] <0.1245.0>@libp2p_group_worker:connecting:237 Failed to connect to "/ip4/3.248.105.103/tcp/2154": {exit,{timeout,{gen_server,call,[<0.14883.0>,open]}}}
2021-06-14 12:52:03.317 161 [info] <0.14905.0>@libp2p_transport_proxy:connect:38 init proxy with ["/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU","/p2p/11288gJqrG1ysVZe3ZBRvBkX9ZToagjcwG19Ze7PuGWn3Jp9C6Nu"]
2021-06-14 12:52:04.210 161 [info] <0.14907.0>@libp2p_stream_proxy:init:63 init proxy client with {{connection,libp2p_yamux_stream,<0.14906.0>},[{swarm,<0.1229.0>},{p2p_circuit,"/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU/p2p-circuit/p2p/11288gJqrG1ysVZe3ZBRvBkX9ZToagjcwG19Ze7PuGWn3Jp9C6Nu"},{transport,<0.14905.0>},{id,<<83,19,227,113,63,243,106,117,11,85,9,45,157,90,63,68>>}]}
2021-06-14 12:52:05.599 161 [info] <0.14907.0>@libp2p_stream_proxy:handle_client_data:174 client got dial back request {libp2p_proxy_dial_back_pb}
2021-06-14 12:52:05.601 161 [info] <0.14907.0>@libp2p_stream_proxy:dial_back:226 Got port "44158" from peerbook for "/p2p/11ovuQif5B5drQ1EKG2YBAMV9sGg8N5dDv86gvmJNTnXJZqkLpU"
2021-06-14 12:52:06.983 161 [info] <0.14907.0>@libp2p_stream_proxy:handle_client_data:188 client got proxy resp {libp2p_proxy_resp_pb,true,<<"/ip4/73.158.37.175/tcp/53571">>}
2021-06-14 12:52:06.984 161 [info] <0.14905.0>@libp2p_transport_proxy:connect_rcv:110 proxy successful {connection,libp2p_transport_tcp,{tcp_state,{"/ip4/172.17.0.3/tcp/51089","/ip4/73.158.37.175/tcp/53571"},#Port<0.4048>,undefined,ranch_tcp}}

[madninja]

A release is being prepped. My guess is that you were suffering the deadlocked snapshot load issue.

[mihail99555]

On my IP diagnostic page on Sync % and on Height Status is showing Miner is still loading, is this the same error? I have submitted a ticket #246757

[shawaj]

@mihail99555 yes we think it is. Once we push an update we will notify everyone in Discord with a pin. If you are still having issues after that then you can contact us via discord or email and we will help further

[whittinghamj]

How are you guys accessing the terminal log output and how can I do the same please?

Thanks

[vihu]

@vihu any idea when it might be possible to fix this one?

Hoping that the next release will address this, specifically blockchain-core#864.

[evanmcc]

any update on this? can I close it?

[shawaj]

We haven't seen this issue occurring again since the new release so from my perspective it can be closed

[abhay]

Thanks @shawaj