How to Check If Everything is Working (or Not)

🛠️ A work-in-progress 🛠️

This doc assumes you know how to use the CLI. Using the CLI is the best way to troubleshoot (and to do everything Chinilla too). The Quick Start Guide and CLI Commands Reference have useful info to get you familiar with the CLI.

Where to Find Things

The file structure for Linux, macOS, and Windows versions of Chinilla are similar.

/home/user
├─ .chinilla/
│   └── vanillanet/
│      ├─ config/
│      │      ├─ config.yaml
│      │      └─ ssl/
│      │            └─ (and more...)
│      ├─ db/
│      ├─ log/
│      │      └─ debug.log
│      ├─ run/
│      │      └─ (and more...)
│      └─ wallet/
│             └─ (and more...)
└── /chinilla-blockchain
       └─ (and more...)

Linux & macOS

• Chinilla config: ~/.chinilla/vanillanet/config/config.yaml
• Chinilla logs: ~/.chinilla/vanillanet/log/

Windows

• Chinilla config: C:\Users\%USERNAME%\.chinilla\vanillanet\config\config.yaml
• Chinilla logs: C:\Users\%USERNAME%\.chinilla\vanillanet\log\

Logs

In config.yaml you can set the level of detail for your logs.

Look for this section in config.yaml. It’s useful to change the logger setting log_level from WARNING to INFO to get the detail needed to troubleshoot.

logging: &id001
    log_filename: log/debug.log
    log_level: INFO
    log_stdout: false

You can run grep (Linux, macOS) or Select-String (Windows) to search through your logs for relevant information.

Is It Working?

If you want to quickly find errors, run this:

• Linux/macOS: cat ~/.chinilla/vanillanet/log/debug.log | grep -i 'error'
• Windows: Get-Content -Path "~\.chinilla\vanillanet\log\debug.log" | Select-String -Pattern "error"

Harvester

The time it takes to do a proof challenge should be below 30 seconds. If you see higher times, something is wrong with your setup.

Here are some commands you can use to examine debug.log for problems.

• Linux/macOS: tail ~/.chinilla/vanillanet/log/debug.log | grep eligible
• Windows:
  • Select-String -Path “~\.chinilla\vanillanet\log\debug*” -Pattern “eligible”
  • Select-String -Path “~\.chinilla\vanillanet\log\debug*” -Pattern “Found [^0] proof”
  • Select-String -Path “~\.chinilla\vanillanet\log\debug*” -Pattern “Farmed unfinished_block”
  • Get-Content -Path "~\.chinilla\vanillanet\log\debug.log" -Wait | Select-String -Pattern "found"

Plotting

You can find the documentation for the check command on the CLI Commands Reference - check page

• To check all your plots, run chinilla plots check. This will check all directories you have listed in your config.yaml to contain plots.
• Use chinilla plots check -h to see the options for this command