search

swar / Swar-Chia-Plot-Manager

This is a Cross-Platform Plot Manager for Chia Plotting that is simple, easy-to-use, and reliable.
GNU General Public License v3.0
1.26k stars 388 forks source link

Progress always at 0 #834

Open samuelvisser opened 3 years ago

samuelvisser commented 3 years ago

Sometimes, for whatever reason, the view (and status) screens show no progress at all. Phase always at 1, phase times empty, progress at 0 and temp_size at 0. However, if I check the logs, it is very clear all plots are running and some are almost done.

I even saw this happen a couple of times with only some plots, where the upper few plots showed everything correctly and the lower ones had everything at 0.

Sometimes, this gets fixed by just loading the view or status again. Sometimes, it doesn't matter if I reload a thousand times, it always says 0. What can I do about this, and is this a known issue?

Everything at 0 Only first 3 visible

PPMNUTRA commented 3 years ago

Same here image

Pockles commented 3 years ago

I actually just got the same issue. No idea why or what happened. Nothing I do seems to fix it.

cristi71000 commented 3 years ago

same here

samuelvisser commented 3 years ago

I've noticed this only happens when the CPU is at or near 100%. If it's about 80% or lower, it seems to always correctly load for me. But as the entire game here is to utilize my resources as much as possible, just at the moments where my system is running optimally it doesn't show me what it's doing. This really is beginning to be a big issue for me

Chispes commented 3 years ago

same here

pnvhome commented 3 years ago

the same problem, some times it works for more than 24 hours without any problems, some times few minutes and then shows 0

kingwsf commented 3 years ago

same dich on win10

cristi71000 commented 3 years ago

Yeh - I solved this by moving the log directory to a local folder rather than NAS. Probably the timeout to interogate NAS was too high

FortBoyarin commented 3 years ago

In my case the problem was related to the fact that I was running "python manager.py start" using the Windows Task Scheduler with administrator rights. The problem disappeared when I removed the corresponding check mark (I don't know what it is called in the English version, but the direct translation sounds like "run with the highest rights")

samuelvisser commented 3 years ago

Yeh - I solved this by moving the log directory to a local folder rather than NAS. Probably the timeout to interogate NAS was too high

When u stored the log files on NAS, did it show no progress at all like on the first screenshot, or partial progress like on the second? I save my logs to C drive..

samuelvisser commented 3 years ago

In my case the problem was related to the fact that I was running "python manager.py start" using the Windows Task Scheduler with administrator rights. The problem disappeared when I removed the corresponding check mark (I don't know what it is called in the English version, but the direct translation sounds like "run with the highest rights")

This i actually had myself, too. Thats when i took the first screenshot here actually. For me, in administrator mode it did not show any progress at all (thus i took the first screenshot). I guess it just couldnt access the logs. But, in normal mode it still happens for me, mostly like in screenshot. And sometimes it still doesnt show anything, which i guess is just being unlucky.

So, administrator mode caused the issue consistently, normal mode gets it periodically for me