trying2016/common-tools/utils/utils.go:165 error

[victorprosa]

Dear all,

Some of my plots become invalid after some time on hpool's miner on all versions since 1.3.0 (including 1.4.0-2). The problem doesn't happen on version 1.2.0-5 and on official Chia client. The problem happens both on the Windows version and on the linux-arm version. The client (on 1.4.0-2) throws the following error:

time="2021-05-26T13:54:01-03:00" level=info msg="new mining info" capacity="8.22 TB" file=loggers.go func=logging.CPrint height=340213 jobId=303943903 line=168 scan consume=354 scan time="2021-05-26 13:53:49" tid=52 time="2021-05-26T13:54:02-03:00" level=error msg="prove run error" error="hpool.com/dev/miner-client/miner/chain/chia.(*PlotterSpace).SetPlotInvalid(0x0, 0x1e70120)\n\tminer/chain/chia/plotterSpace.go:507 +0x12c\nhpool.com/dev/miner-client/miner/chain/chia.(*Prove).submitProve(0x1c93240, 0x1e9e190)\n\tminer/chain/chia/prove.go:195 +0x3c0\nhpool.com/dev/miner-client/miner/chain/chia.(*Prove).run(0x1c93240)\n\tminer/chain/chia/prove.go:156 +0x130\ngithub.com/trying2016/common-tools/utils.SafeGo.func1(0x4ea544, 0x1c9ee58)\n\tvendor/github.com/trying2016/common-tools/utils/utils.go:182 +0x48\ncreated by github.com/trying2016/common-tools/utils.SafeGo\n\tvendor/github.com/trying2016/common-tools/utils/utils.go:165 +0x34" f7="{loggers.go,logging.CPrint,156}" f8="{prove.go,chia.(*Prove).Start.func1,71}" f9="{utils.go,utils.SafeGo.func1.1,172}" tid=27 time="2021-05-26T13:54:09-03:00" level=info msg="new mining info" capacity="8.12 TB" file=loggers.go func=logging.CPrint height=340213 jobId=3411567634 line=168 scan consume=354 scan time="2021-05-26 13:54:01" tid=52

There doesn't seem to be a pattern on which plots turn invalid nor the time required to become invalid, sometimes one plot simply becomes invalid, eventually more become and I restart the client. After restarting all plots are valid and they slowly become invalid but the ones becoming invalid after the restart are different than the ones that were invalid before the restart. The number of files remain the same on GUI but the capacity is reduced. On the website the pools affected become "offline" and the capacity is reduced. The plots affected remain invalid until a restart of the client.

Could the devs (@trying2016 @hpool-dev) please shine some light on what causes this behaviour or what they need to investigate further?

Thank you.

[gddrx]

+1

[equallygoose]

Please make the SetPlotInvalid log message print the bad plot file name

[tyborall]

I have the same and even I can reproduce that in my scenario. I think I'am false recognized as bad user and I know why this happened... @hpool-dev @trying2016 please could you look on my comments I put in #503... And maybe please check if I'am on your "suspicious beaviour" users list and if so please contact me... I think know what's the cause for this... Here is my API key: 8e0a2ce3-7ec0-47bd-9fdb-f420bd7bad2a