chiaharvestgraph
chiaharvestgraph copied to clipboard
stolk
Error message on startup: UNEXPECTED TIME VALUE
I see this when starting the chiaharvestgraph on Raspberry Pi OS (Debian). It then appear to run normally, though, so not sure what the impact is.
tim=1633092685 lasttimehi=1633702500 d=-609815 slot=-6 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1633092937 lasttimehi=1633702500 d=-609563 slot=-6 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1633097402 lasttimehi=1633702500 d=-605098 slot=-1 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1633097446 lasttimehi=1633702500 d=-605054 slot=-1 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1633097563 lasttimehi=1633702500 d=-604937 slot=-1 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12
I have the same issue. Has there been any investigation or resolution for this error?
tim=1640683059 lasttimehi=1641430800 d=-747741 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683072 lasttimehi=1641430800 d=-747728 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683080 lasttimehi=1641430800 d=-747720 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683135 lasttimehi=1641430800 d=-747665 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683145 lasttimehi=1641430800 d=-747655 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683188 lasttimehi=1641430800 d=-747612 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683188 lasttimehi=1641430800 d=-747612 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12
Did your computer clock change recently?
On Wed, Jan 5, 2022 at 4:58 PM nothingshocking @.***> wrote:
I have the same issue. Has there been any investigation or resolution for this error?
tim=1640683059 lasttimehi=1641430800 d=-747741 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683072 lasttimehi=1641430800 d=-747728 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683080 lasttimehi=1641430800 d=-747720 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683135 lasttimehi=1641430800 d=-747665 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683145 lasttimehi=1641430800 d=-747655 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683188 lasttimehi=1641430800 d=-747612 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640683188 lasttimehi=1641430800 d=-747612 slot=-159 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12
— Reply to this email directly, view it on GitHub https://github.com/stolk/chiaharvestgraph/issues/49#issuecomment-1006199204, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADPE4HFVFUOEIW6OOYAH53UUTSLRANCNFSM5FTWS6DA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Owner/Director of Game Studio Abraham Stolk Inc. Vancouver BC, Canada @.***
It did after the time change in October, or whenever that was. Not recently as far as I am aware.
Mine started around week or so prior to my post (10/08/2021) but I don't have logs back that far anymore.
It did after the time change in October, or whenever that was. Not recently as far as I am aware.
Daylight Savings was on 11/07/2021, so I don't think it's related to that.
Agreed, DST doesn't seem to be the case. For me the graph is working fine once it starts up. The error starts directly after starting as it starts to go through the log directory.
xxxxxx@xxxxxx:~/chia-blockchain/chiaharvestgraph$ ./chiaharvestgraph ~/.chia/mainnet/log Monitoring directory /home/xxxxxx/.chia/mainnet/log err - UNEXPECTED TIME VALUE. tim=1640384941 lasttimehi=1641483000 d=-1098059 slot=-549 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640385014 lasttimehi=1641483000 d=-1097986 slot=-548 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 err - UNEXPECTED TIME VALUE. tim=1640385021 lasttimehi=1641483000 d=-1097979 slot=-548 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12
The error stops when it gets to debug.log.4 and the start up messages show it continues through the remaining logs (3, 2, etc.) and then the graph starts.
err - UNEXPECTED TIME VALUE. tim=1640683188 lasttimehi=1641483000 d=-799812 slot=-217 REPORT THIS MESSAGE TO https://github.com/stolk/chiaharvestgraph/issues/12 read 121445 lines from log debug.log.4 read 132568 lines from log debug.log.3 read 135695 lines from log debug.log.2
When I noticed the error sometime back it was after I had some Node/Farmer issues due to RPi storage limitations from the DB growth. I resolved those issues and assumed the ChiaHarvestGraph startup error was related to issues with the older logs when the Farmer/Node was shitting the bed. Since that is resolved and that those older logs are gone that assumption doesn't make sense hence my reaching out to this thread. I hope this helps add some more helpful detail.