Octoprint/Klipper diagnostics

When you install the kiauh way:

klippy.log is in ~/printer_data/logs 

read log via 

~/klipper/scripts/logextract.py ~/printer_data/logs/klippy.log

When you install the Octopi way..

Klippy.log is in tmp.

read Klippy.log using  ~/klipper/scripts/logextract.py  i.e

cp ~/tmp/klippy.log . 

~/klipper/scripts/logextract.py  klippy.log 

Octoprint logs are in:

~/.octoprint/logs

its not uncommon to have klipper fail to connect if you use mcu_pi.

to restart klipper, type following in linux login

sudo service klipper restart

systemctl stop octoprint

service klipper restart

systemctl start octoprint

to add debug into .cfg

{ action_respond_info("_PRINT_START") }

alias cssh='ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null'

sudo service klipper stop;rm klippy.log ;sudo service klipper start

swap between octoprint and 

sudo systemctl disable octoprint.service

sudo systemctl enable moonraker.service

or

sudo systemctl enable moonraker.service

sudo systemctl enable octoprint.service