3
You should set all three to 0 in order to accept 0-fee transactions. This will not affect the validity of the blocks you create.
One possible negative repercussion is that your mempool could be spammed with very cheap transactions and the mempool isn't currently as sophisticated as it could be. However, if that happens you could revert to requiring more ...
2
Use ./tezos-node config update --connections=300 to fix your config file, as Tom said, those numbers should not match. Then restart tezos-node. Make sure your firewall is open, and any routers are port-forwarding to port 9732. You should also enable the RPC while you are at it config update --rpc-addr=127.0.0.1:8732 so that you can use other tools which ...
1
Calling tezos-admin-client p2p stat on node B will list among other things, all active connections. The connections to private node will have the word private near the end of the line.
Here is an example in sandbox where 127.0.0.1:19732 plays the node A (private and trusted):
$ tezos-admin-client p2p stat
GLOBAL STATS
↗ 4.21 kiB (224 B/s) ↘ 1.70 kiB (89 ...
1
Your last baked block was not your last assigned block.
Meaning your baker had the opportunity/right to bake a block at height 576529 but missed to inject a block.
Only top voted, non community-wiki answers of a minimum length are eligible