go-filecoin chain stalled log debug

setup-go-filecoin-logs-for-chain-debug.sh

# Use this set of commands for tuning your logs to debug scenarios where your node can't sync the chain
# At a high level if your chain is getting stuck it is because one of 2 things is going wrong
# 1. Your node can't fetch the chain data
# 2. Your node can't correctly process the longest chain

# first quiet all logs to ERROR level
go-filecoin log level error

# listen to the details of chain related subsystems
# logs related to fetching 
go-filecoin log level --subsystem=net/block_validator debug
go-filecoin log level --subsystem=peer-tracker debug
go-filecoin log level --subsystem=net.graphsync_fetcher debug

# logs related to scheduling fetched data for processing
go-filecoin log level --subsystem=chain.syncer debug 
go-filecoin log level --subsystem=chain.store debug 

# logs related to the actual processing 
go-filecoin log level --subsystem=consensus.expected debug
go-filecoin log level --subsystem=miner-actor debug

If this is still too noisy you can selectively reset some subsystems up to INFO or WARNING
Please comment corrections if the subsystem names have changed by the time you are reading this. They are all subject to change.