Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plots stuck in phase 3 for days #77

Closed
AliMickey opened this issue Jun 2, 2021 · 9 comments
Closed

Plots stuck in phase 3 for days #77

AliMickey opened this issue Jun 2, 2021 · 9 comments
Assignees
Labels
question Further information is requested

Comments

@AliMickey
Copy link

Hello,

plotman started two plot jobs before i stopped it to let them finish (for testing/learning).

Both of them are in phase 3 and seem to be stuck.

image

image

Node is fully synced if that makes a difference. Both the tmp and final dest is on a dedicated harddrive. It has sufficient space.
image

Summary:
image

The initial plot is one i made using the official gui before migrating to this.
The temp folder is full of .tmp files.

@AliMickey
Copy link
Author

BTW my system is constantly on around 50% cpu usage with no disk usage.

image

@guydavis
Copy link
Owner

guydavis commented Jun 3, 2021

Hello! Yes, that doesn't seem seem correct. Please take a look at some in-container info via docker exec -it machinaris bash:

df -hT
ps auxw | grep "plots create"

Is the problem repeatable for your setup? I would recommend killing the plots via the Plotting page and restarting the Machinaris container after clearing out the temp files.

As this issue seems to be Plotman-related, you may want to open an issue in their Github issues

@guydavis guydavis self-assigned this Jun 3, 2021
@guydavis guydavis added the question Further information is requested label Jun 3, 2021
@AliMickey
Copy link
Author

image

Won't i lose the tmp files? I was hoping to recover the queue somehow and finish them off. Otherwise i will probably just use the official cli/gui as i do not want to be uselessly stressing out my HDD.

@guydavis
Copy link
Owner

guydavis commented Jun 3, 2021

Yes, if you kill the plots then you would need to restart from zero, but days is far too long. Please share the complete docker run command you are using. I am interested to see your volume mappings to /plots and /plotting.

@AliMickey
Copy link
Author

image

@guydavis
Copy link
Owner

guydavis commented Jun 4, 2021

Hi, that docker compose looks good from what I can tell. Sorry for the trouble you're encountering.

FYI, there is a new release today, so it may be worth upgrading and trying again to see if this recurs.

Please start with a single plot at a time (global_max_jobs=1 in Settings | Plotting). If that works, then increase the Plotting settings to get more jobs running in parallel.

@AliMickey
Copy link
Author

Updated and changed the config now.

Started a new plot, if this does not complete then unfortunately ill have to go back to the official gui.

I'll be happy to test and provide logs/support though to fix this.

@AliMickey
Copy link
Author

Sadly its been stuck here for a while again.

image

image

@AliMickey
Copy link
Author

I think it may be a bad ram stick, dont know how my initial plot went through but now nothing else is finishing. I'll close this for now and try this tool again down the line when i replace the stick.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants