TransWikia.com

More verbose logging in tezos-client

Tezos Asked by Thorkil Værge on December 8, 2020

I have some problems connecting to a node through tezos-client. Specifically I cannot succesfully run tezos-client -l -A rpcalpha.tzbeta.net -P 443 -S config update to connect to a testnet node. It fails on a GET request to https://rpcalpha.tzbeta.net:443/chains/main/blocks/head/protocols (Neither of the two HTTP requests are sent as the TCP or SSL connection is never established).

>>>>0: https://rpcalpha.tzbeta.net:443/version
>>>>1: https://rpcalpha.tzbeta.net:443/chains/main/blocks/head/protocols
Warning:
  Failed to acquire the protocol version from the node
  Rpc request failed:
     - meth: GET
     - uri: https://rpcalpha.tzbeta.net:443/chains/main/blocks/head/protocols
     - error: Unable to connect to the node: "Unix.Unix_error(Unix.ETIMEDOUT, "connect", "")"

But when I run curl -v https://rpcalpha.tzbeta.net:443/chains/main/blocks/head/protocols I get a 200 OK response. curl -v https://rpcalpha.tzbeta.net:443/version also works.

It would be easier for me to debug the problem, which is probably network related, if I could get verbose logs of what tezos-client is doing, specifically the HTTP requests’ headers would be useful. Is that possible?

One Answer

You can add argument -l --log-requests: log all requests to the node to tezos-client to see the connection.

Although this won't show you the headers, you can see the tezos-client -A rpcalpha.tzbeta.net ... tries to connect to http://rpcalpha.tzbeta.net:8732. To connect to https://rpcalpha.tzbeta.net:443 instead, you will want to add the following arguments:

  • -S --tls: use TLS to connect to node.
  • -P --port <number>: RPC port of the node with 443

To see the list of all available arguments, check out tezos-client --help.

Answered by Tomáš Zemanovič on December 8, 2020

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP