Problems starting swar manager after installing

After installing python latest version and doing the guide i have no clue what this errors should tell me, do you have an idea ?

PS C:\users\tom29\swar> python manager.py start
Traceback (most recent call last):
  File "C:\users\tom29\swar\manager.py", line 29, in <module>
    start_manager()
  File "C:\users\tom29\swar\plotmanager\library\utilities\commands.py", line 32, in start_manager
    notification_settings, debug_level, view_settings = get_config_info()
  File "C:\users\tom29\swar\plotmanager\library\parse\configuration.py", line 102, in get_config_info
    config = _get_config()
  File "C:\users\tom29\swar\plotmanager\library\parse\configuration.py", line 16, in _get_config
    config = yaml.load(stream=f, Loader=yaml.Loader)
  File "C:\Program Files\Python39\lib\site-packages\yaml\__init__.py", line 114, in load
    return loader.get_single_data()
  File "C:\Program Files\Python39\lib\site-packages\yaml\constructor.py", line 49, in get_single_data
    node = self.get_single_node()
  File "C:\Program Files\Python39\lib\site-packages\yaml\composer.py", line 36, in get_single_node
    document = self.compose_document()
  File "C:\Program Files\Python39\lib\site-packages\yaml\composer.py", line 55, in compose_document
    node = self.compose_node(None, None)
  File "C:\Program Files\Python39\lib\site-packages\yaml\composer.py", line 84, in compose_node
    node = self.compose_mapping_node(anchor)
  File "C:\Program Files\Python39\lib\site-packages\yaml\composer.py", line 127, in compose_mapping_node
    while not self.check_event(MappingEndEvent):
  File "C:\Program Files\Python39\lib\site-packages\yaml\parser.py", line 98, in check_event
    self.current_event = self.state()
  File "C:\Program Files\Python39\lib\site-packages\yaml\parser.py", line 438, in parse_block_mapping_key
    raise ParserError("while parsing a block mapping", self.marks[-1],
yaml.parser.ParserError: while parsing a block mapping
  in "C:\Users\tom29\Swar\config.yaml", line 6, column 1
expected <block end>, but found '-'
  in "C:\Users\tom29\Swar\config.yaml", line 154, column 1
PS C:\users\tom29\swar>
1 Like

Looks like something is wrong in your config file, incorrect YAML formatting.

You can check it on yamllint.com. If something is wrong, better start over from the default and make sure the file format doesn’t change

1 Like

Yes, YAML is very particular about formatting. Don’t use just a general editor like notepad. It will add spaces in spots that YAML will have a cow about. I normally use notepad++ to edit my YAML files and have had no issues.

i tried both suggestions nothing changes…

It is definitely your YAML file. Delete your config file and make a fresh copy of the example conifg. Then load notepad++. Open the new config in notepad++ and make your changes. Make sure not to add any spaces or line breaks. Just edit the numbers and fields that need changed. Save it and try again.

What did the yamllint.com check say?

yamillint check was ok, erstellt mit notepad ++, aber es startet immer noch nicht…

C:\Users\tom29\Swar-Chia-Plot-Manager-main>python manager.py view
Traceback (most recent call last):
  File "C:\Users\tom29\Swar-Chia-Plot-Manager-main\manager.py", line 36, in <module>
    view()
  File "C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\utilities\commands.py", line 74, in view
    notification_settings, debug_level, view_settings = get_config_info()
  File "C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py", line 102, in get_config_info
    config = _get_config()
  File "C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py", line 16, in _get_config
    config = yaml.load(stream=f, Loader=yaml.Loader)
  File "C:\Program Files\Python39\lib\site-packages\yaml\__init__.py", line 114, in load
    return loader.get_single_data()
  File "C:\Program Files\Python39\lib\site-packages\yaml\constructor.py", line 49, in get_single_data
    node = self.get_single_node()
  File "C:\Program Files\Python39\lib\site-packages\yaml\composer.py", line 39, in get_single_node
    if not self.check_event(StreamEndEvent):
  File "C:\Program Files\Python39\lib\site-packages\yaml\parser.py", line 98, in check_event
    self.current_event = self.state()
  File "C:\Program Files\Python39\lib\site-packages\yaml\parser.py", line 171, in parse_document_start
    raise ParserError(None, None,
yaml.parser.ParserError: expected '<document start>', but found '<block mapping start>'
  in "C:\Users\tom29\Swar-Chia-Plot-Manager-main\config.yaml", line 10, column 1

C:\Users\tom29\Swar-Chia-Plot-Manager-main>python manager.py stop
No manager processes were found.

Do you get the same errors (when you run start) with the new config file? The above errors are from “view” then “stop”.

C:>cd C:\Users\tom29\Swar-Chia-Plot-Manager-main

C:\Users\tom29\Swar-Chia-Plot-Manager-main>python manager.py start
Traceback (most recent call last):
File “C:\Users\tom29\Swar-Chia-Plot-Manager-main\manager.py”, line 29, in
start_manager()
File “C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\utilities\commands.py”, line 32, in start_manager
notification_settings, debug_level, view_settings = get_config_info()
File “C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py”, line 102, in get_config_info
config = _get_config()
File “C:\Users\tom29\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py”, line 16, in get_config
config = yaml.load(stream=f, Loader=yaml.Loader)
File "C:\Program Files\Python39\lib\site-packages\yaml_init
.py", line 114, in load
return loader.get_single_data()
File “C:\Program Files\Python39\lib\site-packages\yaml\constructor.py”, line 49, in get_single_data
node = self.get_single_node()
File “C:\Program Files\Python39\lib\site-packages\yaml\composer.py”, line 39, in get_single_node
if not self.check_event(StreamEndEvent):
File “C:\Program Files\Python39\lib\site-packages\yaml\parser.py”, line 98, in check_event
self.current_event = self.state()
File “C:\Program Files\Python39\lib\site-packages\yaml\parser.py”, line 171, in parse_document_start
raise ParserError(None, None,
yaml.parser.ParserError: expected ‘’, but found ‘’
in “C:\Users\tom29\Swar-Chia-Plot-Manager-main\config.yaml”, line 10, column 1

C:\Users\tom29\Swar-Chia-Plot-Manager-main>

# 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\tom29\AppData\Local\chia-blockchain\app-1.1.5\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: I:\Chia Final\Chia\Logs\Plotter


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: 

  # 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: Viper4100 2TB
    max_plots: 999 
    farmer_public_key:  
    pool_public_key: 
    temporary_directory: G:\Chiaplot
    temporary2_directory: C:\chiaplot
    destination_directory: I:\Chia Final
    size: 32
    bitfield: true
    threads: 6
    buckets: 128
    memory_buffer: 3800
    max_concurrent: 10
    max_concurrent_with_start_early: 11
    stagger_minutes: 60
    max_for_phase_1: 4
    concurrency_start_early_phase: 4
    concurrency_start_early_phase_delay: 0
    temporary2_destination_sync: false

  - name: SSD Crucial 1TB
    max_plots: 999
    farmer_public_key:  
    pool_public_key: 
    temporary_directory: H:\Chiaplot
    temporary2_directory: C:\chiaplot
    destination_directory: I:\Chia Final
    size: 32
    bitfield: true
    threads: 4
    buckets: 128
    memory_buffer: 3800
    max_concurrent: 2
    max_concurrent_with_start_early: 3
    stagger_minutes: 150
    max_for_phase_1: 4
    concurrency_start_early_phase: 4
    concurrency_start_early_phase_delay: 0
    temporary2_destination_sync: false

Just a guess, try removing the spaces from your job names. And maybe even the space in the folder name of your destination directory.

that is only shown in that copy/paste there are no spaces between the named folders

temporäres_Verzeichnis: H:\Chiaplot
temporäres2_Verzeichnis: C:\chiaplot
Zielverzeichnis: I:\Chia Final

wohooooo
i just deleted the two spaces in front of line chia_location… :

chia_location: C: \ Benutzer \ tom29 \ AppData \ Local \ chia-blockchain \ app-1.1.5 \ resources \ app.asar.unpacked \ daemon \ chia.exe

and tried to start now it is runnig… but i tried this several times before…
now its running

=========================================================================================================================
num         job          k      pid           start          elapsed_time   phase   phase_times   progress   temp_size
=========================================================================================================================
1     ?                 None   19620   2021-05-18 20:25:11   00:11:17       1                     3.29%      0 GiB
2     ?                 None   2836    2021-05-18 20:26:15   00:10:13       1                     2.67%      0 GiB
3     Viper4100 2TB     32     12864   2021-05-18 20:35:02   00:01:26       1                     0.58%      18 GiB
4     SSD Crucial 1TB   32     10808   2021-05-18 20:35:03   00:01:26       1                     0.58%      18 GiB
=========================================================================================================================
Manager Status: Running

=======================================================
 type   drive     used     total     percent   plots
=======================================================
temp    G:      0.08TiB   1.82TiB    4.3%      1
temp    H:      0.37TiB   0.91TiB    40.3%     1
temp2   C:      0.16TiB   0.91TiB    17.7%     2
dest    I:      0.00TiB   12.73TiB   0.0%      2
=======================================================
CPU Usage: 30.7%
RAM Usage: 14.89/31.93GiB(46.6%)

Plots Completed Yesterday: 0
Plots Completed Today: 0

Next log check at 2021-05-18 20:37:29

I was talking about the spaces in the actual name, not before or after the line. But I’m happy you found the issue. This had to have been something you added by mistake. The example config has worked every time for me.

i just started gui and new plots and tried further to start swar manager but i tried without this spaces before with no success. but the tip with the notepad ++ was good and the yamil check also.
thx to all for your help hopefully others will help this threat also.

Good to hear, just wanted to add forfuture reference.

If i use “ssd1” as job name = error

But “ssd 1” is fine

how to fix

PS C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main> python manager.py start
Traceback (most recent call last):
  File "C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main\manager.py", line 30, in <module>
    start_manager()
  File "C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main\plotmanager\library\utilities\commands.py", line 35, in start_manager
    instrumentation_settings = get_config_info()
  File "C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py", line 145, in get_config_info
    max_concurrent, max_for_phase_1, minimum_minutes_between_jobs = _get_global_config(config=config)
  File "C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py", line 62, in _get_global_config
    _check_parameters(parameter=global_config, expected_parameters=expected_parameters, parameter_type='global')
  File "C:\Users\hakva\OneDrive\Desktop\Swar-Chia-Plot-Manager-main\plotmanager\library\parse\configuration.py", line 133, in _check_parameters
    raise InvalidYAMLConfigException(f'Failed to find the following {parameter_type} parameters: '
plotmanager.library.utilities.exceptions.InvalidYAMLConfigException: Failed to find the following global parameters: max_for_phase_1, minimum_minutes_between_jobs

Start over by copying from the default template file.

And this time don’t delete any values.
It is saying you deleted two values from the config that you need to run the program.

(or fix the existing config file by adding them back in the right place again)