Current log not being parsed

[Dudewhatzup]

Love your project - having trouble reading the "current" logs as they show up gray - screenshot below. Any suggestions on where I went wrong?

Thanks!

[stolk]

All that red makes me think your harvester is not running?

The grey, looks like debug.log is missing?

What if you do:

$ grep “eligible” ~/chia/mainnet/log/debug.log

What timestamps do you see?

Do you use chia gui? Do you actually see entries in “latest challenges”

On Tue, May 18, 2021 at 12:19 AM Dudewhatzup @.***> wrote:

Love your project - having trouble reading the "current" logs as they show up gray - screenshot below. Any suggestions on where I went wrong?

Thanks!

[image: image] https://user-images.githubusercontent.com/84373774/118608504-c47e1f80-b787-11eb-8369-45762e0eb3e7.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stolk/chiaharvestgraph/issues/17, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADPE4BQ4F5T6TSAZT4NLDLTOIIJNANCNFSM45B5WCLA .

-- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada @.***

[stolk]

Oh, I forgot a . before chia in the grep cmd.

On Tue, May 18, 2021 at 7:24 AM Bram Stolk @.***> wrote:

All that red makes me think your harvester is not running?

The grey, looks like debug.log is missing?

What if you do:

$ grep “eligible” ~/chia/mainnet/log/debug.log

What timestamps do you see?

Do you use chia gui? Do you actually see entries in “latest challenges”

On Tue, May 18, 2021 at 12:19 AM Dudewhatzup @.***> wrote:

Love your project - having trouble reading the "current" logs as they show up gray - screenshot below. Any suggestions on where I went wrong?

Thanks!

[image: image] https://user-images.githubusercontent.com/84373774/118608504-c47e1f80-b787-11eb-8369-45762e0eb3e7.png

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/stolk/chiaharvestgraph/issues/17, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADPE4BQ4F5T6TSAZT4NLDLTOIIJNANCNFSM45B5WCLA .

-- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada @.***

-- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada @.***

[Dudewhatzup]

Hey, I use nano, but I got what you meant. I checked the logs, they show current timestamps.

Maybe it has to do with the fact I'm running chia in a docker, but its funny that its not getting access to the "current" debug.log. Love to hear what you think might be the issue... (FYI tried sudo)

The red - sync issues that's been figured out since I updated to 1.1.6 beta

2021-05-18T17:43:30.509 harvester chia.harvester.harvester: INFO 1 plots were eligible for farming XXXXXXXXXX... Found 0 proofs. Time: 0.11401 s. Total 240 plots

[dsimon]

I saw a similar issue when I first installed. I am running chiaharvestgraph in Windows Subsystem for Linux (basically a lightweight linux VM). I resolved it by correcting the timezone settings in my WSL (Ubuntu) instance to match my Windows host. It seems the parser was reading logs created by Windows and interpreting them as 4 hours older than they were.

[internetpopular]

dsimon figured it out. I am running Chia in an Unraid docker and the logs are UTC. After changing the timezone to UTC in the debian docker that chiaharvestgraph was running in it works perfectly.

[Dudewhatzup]

Looks like that solved it. For those looking for the future, dsimon / internetpopular can you post for us linux noobs how to change timezone to UTC in docker / WSL?

[dsimon]

Looks like that solved it. For those looking for the future, dsimon / internetpopular can you post for us linux noobs how to change timezone to UTC in docker / WSL?

Certainly. I am running Ubuntu under WSL2, and this was the command I used:

sudo timedatectl set-timezone America/New-York

For more information: https://linuxhint.com/set-up-change-time-zone-ubuntu/

[Dudewhatzup]

Closed many thanks to all!