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 389 forks source link

Plot manager view stays at zero progress #730

Open Kali123411 opened 3 years ago

Kali123411 commented 3 years ago

Plotman view shows zero progess although jobs appear to be running. Also CPU utilization rate seems stuck at 99 and does not correlate with Windows. Capture

bladeJumper commented 3 years ago

Found RuntimeError('SystemExtendedHandleInformation buffer too big') in process.py, line 216, could be the cause.

adamrcarmack commented 3 years ago

I'm having the same problem and I don't have excess handles.

My logs are showing that the plots are progressing, and I had 4 plots finish over night, so I don't know why it suddenly dropped the progress view.

alewir commented 3 years ago

My logs are showing that the plots are progressing, and I had 4 plots finish over night, so I don't know why it suddenly dropped the progress view.

image

Same here it was showing progress and then it stopped suddenly and shows only zeros as on screenshot above, although it seems in logs that plotting is progressing.

firesh commented 3 years ago

Some issue. image

gacz81 commented 3 years ago

That is an administrator permissions issue. I was having the same.

You may be was running the "python manager.py start" as administrator console and later you run the "python manager.py view" as a normal user. Try running both as administrator or both as normal user.

For me worked running both as administrator.

Hope it help. Let me know please.

alewir commented 3 years ago

I've tried it - started both as admin and it didn't help. On one of my PC's simple rebooting helped out of nowhere.

FortBoyarin commented 3 years ago

I can confirm that the problem seems to be associated with administrator permissions. 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")