-
Notifications
You must be signed in to change notification settings - Fork 278
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
Unexpected plot log and process count #161
Comments
From this information I'm not sure what is going on. The log files aren't proof that plotman has started 10 simultaneous processes and the two found processes doesn't show that plotman is missing processes that are running. Could you share the following to help debug this please?
My guess is that the plotting processes are terminating for some reason. I vaguely guess based on the timing that it isn't due to completion. Usually plots that fail do so fairly immediately, in my experience. But... That's the best guess I've got until we can look over the additional information. |
Also, let's add the full configuration file to the list. (edited above) |
Hi @altendky, thanks for the help. I inspected the log files and looks like plots were not terminated, I'll attach the zip below. Unfortunately, I already killed the plot jobs since my plotting drive was full. Here is the output of the command: config.yml:
zip of log files: |
There are incomplete logs. They don't indicate why. If it happens again go ahead and collect the info again. Sorry. |
No worries. I'll add more details if I can re-produce the issue. Thanks! |
+1. Running plotman in WSL2 with 1 tmp drive and 1 dst drive without archiving:
Here is my configuration for scheduling:
My understanding is that maximum of 8 jobs will be created with this configuration, and should be able to display the status of all the 8 jobs. However, there are 10 plotting logs created and the only shows 2 jobs:
Did I miss anything or mis-understand the configuration? Please help, thanks!
Originally posted by @zrjaa1 in #149 (comment)
The text was updated successfully, but these errors were encountered: