Broken Config File Impacts Tezos-Client
Environment (Mainnet, test network, build from source, ...)
./mainnet.sh status
Node is running
Baker is running
Endorser is running
The script is up to date.
Summary
Broken "config" file in the .tezos-client folder creates issues with the Tezos-Client.
~/.tezos-client $ cat config
{ "base_dir": "/var/run/tezos/client", "endpoint": "http://node:8732",
"web_port": 8080, "confirmations": 0 }~/.tezos-client $
Please also let me know what is wrong with the config file, as I don't see any issues with it.
tezos-client list known addresses for example, returns no results or errors with the config file; even though a wallet is connected.
~/.tezos-client $ tezos-client list known addresses
Disclaimer:
The Tezos network is a new blockchain technology.
Users are solely responsible for any risks associated
with usage of the Tezos network. Users should do their
own research to determine if Tezos is the appropriate
platform for their needs and should apply judgement and
care in their network interactions.
This issue was not discovered until attempting to re-import the wallet via the secret_key, where incorrect JSON was raised.
Steps to reproduce
Ensure config file from above.
./mainnet.sh shell
tezos-client list known addresses
<no wallets found>
Removing the config file and re-trying to "list known addresses" command returns the expected wallet.
Expected behavior
Wallet is returned. Or error in config file is prompted to the user.
Actual behavior
Wallet is not returned. No error in config file is displayed to the user.
History mode
Full by default
Edited by Victor Dumitrescu