BUSCO 5.2.1 starts,stops and relaunches repeatedly

BUSCO starts, crashes, and restarts repeatedly it eventually spits out the error below while still trying to start again and using -f or --restart help it down different paths of perpetual errors

Here is my command line: busco -i mainGenome.fasta -l poales_odb10/ -o r3.genome -m genome --augustus_species Sorghum_bicolor --long --augustus --config /usr/bin/busco/config/config.ini --offline --augustus_parameters='--progress=true' -c 16

Here are two different bits of errors that were output: 2021-07-12 13:47:04 INFO: ***** Start a BUSCO v5.2.1 analysis, current time: 07/12/2021 13:47:04 ***** 2021-07-12 13:47:04 INFO: Configuring BUSCO with /bioinfo/installs/busco/config/config.ini 2021-07-12 13:47:04 INFO: Mode is genome 2021-07-12 13:47:04 INFO: Downloading information on latest versions of BUSCO data... 2021-07-12 13:47:05 INFO: Input file is mainGenome.fasta 2021-07-12 13:47:05 INFO: Using local lineages directory poales_odb10/ 2021-07-12 13:47:05 WARNING: An augustus species was mentioned in the config file or on the command line, dataset default species (maize) will be ignored 2021-07-12 13:47:18 INFO: Running BUSCO using lineage dataset (eukaryota, 2020-08-05) 2021-07-12 13:47:18 INFO: Running 1 job(s) on makeblastdb, starting at 07/12/2021 13:47:18 2021-07-12 13:47:20 INFO: ***** Start a BUSCO v5.2.1 analysis, current time: 07/12/2021 13:47:20 ***** 2021-07-12 13:47:20 INFO: Configuring BUSCO with /bioinfo/installs/busco/config/config.ini 2021-07-12 13:47:20 INFO: ***** Start a BUSCO v5.2.1 analysis, current time: 07/12/2021 13:47:20 ***** 2021-07-12 13:47:20 INFO: Mode is genome 2021-07-12 13:47:20 INFO: Configuring BUSCO with /bioinfo/installs/busco/config/config.ini 2021-07-12 13:47:20 ERROR: A run with the name r3.genome already exists... If you are sure you wish to overwrite existing files, please use the -f (force) option 2021-07-12 13:47:20 INFO: Mode is genome 2021-07-12 13:47:20 ERROR: A run with the name r3.genome already exists... If you are sure you wish to overwrite existing files, please use the -f (force) option 2021-07-12 13:47:20 INFO: ***** Start a BUSCO v5.2.1 analysis, current time: 07/12/2021 13:47:20 ***** 2021-07-12 13:47:20 INFO: Configuring BUSCO with /bioinfo/installs/busco/config/config.ini 2021-07-12 13:47:20 ERROR: BUSCO analysis failed ! 2021-07-12 13:47:20 INFO: Mode is genome 2021-07-12 13:47:20 ERROR: BUSCO analysis failed ! 2021-07-12 13:47:20 ERROR: Check the logs, read the user guide (https://busco.ezlab.org/busco_userguide.html), and check the BUSCO issue board on https://gitlab.com/ezlab/busco/issues

2021-07-12 13:47:20 ERROR: A run with the name r3.genome already exists... If you are sure you wish to overwrite existing files, please use the -f (force) option 2021-07-12 13:47:20 ERROR: Check the logs, read the user guide (https://busco.ezlab.org/busco_userguide.html), and check the BUSCO issue board on https://gitlab.com/ezlab/busco/issues

2021-07-12 13:47:20 ERROR: BUSCO analysis failed !

Here is an older error output:

2021-07-07 10:03:41 CRITICAL: Unhandled exception occurred: Traceback (most recent call last): File "/home/pozersky/.local/lib/python3.6/site-packages/busco/BuscoRunner.py", line 122, in run self.runner.run_analysis() File "/home/pozersky/.local/lib/python3.6/site-packages/busco/BuscoRunner.py", line 334, in run_analysis self.analysis.run_analysis() File "/home/pozersky/.local/lib/python3.6/site-packages/busco/analysis/GenomeAnalysis.py", line 236, in run_analysis self._run_mkblast() File "/home/pozersky/.local/lib/python3.6/site-packages/busco/analysis/Analysis.py", line 127, in _run_mkblast self.mkblast_runner.run() File "/home/pozersky/.local/lib/python3.6/site-packages/busco/busco_tools/blast.py", line 45, in run self.run_jobs() File "/home/pozersky/.local/lib/python3.6/site-packages/busco/busco_tools/Toolset.py", line 196, in run_jobs self.cpus, initializer=type(self).init_globals, initargs=(Value("i", 0),) File "/usr/local/lib/python3.6/multiprocessing/context.py", line 119, in Pool context=self.get_context()) File "/usr/local/lib/python3.6/multiprocessing/pool.py", line 174, in init self._repopulate_pool() File "/usr/local/lib/python3.6/multiprocessing/pool.py", line 239, in _repopulate_pool w.start() File "/usr/local/lib/python3.6/multiprocessing/process.py", line 105, in start self._popen = self._Popen(self) File "/usr/local/lib/python3.6/multiprocessing/context.py", line 284, in _Popen return Popen(process_obj) File "/usr/local/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 32, in init super().init(process_obj) File "/usr/local/lib/python3.6/multiprocessing/popen_fork.py", line 20, in init self._launch(process_obj) File "/usr/local/lib/python3.6/multiprocessing/popen_spawn_posix.py", line 42, in _launch prep_data = spawn.get_preparation_data(process_obj._name) File "/usr/local/lib/python3.6/multiprocessing/spawn.py", line 143, in get_preparation_data _check_not_importing_main() File "/usr/local/lib/python3.6/multiprocessing/spawn.py", line 136, in _check_not_importing_main is not going to be frozen to produce an executable.''') RuntimeError: An attempt has been made to start a new process before the current process has finished its bootstrapping phase.

This probably means that you are not using fork to start your
child processes and you have forgotten to use the proper idiom
in the main module:

    if __name__ == '__main__':
        freeze_support()
        ...

The "freeze_support()" line can be omitted if the program
is not going to be frozen to produce an executable.