TexasUnraid Posted June 17, 2021 Share Posted June 17, 2021 1 hour ago, Benji said: Currently, the forks all use Chia plots. You build the wallet from your Chia mnemonic and can use your key and plots on the other network. I currently have Chia (Machinaris), Chaingreen and Flax (Win10 GUIs) all farming the same plots. I don't know a whole lot about dockers and how they work, so I can't comment much. That being said, I imagined just having 3 separate dockers, one for each blockchain. So basically you can farm the others for free? Where do I sign up lol. What is there to lose? Separate dockers would be fine I agree for those that want to do this. Although if they take off, combining them into a single docker would be interesting and cut the setup time by 2/3's. Quote Link to comment
TexasUnraid Posted June 18, 2021 Share Posted June 18, 2021 Ok, I am genuinely trying to find this "flax" you speak of, I can not find a thing except for the seeds. lol Quote Link to comment
guy.davis Posted June 18, 2021 Author Share Posted June 18, 2021 1 hour ago, TexasUnraid said: Ok, I am genuinely trying to find this "flax" you speak of, I can not find a thing except for the seeds. lol Bit of guess, but this is what I found: https://www.chaingreen.org/ https://flaxnetwork.org/ No idea about them, never tried them, so be cautious. Interesting the concept of multiple forks though. Quote Link to comment
TexasUnraid Posted June 18, 2021 Share Posted June 18, 2021 (edited) yeah I found the chiagreen site, good find on the flax. Indeed, if I had to replot or use space exclusively for them I would not even consider it but if it shares the chia plots I figure it is worth looking into. I also heard that the Makers of chia had this in mind from the start apparently, the ability for other coins/networks to piggyback off the chia framework or something. The nail in the coffin at this point is I have nothing to loose, I will be creating a new wallet when pools come out anyways, It is farming on a dedicated machine with hpool sandboxed and my hpool funds will be withdrawn to another wallet as well, so since this wallet is already compromised, might as well go all in lol. Edited June 18, 2021 by TexasUnraid Quote Link to comment
guy.davis Posted June 18, 2021 Author Share Posted June 18, 2021 For the adventurous types, the current Machinaris test version offers: Central control of multiple Machinaris workers on your LAN. Madmax plotter integration via customized Plotman Test version image: ghcr.io/guydavis/machinaris:test Please report any issues on Github. 2 Quote Link to comment
TexasUnraid Posted June 18, 2021 Share Posted June 18, 2021 VERY nice, I am totally going to switch back to machinaris now that it has madmax. Multiple workers is also very helpful as I have my main server I keep debating setting up for plotting. 1 Quote Link to comment
HATEME Posted June 19, 2021 Share Posted June 19, 2021 (edited) @guy.davis I installed the test version, but can't figure out how to turn on mad max, theres only one option for plotter drop down menu and even with changing config to suit a mad max plotter, with pool/farm key, Its not showing a log file, but I can tell it's only using 2 threads vs the full fat cpu. EDIT: the config file is saved just like your wiki, but plotting never starts and goes straight to stopped, log for drop down menu says: nohup: ignoring input Namespace(cmd='kill', idprefix=['efb07080']) Pausing PID 1556, plot id efb07080bad55792cdca8e0813f977d528a2515adfc55864e8e210bcffe7dc6d Will kill pid 1556, plot id efb07080bad55792cdca8e0813f977d528a2515adfc55864e8e210bcffe7dc6d Will delete 211 temp files Are you sure? ("y" to confirm): killing... cleaning up temp files... Edited June 19, 2021 by HATEME Quote Link to comment
rukiftw Posted June 20, 2021 Share Posted June 20, 2021 (edited) 5 hours ago, HATEME said: @guy.davis I installed the test version, but can't figure out how to turn on mad max, theres only one option for plotter drop down menu and even with changing config to suit a mad max plotter, with pool/farm key, Its not showing a log file, but I can tell it's only using 2 threads vs the full fat cpu. EDIT: the config file is saved just like your wiki, but plotting never starts and goes straight to stopped, log for drop down menu says: nohup: ignoring input Namespace(cmd='kill', idprefix=['efb07080']) Pausing PID 1556, plot id efb07080bad55792cdca8e0813f977d528a2515adfc55864e8e210bcffe7dc6d Will kill pid 1556, plot id efb07080bad55792cdca8e0813f977d528a2515adfc55864e8e210bcffe7dc6d Will delete 211 temp files Are you sure? ("y" to confirm): killing... cleaning up temp files... I followied this guide: https://github.com/guydavis/machinaris/wiki/Plotman#plotting and https://github.com/guydavis/machinaris/wiki/MadMax it does not work. machinaris doesnt know what the madmax type is. Error: Traceback (most recent call last): File "/chia-blockchain/venv/lib/python3.8/site-packages/plotman/configuration.py", line 40, in get_validated_configs loaded = schema.load(config_objects) File "/chia-blockchain/venv/lib/python3.8/site-packages/marshmallow/schema.py", line 714, in load return self._do_load( File "/chia-blockchain/venv/lib/python3.8/site-packages/marshmallow/schema.py", line 896, in _do_load raise exc marshmallow.exceptions.ValidationError: {'plotting': {'e': ['Missing data for required field.'], 'k': ['Missing data for required field.'], 'job_buffer': ['Missing data for required field.'], 'type': ['Unknown field.']}} The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/chia-blockchain/venv/bin/plotman", line 8, in <module> sys.exit(main()) File "/chia-blockchain/venv/lib/python3.8/site-packages/plotman/plotman.py", line 137, in main cfg = configuration.get_validated_configs(config_text, config_path) File "/chia-blockchain/venv/lib/python3.8/site-packages/plotman/configuration.py", line 42, in get_validated_configs raise ConfigurationException( plotman.configuration.ConfigurationException: Config file at: '/root/.chia/plotman/plotman.yaml' is malformed Edited June 20, 2021 by rukiftw doesnt work Quote Link to comment
guy.davis Posted June 20, 2021 Author Share Posted June 20, 2021 (edited) On 6/19/2021 at 9:50 PM, rukiftw said: I followied this guide: https://github.com/guydavis/machinaris/wiki/Plotman#plotting and https://github.com/guydavis/machinaris/wiki/MadMax it does not work. machinaris doesnt know what the madmax type is. Hi, please create an Issue on Github, attaching your full plotman.yaml and also a screenshot showing full browser window with every version number at bottom. That will help me diagnose the issue. Also, drop into the Discord tomorrow for more hand's on help. Thanks for testing! 2021-06-20: Just pushed an updated test image to DockerHub with multiple fixes. Please be sure to pull the latest if you are giving it another try. Edited June 21, 2021 by guy.davis Updated test image. Quote Link to comment
guy.davis Posted June 25, 2021 Author Share Posted June 25, 2021 Good day! The next version of Machinaris is now available: v0.4.0. Thanks to all those who tested and provided feedback during the release cycle. All contributions are appreciated! Changes: - Support for the Madmax plotter, in addition to the official Chia plotter. - Manage multiple plotters, harvesters, and farmers across your LAN, all from a single WebUI on one controller system. - A full REST API for developers to extend and integrate with Machinaris. Notes: * Due to configuration file changes in Plotman, you may need to save a new config on your Settings | Plotting page: * --> get a Chia plotter template * --> get a Madmax plotter template 2 Quote Link to comment
Ystebad Posted June 26, 2021 Share Posted June 26, 2021 (edited) Downloaded new version and trying to use the new madmax. I think I changed my config for plotting as per recommendation but each time I try to start it it says "starting" then "plotman started successfully" but no cores being used and nothing showing up in plotting as ongoing and it says "idle" at the top. My config: # Learn more about Plotman at https://github.com/ericaltendorf/plotman # https://github.com/ericaltendorf/plotman/wiki/Configuration#versions version: [1] 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: - /madmaxdisk9 # 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: - /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: yes this is my number here pool_pk: another private number here # 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: 4 # Default is 4, crank up if you have many cores n_buckets: 256 # Default is 256 PLOTTING LOGS: Autoscroll ...sleeping 20 s: (False, 'stagger (62s/1800s)') ...sleeping 20 s: (False, 'stagger (83s/1800s)') ...sleeping 20 s: (False, 'stagger (103s/1800s)') ...sleeping 20 s: (False, 'stagger (124s/1800s)') ...sleeping 20 s: (False, 'stagger (145s/1800s)') ...sleeping 20 s: (False, 'stagger (166s/1800s)') ...sleeping 20 s: (False, 'stagger (186s/1800s)') ...sleeping 20 s: (False, 'stagger (207s/1800s)') ...sleeping 20 s: (False, 'stagger (228s/1800s)') ...sleeping 20 s: (False, 'stagger (249s/1800s)') ...sleeping 20 s: (False, 'stagger (269s/1800s)') ...sleeping 20 s: (False, 'stagger (290s/1800s)') ...sleeping 20 s: (False, 'stagger (311s/1800s)') ...sleeping 20 s: (False, 'stagger (331s/1800s)') ...sleeping 20 s: (False, 'stagger (352s/1800s)') ...sleeping 20 s: (False, 'stagger (373s/1800s)') ...sleeping 20 s: (False, 'stagger (393s/1800s)') ...sleeping 20 s: (False, 'stagger (414s/1800s)') ...sleeping 20 s: (False, 'stagger (435s/1800s)') ...sleeping 20 s: (False, 'stagger (456s/1800s)') ...sleeping 20 s: (False, 'stagger (477s/1800s)') ...sleeping 20 s: (False, 'stagger (497s/1800s)') ...sleeping 20 s: (False, 'stagger (518s/1800s)') ...sleeping 20 s: (False, 'stagger (539s/1800s)') ...sleeping 20 s: (False, 'stagger (560s/1800s)') ...sleeping 20 s: (False, 'stagger (580s/1800s)') ...sleeping 20 s: (False, 'stagger (601s/1800s)') ...sleeping 20 s: (False, 'stagger (622s/1800s)') ...sleeping 20 s: (False, 'stagger (643s/1800s)') ...sleeping 20 s: (False, 'stagger (664s/1800s)') ...sleeping 20 s: (False, 'stagger (684s/1800s)') ...sleeping 20 s: (False, 'stagger (705s/1800s)') ...sleeping 20 s: (False, 'stagger (726s/1800s)') ...sleeping 20 s: (False, 'stagger (747s/1800s)') ...sleeping 20 s: (False, 'stagger (768s/1800s)') ...sleeping 20 s: (False, 'stagger (788s/1800s)') ...sleeping 20 s: (False, 'stagger (809s/1800s)') ...sleeping 20 s: (False, 'stagger (830s/1800s)') ...sleeping 20 s: (False, 'stagger (851s/1800s)') ...sleeping 20 s: (False, 'stagger (872s/1800s)') ...sleeping 20 s: (False, 'stagger (892s/1800s)') ...sleeping 20 s: (False, 'stagger (913s/1800s)') ...sleeping 20 s: (False, 'stagger (934s/1800s)') ...sleeping 20 s: (False, 'stagger (957s/1800s)') ...sleeping 20 s: (False, 'stagger (978s/1800s)') ...sleeping 20 s: (False, 'stagger (998s/1800s)') ...sleeping 20 s: (False, 'stagger (1019s/1800s)') ...sleeping 20 s: (False, 'stagger (1040s/1800s)') ...sleeping 20 s: (False, 'stagger (1061s/1800s)') ...sleeping 20 s: (False, 'stagger (1081s/1800s)') ...sleeping 20 s: (False, 'stagger (1102s/1800s)') ...sleeping 20 s: (False, 'stagger (1122s/1800s)') ...sleeping 20 s: (False, 'stagger (1143s/1800s)') ...sleeping 20 s: (False, 'stagger (1164s/1800s)') ...sleeping 20 s: (False, 'stagger (1185s/1800s)') ...sleeping 20 s: (False, 'stagger (1206s/1800s)') ...sleeping 20 s: (False, 'stagger (1226s/1800s)') ...sleeping 20 s: (False, 'stagger (1247s/1800s)') ...sleeping 20 s: (False, 'stagger (1268s/1800s)') ...sleeping 20 s: (False, 'stagger (1288s/1800s)') ...sleeping 20 s: (False, 'stagger (1311s/1800s)') ...sleeping 20 s: (False, 'stagger (1333s/1800s)') ...sleeping 20 s: (False, 'stagger (1354s/1800s)') ...sleeping 20 s: (False, 'stagger (1376s/1800s)') ...sleeping 20 s: (False, 'stagger (1397s/1800s)') ...sleeping 20 s: (False, 'stagger (1419s/1800s)') ...sleeping 20 s: (False, 'stagger (1440s/1800s)') ...sleeping 20 s: (False, 'stagger (1460s/1800s)') ...sleeping 20 s: (False, 'stagger (1481s/1800s)') ...sleeping 20 s: (False, 'stagger (1502s/1800s)') ...sleeping 20 s: (False, 'stagger (1523s/1800s)') ...sleeping 20 s: (False, 'stagger (1543s/1800s)') ...sleeping 20 s: (False, 'stagger (1564s/1800s)') ...sleeping 20 s: (False, 'stagger (1585s/1800s)') ...sleeping 20 s: (False, 'stagger (1606s/1800s)') ...sleeping 20 s: (False, 'stagger (1626s/1800s)') ...sleeping 20 s: (False, 'stagger (1647s/1800s)') ...sleeping 20 s: (False, 'stagger (1668s/1800s)') ...sleeping 20 s: (False, 'stagger (1689s/1800s)') ...sleeping 20 s: (False, 'stagger (1710s/1800s)') ...sleeping 20 s: (False, 'stagger (1730s/1800s)') ...sleeping 20 s: (False, 'stagger (1751s/1800s)') ...sleeping 20 s: (False, 'stagger (1772s/1800s)') ...sleeping 20 s: (False, 'stagger (1792s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1813s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1834s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1855s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1876s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1897s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1917s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1938s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1959s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1980s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2001s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2022s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2043s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2063s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2084s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2105s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2126s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2147s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2168s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2189s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2209s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2230s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2251s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2272s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2293s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2314s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2334s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2356s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2377s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2397s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2418s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2439s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2460s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2481s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2502s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2522s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2543s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2564s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2585s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2605s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2626s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2648s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2671s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2691s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2712s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2733s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2756s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2780s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2801s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2821s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2843s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2864s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2889s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2910s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2934s/1800s)') ...sleeping 20 s: (False, 'no eligible tempdirs (2958s/1800s)') ...sleeping 20 s: (True, 'Starting plot job: chia plots create -k 32 -r 6 -u 128 -b 3389 -t /plotting2 -d /plots ; logging to /root/.chia/plotman/logs/2021-06-25T09_15_46.524968-04_00.log') ...sleeping 20 s: (False, 'stagger (21s/1800s)') ...sleeping 20 s: (False, 'stagger (42s/1800s)') ...sleeping 20 s: (False, 'stagger (62s/1800s)') ...sleeping 20 s: (False, 'stagger (83s/1800s)') ...sleeping 20 s: (False, 'stagger (104s/1800s)') ...sleeping 20 s: (False, 'stagger (125s/1800s)') ...sleeping 20 s: (False, 'stagger (145s/1800s)') ...sleeping 20 s: (False, 'stagger (166s/1800s)') ...sleeping 20 s: (False, 'stagger (187s/1800s)') ...sleeping 20 s: (False, 'stagger (208s/1800s)') ...sleeping 20 s: (False, 'stagger (229s/1800s)') ...sleeping 20 s: (False, 'stagger (250s/1800s)') ...sleeping 20 s: (False, 'stagger (271s/1800s)') ...sleeping 20 s: (False, 'stagger (292s/1800s)') ...sleeping 20 s: (False, 'stagger (312s/1800s)') ...sleeping 20 s: (False, 'stagger (333s/1800s)') ...sleeping 20 s: (False, 'stagger (354s/1800s)') ...sleeping 20 s: (False, 'stagger (375s/1800s)') ...sleeping 20 s: (False, 'stagger (395s/1800s)') ...sleeping 20 s: (False, 'stagger (416s/1800s)') ...sleeping 20 s: (False, 'stagger (437s/1800s)') ...sleeping 20 s: (False, 'stagger (458s/1800s)') ...sleeping 20 s: (False, 'stagger (478s/1800s)') ...sleeping 20 s: (False, 'stagger (499s/1800s)') ...sleeping 20 s: (False, 'stagger (520s/1800s)') ...sleeping 20 s: (False, 'stagger (540s/1800s)') ...sleeping 20 s: (False, 'stagger (561s/1800s)') ...sleeping 20 s: (False, 'stagger (582s/1800s)') ...sleeping 20 s: (False, 'stagger (603s/1800s)') ...sleeping 20 s: (False, 'stagger (624s/1800s)') ...sleeping 20 s: (False, 'stagger (644s/1800s)') ...sleeping 20 s: (False, 'stagger (665s/1800s)') ...sleeping 20 s: (False, 'stagger (686s/1800s)') ...sleeping 20 s: (False, 'stagger (707s/1800s)') ...sleeping 20 s: (False, 'stagger (727s/1800s)') ...sleeping 20 s: (False, 'stagger (748s/1800s)') ...sleeping 20 s: (False, 'stagger (769s/1800s)') ...sleeping 20 s: (False, 'stagger (790s/1800s)') ...sleeping 20 s: (False, 'stagger (810s/1800s)') ...sleeping 20 s: (False, 'stagger (831s/1800s)') ...sleeping 20 s: (False, 'stagger (852s/1800s)') ...sleeping 20 s: (False, 'stagger (873s/1800s)') ...sleeping 20 s: (False, 'stagger (893s/1800s)') ...sleeping 20 s: (False, 'stagger (914s/1800s)') ...sleeping 20 s: (False, 'stagger (935s/1800s)') ...sleeping 20 s: (False, 'stagger (955s/1800s)') ...sleeping 20 s: (False, 'stagger (976s/1800s)') ...sleeping 20 s: (False, 'stagger (997s/1800s)') ...sleeping 20 s: (False, 'stagger (1017s/1800s)') ...sleeping 20 s: (False, 'stagger (1038s/1800s)') ...sleeping 20 s: (False, 'stagger (1059s/1800s)') ...sleeping 20 s: (False, 'stagger (1080s/1800s)') ...sleeping 20 s: (False, 'stagger (1101s/1800s)') ...sleeping 20 s: (False, 'stagger (1121s/1800s)') ...sleeping 20 s: (False, 'stagger (1142s/1800s)') ...sleeping 20 s: (False, 'stagger (1163s/1800s)') ...sleeping 20 s: (False, 'stagger (1184s/1800s)') ...sleeping 20 s: (False, 'stagger (1204s/1800s)') ...sleeping 20 s: (False, 'stagger (1225s/1800s)') ...sleeping 20 s: (False, 'stagger (1246s/1800s)') ...sleeping 20 s: (False, 'stagger (1267s/1800s)') ...sleeping 20 s: (False, 'stagger (1287s/1800s)') ...sleeping 20 s: (False, 'stagger (1308s/1800s)') ...sleeping 20 s: (False, 'stagger (1329s/1800s)') ...sleeping 20 s: (False, 'stagger (1350s/1800s)') ...sleeping 20 s: (False, 'stagger (1370s/1800s)') ...sleeping 20 s: (False, 'stagger (1391s/1800s)') ...sleeping 20 s: (False, 'stagger (1412s/1800s)') ...sleeping 20 s: (False, 'stagger (1433s/1800s)') ...sleeping 20 s: (False, 'stagger (1453s/1800s)') ...sleeping 20 s: (False, 'stagger (1474s/1800s)') ...sleeping 20 s: (False, 'stagger (1495s/1800s)') ...sleeping 20 s: (False, 'stagger (1516s/1800s)') ...sleeping 20 s: (False, 'stagger (1536s/1800s)') ...sleeping 20 s: (False, 'stagger (1558s/1800s)') ...sleeping 20 s: (False, 'stagger (1579s/1800s)') ...sleeping 20 s: (False, 'stagger (1599s/1800s)') ...sleeping 20 s: (False, 'stagger (1620s/1800s)') ...sleeping 20 s: (False, 'stagger (1642s/1800s)') ...sleeping 20 s: (False, 'stagger (1663s/1800s)') ...sleeping 20 s: (False, 'stagger (1684s/1800s)') ...sleeping 20 s: (False, 'stagger (1704s/1800s)') ...sleeping 20 s: (False, 'stagger (1725s/1800s)') ...sleeping 20 s: (False, 'stagger (1746s/1800s)') ...sleeping 20 s: (False, 'stagger (1769s/1800s)') ...sleeping 20 s: (False, 'stagger (1790s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1811s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1831s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1852s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1873s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1894s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1915s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1935s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1956s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1977s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (1998s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2019s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2039s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2060s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2081s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2102s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2123s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2144s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2165s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2186s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2207s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2228s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2249s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2270s/1800s)') ...sleeping 20 s: (False, 'max jobs (6) - (2290s/1800s)')Terminated Edited June 26, 2021 by Ystebad Quote Link to comment
HATEME Posted June 26, 2021 Share Posted June 26, 2021 (edited) 5 hours ago, Ystebad said: Same exact situation, I try to get madmax running and it fails every time, no matter what setting I change. The Stagger major/minor limits have changed from 4, 0, 1 to 1 , 1, 1. I've changed every setting at least a couple times. Tried the vanilla copy of template, same result. All my temps dir are in one drive because I only have one plotting drive, seperate folders and directories added in docker path as plotting2 and plotting3. Every time i restart, plot setting reverts back with 4 threads, pool/farm key disappear. I have like 30 different .yaml's in my plotman folder from previous settings versions, can't delete any because appdata permissions locked, I'm at a loss, I'm confused. Log says max jobs 6, but that was a setting on my chia yaml, not madmax currently saved. Chia plotter worked at first when I updated docker, till I figured out that have to change Type: chia to Type: madmax EDIT: I just switched setting back and Chia plotter runs fine # 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: 1 # 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: - /plots 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: YOUR_FARMER_PUBLIC_KEY #pool_pk: YOUR_POOL_PUBLIC_KEY # 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: 4 # Default is 4, crank up if you have many cores n_buckets: 256 # Default is 256 ...sleeping 20 s: (False, 'stagger (2326s/3600s)') ...sleeping 20 s: (False, 'stagger (2347s/3600s)') ...sleeping 20 s: (False, 'stagger (2367s/3600s)') ...sleeping 20 s: (False, 'stagger (2389s/3600s)') ...sleeping 20 s: (False, 'stagger (2409s/3600s)') ...sleeping 20 s: (False, 'stagger (2430s/3600s)') ...sleeping 20 s: (False, 'stagger (2451s/3600s)') ...sleeping 20 s: (False, 'stagger (2472s/3600s)') ...sleeping 20 s: (False, 'stagger (2492s/3600s)') ...sleeping 20 s: (False, 'stagger (2513s/3600s)') ...sleeping 20 s: (False, 'stagger (2534s/3600s)') ...sleeping 20 s: (False, 'stagger (2555s/3600s)') ...sleeping 20 s: (False, 'stagger (2576s/3600s)') ...sleeping 20 s: (False, 'stagger (2596s/3600s)') ...sleeping 20 s: (False, 'stagger (2617s/3600s)') ...sleeping 20 s: (False, 'stagger (2638s/3600s)') ...sleeping 20 s: (False, 'stagger (2658s/3600s)') ...sleeping 20 s: (False, 'stagger (2679s/3600s)') ...sleeping 20 s: (False, 'stagger (2700s/3600s)') ...sleeping 20 s: (False, 'stagger (2720s/3600s)') ...sleeping 20 s: (False, 'stagger (2741s/3600s)') ...sleeping 20 s: (False, 'stagger (2762s/3600s)') ...sleeping 20 s: (False, 'stagger (2783s/3600s)') ...sleeping 20 s: (False, 'stagger (2804s/3600s)') ...sleeping 20 s: (False, 'stagger (2825s/3600s)') ...sleeping 20 s: (False, 'stagger (2846s/3600s)') ...sleeping 20 s: (False, 'stagger (2867s/3600s)') ...sleeping 20 s: (False, 'stagger (2888s/3600s)') ...sleeping 20 s: (False, 'stagger (2909s/3600s)') ...sleeping 20 s: (False, 'stagger (2930s/3600s)') ...sleeping 20 s: (False, 'stagger (2951s/3600s)') ...sleeping 20 s: (False, 'stagger (2971s/3600s)') ...sleeping 20 s: (False, 'stagger (2993s/3600s)') ...sleeping 20 s: (False, 'stagger (3014s/3600s)') ...sleeping 20 s: (False, 'stagger (3034s/3600s)') ...sleeping 20 s: (False, 'stagger (3055s/3600s)') ...sleeping 20 s: (False, 'stagger (3076s/3600s)') ...sleeping 20 s: (False, 'stagger (3097s/3600s)') ...sleeping 20 s: (False, 'stagger (3118s/3600s)') ...sleeping 20 s: (False, 'stagger (3139s/3600s)') ...sleeping 20 s: (False, 'stagger (3160s/3600s)') ...sleeping 20 s: (False, 'stagger (3180s/3600s)') ...sleeping 20 s: (False, 'stagger (3201s/3600s)') ...sleeping 20 s: (False, 'stagger (3223s/3600s)') ...sleeping 20 s: (False, 'stagger (3243s/3600s)') ...sleeping 20 s: (False, 'stagger (3264s/3600s)') ...sleeping 20 s: (False, 'stagger (3285s/3600s)') ...sleeping 20 s: (False, 'stagger (3306s/3600s)') ...sleeping 20 s: (False, 'stagger (3327s/3600s)') ...sleeping 20 s: (False, 'stagger (3348s/3600s)') ...sleeping 20 s: (False, 'stagger (3368s/3600s)') ...sleeping 20 s: (False, 'stagger (3389s/3600s)') ...sleeping 20 s: (False, 'stagger (3410s/3600s)') ...sleeping 20 s: (False, 'stagger (3431s/3600s)') ...sleeping 20 s: (False, 'stagger (3451s/3600s)') ...sleeping 20 s: (False, 'stagger (3473s/3600s)') ...sleeping 20 s: (False, 'stagger (3493s/3600s)') ...sleeping 20 s: (False, 'stagger (3514s/3600s)') ...sleeping 20 s: (False, 'stagger (3535s/3600s)') ...sleeping 20 s: (False, 'stagger (3555s/3600s)') ...sleeping 20 s: (False, 'stagger (3576s/3600s)') ...sleeping 20 s: (False, 'stagger (3597s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3618s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3639s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3659s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3680s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3701s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3722s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3743s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3764s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3785s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3806s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3827s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3848s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3869s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3890s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3911s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3932s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3952s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3973s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (3994s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4014s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4036s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4056s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4077s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4098s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4119s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4139s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4160s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4181s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4203s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4224s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4244s/3600s)') ...sleeping 20 s: (False, 'max jobs (6) - (4265s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4286s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4307s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4328s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4349s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4369s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4390s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4411s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4432s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4452s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4473s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4494s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4515s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4535s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4556s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4576s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4597s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4618s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4638s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4659s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4679s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4700s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4720s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4741s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4762s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4783s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4803s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4824s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4845s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4865s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4887s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4908s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4928s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4949s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4969s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (4990s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5010s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5030s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5051s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5072s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5092s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5113s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5135s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5155s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5175s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5196s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5216s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5237s/3600s)') ...sleeping 20 s: (False, 'no eligible tempdirs (5257s/3600s)') ...sleeping 20 s: (True, 'Starting plot job: chia plots create -k 32 -r 6 -u 128 -b 3408 -t /plotting -d /plots ; logging to /root/.chia/plotman/logs/2021-06-25T22_31_53.587360-04_00.log') ...sleeping 20 s: (False, 'stagger (21s/3600s)') ...sleeping 20 s: (False, 'stagger (42s/3600s)') ...sleeping 20 s: (False, 'stagger (62s/3600s)') ...sleeping 20 s: (False, 'stagger (83s/3600s)') ...sleeping 20 s: (False, 'stagger (104s/3600s)') ...sleeping 20 s: (False, 'stagger (125s/3600s)') ...sleeping 20 s: (False, 'stagger (146s/3600s)') ...sleeping 20 s: (False, 'stagger (166s/3600s)') ...sleeping 20 s: (False, 'stagger (187s/3600s)') ...sleeping 20 s: (False, 'stagger (208s/3600s)') ...sleeping 20 s: (False, 'stagger (229s/3600s)') ...sleeping 20 s: (False, 'stagger (250s/3600s)') ...sleeping 20 s: (False, 'stagger (270s/3600s)') ...sleeping 20 s: (False, 'stagger (291s/3600s)') ...sleeping 20 s: (False, 'stagger (312s/3600s)') ...sleeping 20 s: (False, 'stagger (332s/3600s)') ...sleeping 20 s: (False, 'stagger (354s/3600s)') ...sleeping 20 s: (False, 'stagger (375s/3600s)') ...sleeping 20 s: (False, 'stagger (396s/3600s)') ...sleeping 20 s: (False, 'stagger (417s/3600s)') ...sleeping 20 s: (False, 'stagger (438s/3600s)') ...sleeping 20 s: (False, 'stagger (459s/3600s)') ...sleeping 20 s: (False, 'stagger (480s/3600s)') ...sleeping 20 s: (False, 'stagger (501s/3600s)') ...sleeping 20 s: (False, 'stagger (522s/3600s)') ...sleeping 20 s: (False, 'stagger (542s/3600s)') ...sleeping 20 s: (False, 'stagger (563s/3600s)') ...sleeping 20 s: (False, 'stagger (584s/3600s)') ...sleeping 20 s: (False, 'stagger (605s/3600s)') ...sleeping 20 s: (False, 'stagger (626s/3600s)') ...sleeping 20 s: (False, 'stagger (647s/3600s)') ...sleeping 20 s: (False, 'stagger (668s/3600s)') ...sleeping 20 s: (False, 'stagger (689s/3600s)') ...sleeping 20 s: (False, 'stagger (710s/3600s)') ...sleeping 20 s: (False, 'stagger (731s/3600s)') ...sleeping 20 s: (False, 'stagger (751s/3600s)') ...sleeping 20 s: (False, 'stagger (772s/3600s)') ...sleeping 20 s: (False, 'stagger (793s/3600s)') ...sleeping 20 s: (False, 'stagger (824s/3600s)') ...sleeping 20 s: (False, 'stagger (845s/3600s)') ...sleeping 20 s: (False, 'stagger (866s/3600s)') ...sleeping 20 s: (False, 'stagger (886s/3600s)') ...sleeping 20 s: (False, 'stagger (907s/3600s)') ...sleeping 20 s: (False, 'stagger (928s/3600s)') ...sleeping 20 s: (False, 'stagger (948s/3600s)') ...sleeping 20 s: (False, 'stagger (969s/3600s)') ...sleeping 20 s: (False, 'stagger (990s/3600s)') ...sleeping 20 s: (False, 'stagger (1010s/3600s)') ...sleeping 20 s: (False, 'stagger (1031s/3600s)') ...sleeping 20 s: (False, 'stagger (1052s/3600s)') ...sleeping 20 s: (False, 'stagger (1073s/3600s)') ...sleeping 20 s: (False, 'stagger (1094s/3600s)') ...sleeping 20 s: (False, 'stagger (1115s/3600s)') ...sleeping 20 s: (False, 'stagger (1136s/3600s)') ...sleeping 20 s: (False, 'stagger (1157s/3600s)') ...sleeping 20 s: (False, 'stagger (1178s/3600s)') ...sleeping 20 s: (False, 'stagger (1199s/3600s)') ...sleeping 20 s: (False, 'stagger (1219s/3600s)') ...sleeping 20 s: (False, 'stagger (1240s/3600s)') ...sleeping 20 s: (False, 'stagger (1261s/3600s)') ...sleeping 20 s: (False, 'stagger (1282s/3600s)') ...sleeping 20 s: (False, 'stagger (1303s/3600s)') ...sleeping 20 s: (False, 'stagger (1324s/3600s)') ...sleeping 20 s: (False, 'stagger (1345s/3600s)') ...sleeping 20 s: (False, 'stagger (1365s/3600s)') ...sleeping 20 s: (False, 'stagger (1386s/3600s)') ...sleeping 20 s: (False, 'stagger (1407s/3600s)') ...sleeping 20 s: (False, 'stagger (1428s/3600s)') ...sleeping 20 s: (False, 'stagger (1450s/3600s)') ...sleeping 20 s: (False, 'stagger (1471s/3600s)') ...sleeping 20 s: (False, 'stagger (1491s/3600s)') ...sleeping 20 s: (False, 'stagger (1512s/3600s)') ...sleeping 20 s: (False, 'stagger (1533s/3600s)') ...sleeping 20 s: (False, 'stagger (1554s/3600s)') ...sleeping 20 s: (False, 'stagger (1574s/3600s)') ...sleeping 20 s: (False, 'stagger (1595s/3600s)') ...sleeping 20 s: (False, 'stagger (1616s/3600s)') ...sleeping 20 s: (False, 'stagger (1637s/3600s)') ...sleeping 20 s: (False, 'stagger (1658s/3600s)') ...sleeping 20 s: (False, 'stagger (1679s/3600s)') ...sleeping 20 s: (False, 'stagger (1699s/3600s)') ...sleeping 20 s: (False, 'stagger (1720s/3600s)') ...sleeping 20 s: (False, 'stagger (1741s/3600s)') ...sleeping 20 s: (False, 'stagger (1761s/3600s)') ...sleeping 20 s: (False, 'stagger (1782s/3600s)') ...sleeping 20 s: (False, 'stagger (1803s/3600s)') ...sleeping 20 s: (False, 'stagger (1823s/3600s)') ...sleeping 20 s: (False, 'stagger (1844s/3600s)') ...sleeping 20 s: (False, 'stagger (1865s/3600s)') ...sleeping 20 s: (False, 'stagger (1886s/3600s)') ...sleeping 20 s: (False, 'stagger (1906s/3600s)') ...sleeping 20 s: (False, 'stagger (1927s/3600s)') ...sleeping 20 s: (False, 'stagger (1948s/3600s)') ...sleeping 20 s: (False, 'stagger (1968s/3600s)') ...sleeping 20 s: (False, 'stagger (1989s/3600s)') ...sleeping 20 s: (False, 'stagger (2010s/3600s)') ...sleeping 20 s: (False, 'stagger (2030s/3600s)') ...sleeping 20 s: (False, 'stagger (2051s/3600s)')Terminated md='suspend', idprefix=['606d65f4']) Suspending 606d65f46e408b3803445b09efafd547544fb3bd50d6bc309c7ba709e5e58a73 nohup: ignoring input Namespace(cmd='kill', idprefix=['b3cea3e4']) Pausing PID 3868, plot id b3cea3e4f35781f37dc6962171e9dc2d39cb407dc8c12e5cb4d714ce54d83b13 Will kill pid 3868, plot id b3cea3e4f35781f37dc6962171e9dc2d39cb407dc8c12e5cb4d714ce54d83b13 Will delete 137 temp files Are you sure? ("y" to confirm): killing... cleaning up temp files... Edited June 26, 2021 by HATEME Quote Link to comment
Spazhead Posted June 26, 2021 Share Posted June 26, 2021 (edited) working great so far, I created a ramdisk to use as '-2' tmp drive here are the command lines i use in unraid terminal mkdir /mnt/ram mount -t tmpfs -o size=110G tmpfs /mnt/ram/ to remove ramdisk later, make sure it's empty rm -f -R /mnt/ram/*.* umount -f /mnt/ram rmdir /mnt/ram make sure to add the ramdisk (/mnt/ram) to your settings in machinaris docker here is what mine looks like, here is my plotter settings, I highlighted the only things i changed in YELLOW ----------------------------------------------------------------------------------------------- # 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: - /plotting1 # 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, /mnt/tmp/00 is larger than the other tmp # dirs and it can hold more plots than the default. #\\\\\\\\\\\\\\\"/mnt/tmp/00\\\\\\\\\\\\\\\": #tmpdir_max_jobs: 5 # Optional: tmp2 directory. If specified, will be passed to # chia plots create as -2. Only one tmp2 directory is supported. tmp2: /ram # 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: - /plots 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: 3 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: 60 # 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: <PUT YOUR KEYS> pool_pk: <PUT YOUR KEYS> # 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: 12 # Default is 4, crank up if you have many cores n_buckets: 256 # Default is 256 farmer_pk: <PUT YOUR KEYS> pool_pk: <PUT YOUR KEYS> ---------------------------------------------------------------------------------------------------------------------------------------- these are the times I'm getting from my log, DELL R610 Dual Xeon X5675, 192 GB Ram is only 800 mhz speed (12 threads) (24 threads) looks like 12 threads will do 1 plot/2hrs approx and 24 threads will do 1 plot/hr approx Stay safe Edited June 27, 2021 by Spazhead 1 Quote Link to comment
Spazhead Posted June 26, 2021 Share Posted June 26, 2021 (12 threads) Total plot creation time was 6534.52 sec (108.909 min) (24 threads) Total plot creation time was 3947.82 sec (65.797 min) 1 Quote Link to comment
guy.davis Posted June 26, 2021 Author Share Posted June 26, 2021 (edited) 11 hours ago, Ystebad said: Downloaded new version and trying to use the new madmax. I think I changed my config for plotting as per recommendation but each time I try to start it it says "starting" then "plotman started successfully" but no cores being used and nothing showing up in plotting as ongoing and it says "idle" at the top. My config: # Learn more about Plotman at https://github.com/ericaltendorf/plotman # https://github.com/ericaltendorf/plotman/wiki/Configuration#versions version: [1] Apologies to @Ystebad and @HATEME for encountering this error in the documentation on my part. The version line of the Madmax-enabled plotman.yaml should be: version: [2] This was incorrectly left at '1' in the Wiki doc example. I have just now corrected it. Please try with that setting. Just be sure to set your Farmer and Pool public keys. Sorry for the trouble and thanks for reporting it! Edited June 26, 2021 by guy.davis 1 Quote Link to comment
guy.davis Posted June 26, 2021 Author Share Posted June 26, 2021 1 hour ago, Spazhead said: # Configure the plotter. See: https://github.com/guydavis/machinaris/wiki/Plotman#plotting plotting: farmer_pk: <PUT YOUR KEYS> pool_pk: <PUT YOUR KEYS> # 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: 12 # Default is 4, crank up if you have many cores n_buckets: 256 # Default is 256 farmer_pk: <PUT YOUR KEYS> pool_pk: <PUT YOUR KEYS>- Nice numbers! Plotting to RAM on Unraid is really effective with Madmax. Thanks for helping above as it showed me the error in my plotman.yaml example. Btw, my plotman migrate script looks to have left a double entry in your plotman.yaml above. You only need one pair of 'farmer_pk' and 'pool_pk' lines. Safe to remove the bottom redundant pair. Thanks again for the assistance! Quote Link to comment
HATEME Posted June 26, 2021 Share Posted June 26, 2021 (edited) I got mad max working, my 3700x unraid rig is getting 69min plot time, not sure what my dual xeon rig is yet, but phase 1 is 40min alone, so...better than parallel, but its showing it's age. Is there way to have the finished plot transfer outside of the max job queue. After first plot finished, I know from my main pc running mad max that a transferred plot takes an extra 15-20 min, first madmax just used an extra powershell mover.ps1, but now its integrated together and mover runs in background and starts the next plot. Machinaris stops the queue to wait on moving the finished plot. Could set two max jobs and set stagger to 69 min, but I got a feeling over 10 or 20 plots, those times would vary enough to overlap and make the cpu go nuclear, then cause a meltdown in the cores. EDIT: plot transfer added 26 min to my 69min plot times, maybe global max jobs 2, but temp dir max jobs 1, I'm just using one nvme drive as temp drive. and 2nd temp dir just points to same drive. Edited June 26, 2021 by HATEME Quote Link to comment
ryanhaver Posted June 26, 2021 Share Posted June 26, 2021 (edited) I'm actually seeing Unraid not be able to deal with plotting in RAM, although I am using /tmp not a dedicated ram disk. This may be more related to madmax than anything else. I'm currently testing different settings to see if I can get madmax working reliably. @Spazhead is there any reason you don't use /tmp instead of creating and actual ram disk? Edited June 26, 2021 by ryanhaver Quote Link to comment
ryanhaver Posted June 27, 2021 Share Posted June 27, 2021 It looks like Unraid gets grumpy when ram usage inside /tmp reaches half of the overall system memory. So I'm just going to add the mounting of the tmpfs to my go file so it will be automatically mounted during boot. Quote Link to comment
Spazhead Posted June 27, 2021 Share Posted June 27, 2021 3 hours ago, ryanhaver said: I'm actually seeing Unraid not be able to deal with plotting in RAM, although I am using /tmp not a dedicated ram disk. This may be more related to madmax than anything else. I'm currently testing different settings to see if I can get madmax working reliably. @Spazhead is there any reason you don't use /tmp instead of creating and actual ram disk? yes because when i just used /tmp, it would crash on me, until i found that creating a dedicated ramdisk was more stable. just trial and error testing. Quote Link to comment
cjizzle Posted June 27, 2021 Share Posted June 27, 2021 5 hours ago, ryanhaver said: It looks like Unraid gets grumpy when ram usage inside /tmp reaches half of the overall system memory. So I'm just going to add the mounting of the tmpfs to my go file so it will be automatically mounted during boot. Very excited to use Machinaris for mad max plotting, used it before when parallel plotting. Only thing I am waiting for is the -v variable being implemented (maybe it has been I just haven't seen it) In the meantime I've been using Ubuntu Playground. I am assuming most of the steps are (or will be) the same so here it goes: Real quick system specs: Dell R720, 2x Xeon 12/24, 128GB ram ddr3 1866, 1TB cache nvme, 2TB Chia nvme To create ramdrive: On boot before launching playground or mach or whatever open terminal and use this (plotram is my ramdrive name): mkdir -p /tmp/plotram && mount -t tmpfs -o size=115g tmpfs /tmp/plotram Edit container and add path: ramdrive /plotram /tmp/plotram/ Make sure your paths are set up correctly for chia specific nvme plotting, final plot location, etc. Profit! In Ubuntu Playground without -v variable I was getting 30-33 minute plots (512 buckets default). Now with -v, using 32 threads, 256 buckets for Ph 1+2 and 128 buckets for Ph 3+4 I'm getting 27 minute plots consistently. Here's what I copy and paste into ubuntu playground: ./build/chia_plot -t /plotting1/ -2 /plotram/ -d /plots/ -k 32 -u 256 -r 32 -v 128 -n 300 -f FARMERKEY -p POOLKEY 128GB is plenty in Unraid as long as you dont have a bunch of other crap running. Been plotting away with no errors for days now. Also (in Ubuntu anyways) theres no wait after a plot is done to start a new one, the finished plot transfers to final location while the next plot is churning away, typically finishes somewhere later in Phase 1. I may have missed it, but does this new Machinaris behave the same? And any -v possibilities? Quote Link to comment
Spazhead Posted June 27, 2021 Share Posted June 27, 2021 (edited) Plotting complete for me, one month to complete 1181 plots on existing old hard drives. 90% of these drives have CRC & Bad sectors on them so i don't trust them for real data, but for chia i don't care if it fails. lets earn some Chia hopefully.. Note: Disk 1 is for surveillance only, no chia Thanks Machinaris for making it easier!!!! Edited June 27, 2021 by Spazhead 2 Quote Link to comment
Rav20 Posted June 27, 2021 Share Posted June 27, 2021 Seeking plots took too long: 181.45854 seconds! i keep getting the above error, between 65-600+ seconds yet. when im watching the summary screen i see everything under 1 second. HDD's dont spin down, local on the array not network or anything. any advice for tracing down the problem? Quote Link to comment
Helmonder Posted June 28, 2021 Share Posted June 28, 2021 (edited) Hi, I wanted to try the MADMAX plotting, so I killed my current plots (only just started), removed all temp files, changed the config and am trying to start plotting again.. However the system does not start plotting and the plotting screen shows some confusing information... It says its plotting, but Tower is stopped (I only have 1 system) and the plots that I previouslyt killed are still in the list: Any idea? I switched back to the chia plotter, that works fine. Edited June 28, 2021 by Helmonder Quote Link to comment
Helmonder Posted June 28, 2021 Share Posted June 28, 2021 (edited) Think I found why madmax was not working... Will try again -after- I have read the instructions :-) (EDIT: In the meantime MADMAX is now plotting) Still think something is going on with the plotting screen though... After starting chia plotting again I now: stopped plotting killed the running plot The files are still in the temp folder and the screen still shows the old plot: Edited June 28, 2021 by Helmonder Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.