Closed guydavis closed 3 years ago
guydavis
commented
3 years ago Thanks for testing the very latest test release. Moved your comment to its own issue. Please attach your logs. Did you leave Plotman running when you kill the only running plot job?
keithaustin
commented
3 years ago I was experiencing the same issue, and I'm not sure this was the cause, but my config was incorrect. I had both pool_pk and pool_contract_address set, which was preventing me from starting a plotting job at least. Could not kill a plot even after deleting temporary files but after fixing the config issue it seemed to kill it.
ApfelBirneKreis
commented
3 years ago i know that but when i change to the pool address it is not plotting. Plotman does not even start and there is nothing in the logs im plotting with madmax.
madmax performance slowed down too. cpu power is used in bursts now. very strange behaviour. time to plot increased from 30 mins to almost 80 mins
guydavis
commented
3 years ago i know that but when i change to the pool address it is not plotting. Plotman does not even start and there is nothing in the logs
Hi, please ensure you have pulled the latest :test image. Then ensure you have a working config file. Validate it by running:
docker exec -it machinaris bash
plotman statusAny errors in the config should become apparent when checking plotman status.
Then try to start Plotman and attach all logs here. Thanks!
ApfelBirneKreis
commented
3 years ago plot id plotter k tmp dst wall phase tmp pid stat mem user sys io -------- 32 /plotting/ /pool-plots/ 4:21 ?:? 0 1544 SLP 4.2Gi 16:19 1:06 1s
Total jobs: 1 Jobs in /plotting/: 1
ApfelBirneKreis
commented
3 years ago so it is plotting but not showing up in the gui? And it can`t kill it because it does not have an ID?
guydavis
commented
3 years ago so it is plotting but not showing up in the gui? And it can`t kill it because it does not have an ID?
Please attach all logs here. Thanks!
ApfelBirneKreis
commented
3 years ago [2021-07-06 19:57:24 +0200] [1089] [INFO] Failed to list files at /private-plots INFO:Machinaris API:Failed to list files at /private-plots [2021-07-06 19:57:24 +0200] [1089] [INFO] Traceback (most recent call last): File "/machinaris/api/commands/chia_cli.py", line 61, in load_plots_farming entries = (os.path.join(dir_path, file_name) for file_name in os.listdir(dir_path)) FileNotFoundError: [Errno 2] No such file or directory: '/private-plots '
INFO:Machinaris API:Traceback (most recent call last): File "/machinaris/api/commands/chia_cli.py", line 61, in load_plots_farming entries = (os.path.join(dir_path, file_name) for file_name in os.listdir(dir_path)) FileNotFoundError: [Errno 2] No such file or directory: '/private-plots '
[2021-07-06 19:57:24 +0200] [1089] [INFO] Failed to load plots farming and send. INFO:Machinaris API:Failed to load plots farming and send. [2021-07-06 19:57:24 +0200] [1089] [INFO] Traceback (most recent call last): File "/machinaris/api/commands/chia_cli.py", line 61, in load_plots_farming entries = (os.path.join(dir_path, file_name) for file_name in os.listdir(dir_path)) FileNotFoundError: [Errno 2] No such file or directory: '/private-plots '
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/machinaris/api/schedules/status_plots.py", line 23, in update plots_farming = chia_cli.load_plots_farming() File "/machinaris/api/commands/chia_cli.py", line 68, in load_plots_farming flash('Unable to list plots at {0}. Did you mount your plots directories?'.format(dir_path), 'danger') File "/chia-blockchain/venv/lib/python3.9/site-packages/flask/helpers.py", line 389, in flash flashes = session.get("_flashes", []) File "/chia-blockchain/venv/lib/python3.9/site-packages/werkzeug/local.py", line 422, in get obj = instance._get_current_object() File "/chia-blockchain/venv/lib/python3.9/site-packages/werkzeug/local.py", line 544, in _get_current_object return self.__local() # type: ignore File "/chia-blockchain/venv/lib/python3.9/site-packages/flask/globals.py", line 33, in _lookup_req_object raise RuntimeError(_request_ctx_err_msg) RuntimeError: Working outside of request context.
This typically means that you attempted to use functionality that needed an active HTTP request. Consult the documentation on testing for information about how to avoid this problem.
INFO:Machinaris API:Traceback (most recent call last): File "/machinaris/api/commands/chia_cli.py", line 61, in load_plots_farming entries = (os.path.join(dir_path, file_name) for file_name in os.listdir(dir_path)) FileNotFoundError: [Errno 2] No such file or directory: '/private-plots '
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/machinaris/api/schedules/status_plots.py", line 23, in update plots_farming = chia_cli.load_plots_farming() File "/machinaris/api/commands/chia_cli.py", line 68, in load_plots_farming flash('Unable to list plots at {0}. Did you mount your plots directories?'.format(dir_path), 'danger') File "/chia-blockchain/venv/lib/python3.9/site-packages/flask/helpers.py", line 389, in flash flashes = session.get("_flashes", []) File "/chia-blockchain/venv/lib/python3.9/site-packages/werkzeug/local.py", line 422, in get obj = instance._get_current_object() File "/chia-blockchain/venv/lib/python3.9/site-packages/werkzeug/local.py", line 544, in _get_current_object return self.__local() # type: ignore File "/chia-blockchain/venv/lib/python3.9/site-packages/flask/globals.py", line 33, in _lookup_req_object raise RuntimeError(_request_ctx_err_msg) RuntimeError: Working outside of request context.
This typically means that you attempted to use functionality that needed an active HTTP request. Consult the documentation on testing for information about how to avoid this problem.
I can confirm it is farming in thos directorys and they are correctly mounted in the docker.
ApfelBirneKreis
commented
3 years ago nohup: ignoring input ...starting plot loop ...sleeping 20 s: (True, 'Starting plot job: chia_plot -n 1 -r 10 -u 256 -t /plotting/ -d /plots/ -f 87b595....... -c xch1th....... ; logging to /root/.chia/plotman/logs/2021-07-04T21_00_09.891087+02_00.plot.log')
this plot was started via cli command. the plot i tried to start over the gui doesn`t even list.
ApfelBirneKreis
commented
3 years ago INFO [alembic.env] Migrating database
ApfelBirneKreis
commented
3 years ago [2021-07-06 15:18:35 +0200] [1092] [INFO] Starting gunicorn 20.1.0 [2021-07-06 15:18:35 +0200] [1092] [INFO] Listening at: http://0.0.0.0:8926 (1092) [2021-07-06 15:18:35 +0200] [1092] [INFO] Using worker: sync [2021-07-06 15:18:35 +0200] [1176] [INFO] Booting worker with pid: 1176 [2021-07-06 15:18:35 +0200] [1197] [INFO] Booting worker with pid: 1197
ApfelBirneKreis
commented
3 years ago and the current config:
# Learn more about Plotman at https://github.com/ericaltendorf/plotman
# https://github.com/ericaltendorf/plotman/wiki/Configuration#versions
version: [2]
logging:
# DO NOT CHANGE THIS IN-CONTAINER PATH USED BY MACHINARIS!
plots: /root/.chia/plotman/logs
user_interface:
use_stty_size: False
commands:
interactive:
autostart_plotting: False
autostart_archiving: False
# Where to plot and log.
directories:
# One or more directories to use as tmp dirs for plotting. The
# scheduler will use all of them and distribute jobs among them.
# It assumes that IO is independent for each one (i.e., that each
# one is on a different physical device).
#
# If multiple directories share a common prefix, reports will
# abbreviate and show just the uniquely identifying suffix.
# REMEMBER ALL PATHS ARE IN-CONTAINER, THEY MAP TO HOST PATHS
tmp:
- /plotting
# Optional: Allows overriding some characteristics of certain tmp
# directories. This contains a map of tmp directory names to
# attributes. If a tmp directory and attribute is not listed here,
# it uses the default attribute setting from the main configuration.
#
# Currently support override parameters:
# - tmpdir_max_jobs
#tmp_overrides:
# In this example, /plotting3 is larger than the other tmp
# dirs and it can hold more plots than the default.
#/plotting3:
# tmpdir_max_jobs: 5
# Optional: tmp2 directory. If specified, will be passed to
# the chia and madmax plotters as the '-2' param.
#tmp2: /plotting2
# One or more directories; the scheduler will use all of them.
# These again are presumed to be on independent physical devices,
# so writes (plot jobs) and reads (archivals) can be scheduled
# to minimize IO contention.
# REMEMBER ALL PATHS ARE IN-CONTAINER, THEY MAP TO HOST PATHS
dst:
- /private-plots
- /pool-plots
# See: https://github.com/guydavis/machinaris/wiki/Plotman#archiving
#archiving:
#target: rsyncd
#env:
#site_root: /mnt/disks
#user: root
#host: aragorn
#rsync_port: 12000
#site: disks
# Plotting scheduling parameters
scheduling:
# Run a job on a particular temp dir only if the number of existing jobs
# before tmpdir_stagger_phase_major tmpdir_stagger_phase_minor
# is less than tmpdir_stagger_phase_limit.
# Phase major corresponds to the plot phase, phase minor corresponds to
# the table or table pair in sequence, phase limit corresponds to
# the number of plots allowed before [phase major, phase minor]
tmpdir_stagger_phase_major: 4
tmpdir_stagger_phase_minor: 0
# Optional: default is 1
tmpdir_stagger_phase_limit: 1
# Don't run more than this many jobs at a time on a single temp dir.
# Increase for staggered plotting by chia, leave at 1 for madmax sequential plotting
tmpdir_max_jobs: 1
# Don't run more than this many jobs at a time in total.
# Increase for staggered plotting by chia, leave at 1 for madmax sequential plotting
global_max_jobs: 1
# Don't run any jobs (across all temp dirs) more often than this, in minutes.
global_stagger_m: 30
# How often the daemon wakes to consider starting a new plot job, in seconds.
polling_time_s: 20
# Configure the plotter. See: https://github.com/guydavis/machinaris/wiki/Plotman#plotting
plotting:
farmer_pk: 87b5956......
#pool_pk: a952f596......
pool_contract_address: xch1th.......
# If you enable 'chia', plot in *parallel* with higher tmpdir_max_jobs and global_max_jobs
# If you enable 'madmax', plot in *sequence* with very low tmpdir_max_jobs and global_max_jobs
type: madmax
# The chia plotter: https://github.com/Chia-Network/chia-blockchain
chia:
k: 32 # k-size of plot, leave at 32 most of the time
e: False # Disable bitfield back sorting (default is True)
n_threads: 2 # Threads per job
n_buckets: 128 # Number of buckets to split data into
job_buffer: 3389 # Per job memory
# The madmax plotter: https://github.com/madMAx43v3r/chia-plotter
madmax:
n_threads: 10 # Default is 4, SLOWLY crank up if you have many cores
n_buckets: 256 # Default is 256Fix your Docker run/compose. You are farming a non-existent directory:
FileNotFoundError: [Errno 2] No such file or directory: '/private-plots '
Note, the trailing space you have been using in the name.
Please see the wiki on how to run Machinaris correctly with more than one final plots directory.
Provide the exact run command you are using. Also, you can simply attach files to this issue, you don't have to paste separate comments...
another issue i found. when i try to kill plots it does not work. not stopping nor deleting files. tryed 5 full reinstalls. same problem
Originally posted by @ApfelBirneKreis in https://github.com/guydavis/machinaris/issues/131#issuecomment-874259710