PoC-Consortium/scavenger

Will not start

Closed this issue · 23 comments

Here's the error and my config. I've been using Johhny FFM Blago for 9 months without any issues, was hoping to get this working.

I tried the previous release and had a lot of trouble, I then found someone's custom config, which had fewer lines than the config that comes with Scavenger. This worked for me, but after a day I started getting miner errors. Went back to Blago for a few days, no errors.

I just downloaded your newest release, and it's not starting. I've tried my old config, as well as dropping my stuff in to the new config... same results.

How does this config look?

Thanks! :)

image

Also.... it doesn't show it in the screenshot... but I did comment out the 1st line before running it.

could you post your config into this issue?
please use the
```
sticks to give it a good layout. Checkout https://help.github.com/articles/basic-writing-and-formatting-syntax/#quoting-code

Try to comment out line 1 and line 45 (account_id_to_....) yaml doesnt allow empty hashmaps.

Same config file as before....I think I did miss a comment tag. It doesn't see my drives.

#account_id_to_secret_phrase:                   # define accounts and passphrases for solo mining 


plot_dirs:
  - 'D:\'
  - 'C:\Burst\Ext_Drive_01'
  - 'C:\Burst\Ext_Drive_02'
  - 'C:\Burst\Ext_Drive_03'
  - 'C:\Burst\Ext_Drive_04'
  - 'C:\Burst\Ext_Drive_05'
  - 'C:\Burst\Ext_Drive_06'
  - 'C:\Burst\Ext_Drive_07'
  - 'C:\Burst\Ext_Drive_08'
  - 'C:\Burst\Ext_Drive_09'
  - 'C:\Burst\Ext_Drive_10'
  - 'C:\Burst\Ext_Drive_11'
  - 'C:\Burst\Ext_Drive_12'
  - 'C:\Burst\Ext_Drive_13'
  - 'C:\Burst\Ext_Drive_14'
  - 'C:\Burst\Ext_Drive_15'
  - 'C:\Burst\Ext_Drive_16'
  - 'C:\Burst\Ext_Drive_17'
  - 'C:\Burst\Ext_Drive_18'
  
url: 'http://pool.burstcoin.space:8124'           # dummypool with constant scoop number for benchmarking

hdd_reader_thread_count: 0            # default 0 (=auto: number of disks)
hdd_use_direct_io: true               # default true
hdd_wakeup_after: 240                 # default 240s

cpu_threads: 0                        # default 0 (=auto: number of logical cpu cores)
cpu_worker_task_count: 4              # default 4 (0=GPU only)
cpu_nonces_per_cache: 65536           # default 65536
cpu_thread_pinning: false             # default false

gpu_threads: 0                        # default 0 (=GPU off)
gpu_platform: 0                       # default 0
gpu_device: 0                         # default 0
gpu_worker_task_count: 0              # default 0 (=CPU only)
gpu_nonces_per_cache: 262144          # default 262144
gpu_mem_mapping: false                # default false
gpu_async: false                      # default false

target_deadline: 1353629             # default u32::MAX
# account_id_to_target_deadline:        # target dls for multi-id (optional)


get_mining_info_interval: 3000        # default 3000ms
timeout: 5000                         # default 5000ms
send_proxy_details: true              # default false

console_log_level: 'info'             # default Info, options (off, error, warn, info, debug, trace)
logfile_log_level: 'warn'             # default Warn, options (off, error, warn, info, debug, trace)
logfile_max_count: 10                 # maximum number of log files to keep
logfile_max_size : 20                 # maximum size per logfile in MiB

show_progress: true                   # default true  
show_drive_stats: true               # default false 
benchmark_only: 'disabled'            # default disabled, options (disabled, I/O, XPU)

# Low noise log patterns
console_log_pattern: "{({d(%H:%M:%S)} [{l}]):16.16} {m}{n}"
logfile_log_pattern: "{({d(%Y-%m-%d %H:%M:%S)} [{l}]):26.26} {m}{n}"

# More detailed log patterns
#console_log_pattern: "{d(%H:%M:%S.%3f%z)} [{h({l}):<5}] [{T}] [{t}] - {M}:{m}{n}"
#logfile_log_pattern: "{d(%Y-%m-%dT%H:%M:%S.%3f%z)} [{h({l}):<5}] [{T}]-[{t}] [{f}:{L}] - {M}:{m}{n}"

image

This is what it looks like in Blago... just so you can see it in a working situation. :)

image

could you try

plot_dirs:
  - "D:\"
  - "C:\Burst\Ext_Drive_01\"
  - "C:\Burst\Ext_Drive_02\"
  - "C:\Burst\Ext_Drive_03\"
  - "C:\Burst\Ext_Drive_04\"
  - "C:\Burst\Ext_Drive_05\"
  - "C:\Burst\Ext_Drive_06\"
  - "C:\Burst\Ext_Drive_07\"
  - "C:\Burst\Ext_Drive_08\"
  - "C:\Burst\Ext_Drive_09\"
  - "C:\Burst\Ext_Drive_10\"
  - "C:\Burst\Ext_Drive_11\"
  - "C:\Burst\Ext_Drive_12\"
  - "C:\Burst\Ext_Drive_13\"
  - "C:\Burst\Ext_Drive_14\"
  - "C:\Burst\Ext_Drive_15\"
  - "C:\Burst\Ext_Drive_16\"
  - "C:\Burst\Ext_Drive_17\"
  - "C:\Burst\Ext_Drive_18\"

Yup, 1 sec. :)

Do you think we need to use escape char too or no?

don't think so, but haven't tried it on windows anyway ;-)

keep the last backslash. actually i think it detects D:\ properly but doesnt detect the rest

This should have incremented to 2, correct?

image

could you try setting

hdd_use_direct_io: false               # default true

?

BAZINGA! I also changed it back to single quotes. Really appreciate your help....

image

Are these something to worry about?

image

actually it's mining, so shouldnt be an issue. but you are freakin slow (63s). is that intended?

cpu_worker_task_count: 24              # default 4 (0=GPU only)

try that :-)

w/ Blago, I was getting somewhere around 35s.
image

I am ok with 38 seconds. :)

I have USB3 drives split over 4 anchor USB hubs. They are connected to a USB controller that has 4 separate controllers, each going to a hub. The D drive is a SAS Raid. This is in a Windows 2016 Dell server w/ 48GB RAM and 24 cores of CPU.

8 cpu threads, 8 worker task count... seems to be the sweet spot. Again, I thank you for your help. Really appreciate it. :)

image

then I think we got this solved :-)
still you should be able to scale it up to all cores you have available

We can close the issue... thanks again. :)