How can I solve this problem?

[maxren12645]

PS C:\PlotManager> python manager.py start
Traceback (most recent call last):
File "C:\PlotManager\manager.py", line 29, in
start_manager()
File "C:\PlotManager\plotmanager\library\utilities\commands.py", line 32, in start_manager
notification_settings, debug_level, view_settings = get_config_info()
File "C:\PlotManager\plotmanager\library\parse\configuration.py", line 102, in get_config_info
config = _get_config()
File "C:\PlotManager\plotmanager\library\parse\configuration.py", line 16, in get_config
config = yaml.load(stream=f, Loader=yaml.Loader)
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml_init.py", line 114, in load
return loader.get_single_data()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\constructor.py", line 49, in get_single_data
node = self.get_single_node()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 36, in get_single_node
document = self.compose_document()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 55, in compose_document
node = self.compose_node(None, None)
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 84, in compose_node
node = self.compose_mapping_node(anchor)
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 133, in compose_mapping_node
item_value = self.compose_node(node, item_key)
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 84, in compose_node
node = self.compose_mapping_node(anchor)
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\composer.py", line 127, in compose_mapping_node
while not self.check_event(MappingEndEvent):
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\parser.py", line 98, in check_event
self.current_event = self.state()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\parser.py", line 428, in parse_block_mapping_key
if self.check_token(KeyToken):
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\scanner.py", line 116, in check_token
self.fetch_more_tokens()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\scanner.py", line 223, in fetch_more_tokens
return self.fetch_value()
File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\yaml\scanner.py", line 577, in fetch_value
raise ScannerError(None, None,
yaml.scanner.ScannerError: mapping values are not allowed here
in "C:\PlotManager\config.yaml", line 20, column 17
PS C:\PlotManager>

[RyanWarwick]

Sounds like an issue with the YAML formatting in your config.yaml. Need to take a look at it.

[maxren12645]

This is a single variable that should contain the location of your chia executable file. This is the blockchain executable.

WINDOWS EXAMPLE: C:\Users\Swar\AppData\Local\chia-blockchain\app-1.1.5\resources\app.asar.unpacked\daemon\chia.exe

LINUX EXAMPLE: /usr/lib/chia-blockchain/resources/app.asar.unpacked/daemon/chia

LINUX2 EXAMPLE: /home/swar/chia-blockchain/venv/bin/chia

chia_location: C:\Users\user\AppData\Local\chia-blockchain\app-1.1.3\resources\app.asar.unpacked\daemon\chia.exe

manager:

These are the config settings that will only be used by the plot manager.

check_interval: The number of seconds to wait before checking to see if a new job should start.

log_level: Keep this on ERROR to only record when there are errors. Change this to INFO in order to see more

detailed logging. Warning: INFO will write a lot of information.

check_interval: 60
log_level: ERROR

log:

folder_path: This is the folder where your log files for plots will be saved.

folder_path: C:

view:

These are the settings that will be used by the view.

check_interval: The number of seconds to wait before updating the view.

datetime_format: The datetime format that you want displayed in the view. See here

for formatting: https://docs.python.org/3/library/datetime.html#strftime-and-strptime-format-codes

include_seconds_for_phase: This dictates whether seconds are included in the phase times.

include_drive_info: This dictates whether the drive information will be showed.

include_cpu: This dictates whether the CPU information will be showed.

include_ram: This dictates whether the RAM information will be showed.

include_plot_stats: This dictates whether the plot stats will be showed.

check_interval: 60
datetime_format: "%Y-%m-%d %H:%M:%S"
include_seconds_for_phase: false
include_drive_info: true
include_cpu: true
include_ram: true
include_plot_stats: true

notifications:

These are different settings in order to notified when the plot manager starts and when a plot has been completed.

DISCORD

notify_discord: false
discord_webhook_url: https://discord.com/api/webhooks/0000000000000000/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

PLAY AUDIO SOUND

notify_sound: false
song: audio.mp3

PUSHOVER PUSH SERVICE

notify_pushover: false
pushover_user_key: xx
pushover_api_key: xx

TWILIO

notify_twilio: false
twilio_account_sid: xxxxx
twilio_auth_token: xxxxx
twilio_from_phone: +1234657890
twilio_to_phone: +1234657890

progress:

phase_line_end: These are the settings that will be used to dictate when a phase ends in the progress bar. It is

supposed to reflect the line at which the phase will end so the progress calculations can use that

information with the existing log file to calculate a progress percent.

phase_weight: These are the weight to assign to each phase in the progress calculations. Typically, Phase 1 and 3

are the longest phases so they will hold more weight than the others.

phase1_line_end: 801
phase2_line_end: 834
phase3_line_end: 2474
phase4_line_end: 2620
phase1_weight: 33.4
phase2_weight: 20.43
phase3_weight: 42.29
phase4_weight: 3.88

global:

These are the settings that will be used globally by the plot manager.

max_concurrent: The maximum number of plots that your system can run. The manager will not kick off more than this

number of plots total over time.

max_concurrent: 10

jobs:

These are the settings that will be used by each job. Please note you can have multiple jobs and each job should be

in YAML format in order for it to be interpreted correctly. Almost all the values here will be passed into the

Chia executable file.

Check for more details on the Chia CLI here: https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference

name: This is the name that you want to give to the job.

max_plots: This is the maximum number of jobs to make in one run of the manager. Any restarts to manager will reset

this variable. It is only here to help with short term plotting.

[OPTIONAL] farmer_public_key: Your farmer public key. If none is provided, it will not pass in this variable to the

chia executable which results in your default keys being used. This is only needed if

you have chia set up on a machine that does not have your credentials.

[OPTIONAL] pool_public_key: Your pool public key. Same information as the above.

temporary_directory: Only a single directory should be passed into here. This is where the plotting will take place.

[OPTIONAL] temporary2_directory: Can be a single value or a list of values. This is an optional parameter to use in

case you want to use the temporary2 directory functionality of Chia plotting.

destination_directory: Can be a single value or a list of values. This is the final directory where the plot will be

transferred once it is completed. If you provide a list, it will cycle through each drive

one by one.

size: This refers to the k size of the plot. You would type in something like 32, 33, 34, 35... in here.

bitfield: This refers to whether you want to use bitfield or not in your plotting. Typically, you want to keep

this as true.

threads: This is the number of threads that will be assigned to the plotter. Only phase 1 uses more than 1 thread.

buckets: The number of buckets to use. The default provided by Chia is 128.

memory_buffer: The amount of memory you want to allocate to the process.

max_concurrent: The maximum number of plots to have for this job at any given time.

max_concurrent_with_start_early: The maximum number of plots to have for this job at any given time including

phases that started early.

stagger_minutes: The amount of minutes to wait before the next job can get kicked off. You can even set this to

zero if you want your plots to get kicked off immediately when the concurrent limits allow for it.

max_for_phase_1: The maximum number of plots on phase 1 for this job.

concurrency_start_early_phase: The phase in which you want to start a plot early. It is recommended to use 4 for

this field.

concurrency_start_early_phase_delay: The maximum number of minutes to wait before a new plot gets kicked off when

the start early phase has been detected.

temporary2_destination_sync: This field will always submit the destination directory as the temporary2 directory.

These two directories will be in sync so that they will always be submitted as the

same value.

• name: micron
  max_plots: 999
  farmer_public_key:
  pool_public_key:
  temporary_directory: F:\Plotter
  temporary2_directory:
  destination_directory: F:\Plots
  size: 32
  bitfield: true
  threads: 8
  buckets: 128
  memory_buffer: 4000
  max_concurrent: 6
  max_concurrent_with_start_early: 7
  stagger_minutes: 60
  max_for_phase_1: 2
  concurrency_start_early_phase: 4
  concurrency_start_early_phase_delay: 0
  temporary2_destination_sync: false

听起来像config.yaml中的YAML格式有问题。需要看看它。

[RyanWarwick]

Ouch my eyes. Anyway i think its folder_path. The value cannot be "C:" due to how YAML works. YAML uses ':' symbol to do mapping, so it doesn't read it as a path (C:) and instead reads it as literal YAML.

Try changing folder_path: C: to folder_path: C:\ or "C:"