Code Monkey home page Code Monkey logo

scavenger's People

Contributors

aprock avatar cohsrt avatar felixbrucker avatar guywhoknowstheguy avatar johnnyffm avatar llybin avatar mmullis avatar revolution2020lv avatar spebern avatar tzdybal avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

scavenger's Issues

Connection wasn't established with burst wallet after scavenger version updating.

Hello.

I have burst wallet 2.2.7 (MySQL database, linux version) and lots of scavenger (linux version) which point to my wallet.
They work OK with scavenger 1.6.6 version. But after updating to 1.7.2 or 1.7.4 scavenger work but I don't see established connections with my wallet port 8125.

netstat -an | grep :8125
result is arround 12 rows as
tcp 0 0 miner_ip:41120 burst_wallet_ip:8125 TIME_WAIT

in scavenger log

2019-02-21 09:17:20 [ERROR error getting mining info => connection outage...                        
2019-02-21 09:18:44 [ERROR outage resolved. 

Illegal Instruction crash again.

I was able to compile scavenger previously using the -O2 flag, however, I am not able to get past the Illegal Instruction crash again. I'm on a dual Xeon E5-2630 CPU.

The previous version did give me the unused reference errors when compiling but did execute (and run) successfully. Now I get no warnings but cannot execute the compiled code.

This is freshly git'd source. Unfortunately I blew away the previous (working) version.

config configuration

first: its for poc 1 or 2
and how can i put in config more than onde hard drive?

Github incorrectly classifies project as C instead of Rust

Github Linguist is detecting all the C code and marking the project as C instead of Rust.
Rust enthusiasts may not find the project when exploring for projects to work on.
From PoC-Consortium page

scavenger
A fast Burstcoin miner written in Rust
C  13  4 GPL-3.0 Updated 19 minutes ago

I'm not sure on the best way to fix this without impacting features for the C code.
It'd be so much simpler if we could just tell github exactly what we want.

Compiling master and tag 1.0.0 fail on Ubuntu 16.04 with AMD10 processor

Compiling master and tag 1.0.0 fail on Ubuntu 16.04 with AMD10 processor.

Error log:
Compiling sys-info v0.5.6
error: cannot find macro is_x86_feature_detected! in this scope
--> build.rs:22:8
|
22 | if is_x86_feature_detected!("avx") {
| ^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error

error: Could not compile scavenger.
warning: build failed, waiting for other jobs to finish...
error: build failed

while parsing a quoted scalar, found unknown escape character

Windows 10 error:

thread 'main' panicked at 'failed to parse config yaml: Scan(ScanError { mark: Marker { index: 66, line: 4, col: 2 }, info: "while parsing a quoted scalar, found unknown escape character" })', libcore\result.rs:945:5

note: Run with RUST_BACKTRACE=1 for a backtrace.

Here is the config:

secret_phrase: ""
account_id: 8961560224519517741
plot_dirs:
"T:\plots"
"J:\plots"
"R:\plots"
"G:\plots"
"I:\plots"
"K:\plots"
"E:\plots"
"S:\plots"
"Y:\plots"
"V:\plots"
"W\\plots"
"N:\plots"
"Q:\plots"
"H:\plots"
"U:\plots"
"L:\plots"
"P:\plots"
"O:\plots"
"M:\plots"
"X:\plots"
url: "http://pool.changed.website:8124"
# url: "http://pool.dev.burst-test.net:8124"
worker_thread_count: 1
reader_thread_count: 1
nonces_per_cache: 65536 # default 65536
target_deadline: 10885484741537822773 # default u64::MAX
use_direct_io: true # default true
get_mining_info_interval: 3000 # default 3000ms

target_deadline was reduced to 1299774 (I'm using 0-100 calculator), but same error appear.

Fails on SSE4 CPU

Scavenger fails with SSE4 CPU

Output of the "optimized build"

/sources/scavenger/target/release$ ./scavenger
using sse2
Ungültiger Maschinenbefehl

Machine/OS Details

$ grep -E "^(model name|flags)" /proc/cpuinfo |head -2
model name      : Intel(R) Atom(TM) CPU  C2550  @ 2.40GHz
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
$ uname -a
Linux server05 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-7-amd64 root=UUID=bc8176bb-2357-4b3f-a117-ba1e49dc1c3c ro quiet pti=off
$ cat /etc/debian_version
9.5
$ uptime
 23:15:30 up 4 days,  2:44,  2 users,  load average: 5,83, 5,51, 4,11

Build log

$ cargo build --release
   Compiling nodrop v0.1.12
   Compiling libc v0.2.42
   Compiling cfg-if v0.1.3
   Compiling num-traits v0.2.5
   Compiling memoffset v0.2.1
   Compiling byteorder v1.2.3
   Compiling lazy_static v1.0.1
   Compiling num-integer v0.1.39
   Compiling scopeguard v0.3.3
   Compiling lazycell v0.6.0
   Compiling slab v0.4.0
   Compiling futures v0.1.23
   Compiling num-iter v0.1.37
   Compiling unicode-xid v0.1.0
   Compiling rustc-serialize v0.3.24
   Compiling serde v1.0.65
   Compiling cc v1.0.18
   Compiling fnv v1.0.6
   Compiling matches v0.1.6
   Compiling rayon-core v1.4.1
   Compiling itoa v0.4.1
   Compiling try-lock v0.2.2
   Compiling indexmap v1.0.1
   Compiling unicode-normalization v0.1.7
   Compiling linked-hash-map v0.5.1
   Compiling string v0.1.0
   Compiling rayon v1.0.2
   Compiling httparse v1.2.4
   Compiling dtoa v0.4.2
   Compiling scoped-tls v0.1.2
   Compiling either v1.5.0
   Compiling percent-encoding v1.0.1
   Compiling libc v0.1.12
   Compiling hex v0.3.2
   Compiling crossbeam-utils v0.3.2
   Compiling log v0.4.1
   Compiling crossbeam-utils v0.2.2
   Compiling arrayvec v0.4.7
   Compiling iovec v0.1.2
   Compiling net2 v0.2.32
   Compiling rand v0.4.2
   Compiling num_cpus v1.8.0
   Compiling time v0.1.40
   Compiling filetime v0.2.1
   Compiling num_cpus v0.2.13
   Compiling proc-macro2 v0.4.5
   Compiling unicode-bidi v0.3.4
   Compiling tokio-executor v0.1.2
   Compiling sys-info v0.5.6
   Compiling scavenger v1.0.0-beta (file:///home/fawkes/sources/scavenger)
   Compiling yaml-rust v0.4.0
   Compiling want v0.0.5
   Compiling bytes v0.4.8
   Compiling crossbeam-epoch v0.4.1
   Compiling crossbeam-epoch v0.3.1
   Compiling mio v0.6.14
   Compiling futures-cpupool v0.1.8
   Compiling rand v0.3.22
   Compiling tokio-timer v0.2.4
   Compiling quote v0.6.3
   Compiling tokio-io v0.1.6
   Compiling http v0.1.7
   Compiling num-complex v0.1.43
   Compiling idna v0.1.5
   Compiling crossbeam-deque v0.2.0
   Compiling crossbeam-deque v0.3.1
   Compiling chan v0.1.21
   Compiling syn v0.14.2
warning: src/c/mshabal_128.c: In function ‘simd128_mshabal_close’:
warning: src/c/mshabal_128.c:317:13: warning: unused parameter ‘ub0’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:              ^~~
warning: src/c/mshabal_128.c:317:27: warning: unused parameter ‘ub1’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                            ^~~
warning: src/c/mshabal_128.c:317:41: warning: unused parameter ‘ub2’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                          ^~~
warning: src/c/mshabal_128.c:317:55: warning: unused parameter ‘ub3’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                                        ^~~
warning: src/c/mshabal_128.c:317:69: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                                                      ^
warning: src/c/mshabal_128.c: In function ‘simd128_mshabal_openclose_fast’:
warning: src/c/mshabal_128.c:650:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n)
warning:               ^
warning: src/c/mshabal_256.c: In function ‘simd256_mshabal_close’:
warning: src/c/mshabal_256.c:365:14: warning: unused parameter ‘ub0’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:               ^~~
warning: src/c/mshabal_256.c:365:28: warning: unused parameter ‘ub1’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                             ^~~
warning: src/c/mshabal_256.c:365:42: warning: unused parameter ‘ub2’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                                           ^~~
warning: src/c/mshabal_256.c:365:56: warning: unused parameter ‘ub3’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                                                         ^~~
warning: src/c/mshabal_256.c:366:14: warning: unused parameter ‘ub4’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:               ^~~
warning: src/c/mshabal_256.c:366:28: warning: unused parameter ‘ub5’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                             ^~~
warning: src/c/mshabal_256.c:366:42: warning: unused parameter ‘ub6’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                                           ^~~
warning: src/c/mshabal_256.c:366:56: warning: unused parameter ‘ub7’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                                                         ^~~
warning: src/c/mshabal_256.c:367:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n,
warning:               ^
warning: src/c/mshabal_256.c: In function ‘simd256_mshabal_openclose_fast’:
warning: src/c/mshabal_256.c:715:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n)
warning:               ^
warning: src/c/shabal.c: In function ‘find_best_deadline_sse2’:
warning: src/c/shabal.c:127:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d0 = *((uint64_t *) res0);
warning:      ^~
warning: src/c/shabal.c:128:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d1 = *((uint64_t *) res1);
warning:      ^~
warning: src/c/shabal.c:129:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d2 = *((uint64_t *) res2);
warning:      ^~
warning: src/c/shabal.c:130:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d3 = *((uint64_t *) res3);
warning:      ^~
warning: src/c/shabal.c: In function ‘find_best_deadline_avx’:
warning: src/c/shabal.c:190:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d0 = *((uint64_t *) res0);
warning:      ^~
warning: src/c/shabal.c:191:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d1 = *((uint64_t *) res1);
warning:      ^~
warning: src/c/shabal.c:192:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d2 = *((uint64_t *) res2);
warning:      ^~
warning: src/c/shabal.c:193:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d3 = *((uint64_t *) res3);
warning:      ^~
warning: src/c/shabal.c: In function ‘find_best_deadline_avx2’:
warning: src/c/shabal.c:271:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d0 = *((uint64_t *) res0);
warning:      ^~
warning: src/c/shabal.c:272:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d1 = *((uint64_t *) res1);
warning:      ^~
warning: src/c/shabal.c:273:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d2 = *((uint64_t *) res2);
warning:      ^~
warning: src/c/shabal.c:274:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d3 = *((uint64_t *) res3);
warning:      ^~
warning: src/c/shabal.c:275:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d4 = *((uint64_t *) res4);
warning:      ^~
warning: src/c/shabal.c:276:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d5 = *((uint64_t *) res5);
warning:      ^~
warning: src/c/shabal.c:277:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d6 = *((uint64_t *) res6);
warning:      ^~
warning: src/c/shabal.c:278:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:      d7 = *((uint64_t *) res7);
warning:      ^~
   Compiling tokio-reactor v0.1.1
   Compiling num-bigint v0.1.44
   Compiling tokio-threadpool v0.1.5
   Compiling h2 v0.1.10
   Compiling serde_yaml v0.7.4
   Compiling serde_json v1.0.19
   Compiling tokio-udp v0.1.0
   Compiling tokio-tcp v0.1.0
   Compiling num-rational v0.1.42
   Compiling url v1.7.1
   Compiling tokio-fs v0.1.0
   Compiling serde_derive v1.0.65
   Compiling tokio v0.1.7
   Compiling num v0.1.42
   Compiling stopwatch v0.0.7
   Compiling hyper v0.12.5
   Compiling tokio-core v0.1.17
    Finished release [optimized] target(s) in 7m 06s

Too bad it doesn't work on a CPU without AVX, but it was worth a try. Maybe you can find a fix. Feel free to contact me using discord @kalinka

Bug in 1.7.8 version then solo mining

Tested with brs 2.4.2 in testnet.
In version 1.7.8 then solo mining it shows this error:
15:14:15 [ERROR] submit: deadlines mismatch, height=83673, account=2726459462890839466, nonce=551059758, deadline_miner=440, deadline_pool=137118424068

Then I submitted nonce manually by doing API call it worked:
{
"result": "success",
"deadline": 2481,
"requestProcessingTime": 150
}
Switched to 1.7.6 with same configuration, all works. So your update broked something in solo mining.

q

Hlo,I revised the burstcoin code,and i affirm that it was running by type of poc2,then i tried to mining by scavenger.Unfortunatly,scavenger had a mistake that cmd display mismatch,i found burstcoin receive true nonce and false id when i look over burstcoin's print(scavenger finds nonce  is consistent with the burstcoin receive nonce,but id is  Different),i inspected scavenger's file of config,i didn't write wrong id in there ,can u give me some recommendations about solution this problem,thx.

CL_NV_INVALID_MEM_ACCESS (-9999)

This only happens on one of my machines.
I feel this is related to capacity and the number of GPU-workers.
If I use 26 for GPU workers, it works fine. It failed if I use 30 or more.
But, I can use more than 40 workers in another machine which has less than 400TB space.
This machine also worked before I installed more drives.

================================================================
00:05:08 [INFO] plot files loaded: total drives=70, total capacity=599.7681 TiB
00:05:08 [INFO] CPU-worker: 20, GPU-worker: 30
thread 'main' panicked at 'called Result::unwrap() on an Err value:

################################ OPENCL ERROR ###############################

Error executing function: clCreateContext

Status error code: CL_NV_INVALID_MEM_ACCESS (-9999)

Please visit the following url for more information:

https://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clCreateContext.html#errors

#############################################################################
', libcore/result.rs:1009:5

two type plotting and which is better?

i'm newer and have many questions. (-:
if i have 100 miner pc and some TBs in every pc.
1, every pc has it's own account and plot it's HDD from 0 ~ XXXX nonces.
2, all the pcs only has one account and plot all the HDD by order.
which is better chance to find the shorter deadline?

Given block height does not match current blockchain height

I've got that error from a few servers after upgrading to 1.7.6 version. I hadn't got that error with previous scavenger versions.
Last value: message: {"result":"Given block height does not match current blockchain height","requestProcessingTime":0}

Web server - "Creepminer-like" Analytics GUI

Hello there,

I was wondering if this was scheduled or even considered as a priority feature ?
I used to have it open on my phone to monitor, tweak and optimize my set-up without moving from the couch back in the PoC1 days.

Would love to have all that pleasure back !

Regards.

SIGILL on Linux AMD FX-8350

Linux snuggles 4.15.7-1-ARCH #1 SMP PREEMPT Wed Feb 28 19:01:57 UTC 2018 x86_64 GNU/Linux
Arch Linux
rustup 1.13.0-3
Latest git commit of scavenger (e27358a)
AMD FX-8350

Build logs:

alexis@snuggles ~/b/scavenger> cargo clean
alexis@snuggles ~/b/scavenger> cargo build --release
   Compiling libc v0.2.42
   Compiling num-traits v0.2.5
   Compiling cfg-if v0.1.3
   Compiling nodrop v0.1.12
   Compiling memoffset v0.2.1
   Compiling byteorder v1.2.3
   Compiling scopeguard v0.3.3
   Compiling lazy_static v1.0.1
   Compiling num-integer v0.1.39
   Compiling lazycell v0.6.0
   Compiling slab v0.4.0
   Compiling futures v0.1.23
   Compiling unicode-xid v0.1.0
   Compiling num-iter v0.1.37
   Compiling rustc-serialize v0.3.24
   Compiling fnv v1.0.6
   Compiling matches v0.1.6
   Compiling cc v1.0.18
   Compiling itoa v0.4.1
   Compiling serde v1.0.65
   Compiling rayon-core v1.4.1
   Compiling indexmap v1.0.1
   Compiling unicode-normalization v0.1.7
   Compiling linked-hash-map v0.5.1
   Compiling unicode-width v0.1.5
   Compiling string v0.1.0
   Compiling rayon v1.0.2
   Compiling try-lock v0.2.2        
   Compiling ansi_term v0.10.2
   Compiling vec_map v0.8.1
   Compiling bitflags v1.0.3                      
   Compiling percent-encoding v1.0.1
   Compiling dtoa v0.4.2
   Compiling strsim v0.7.0                                      
   Compiling either v1.5.0
   Compiling scoped-tls v0.1.2
   Compiling httparse v1.2.4                                                  
   Compiling libc v0.1.12
   Compiling hex v0.3.2
   Compiling crossbeam-utils v0.3.2
   Compiling log v0.4.1
   Compiling crossbeam-utils v0.2.2
   Compiling arrayvec v0.4.7   
   Compiling proc-macro2 v0.4.5
   Compiling unicode-bidi v0.3.4
   Compiling iovec v0.1.2
   Compiling net2 v0.2.32
   Compiling rand v0.4.2
   Compiling num_cpus v1.8.0   
   Compiling time v0.1.40
   Compiling atty v0.2.11
   Compiling filetime v0.2.1   
   Compiling num_cpus v0.2.13  
   Compiling textwrap v0.9.0   
   Compiling yaml-rust v0.4.0  
   Compiling tokio-executor v0.1.2
   Compiling want v0.0.5
   Compiling crossbeam-epoch v0.4.1
   Compiling crossbeam-epoch v0.3.1
   Compiling sys-info v0.5.6   
   Compiling scavenger v1.0.0-beta (file:///home/alexis/builds/scavenger)
   Compiling bytes v0.4.8
   Compiling mio v0.6.14
   Compiling futures-cpupool v0.1.8
   Compiling quote v0.6.3
   Compiling clap v2.30.0
   Compiling tokio-timer v0.2.4
   Compiling rand v0.3.22
   Compiling crossbeam-deque v0.2.0
   Compiling crossbeam-deque v0.3.1
   Compiling tokio-io v0.1.6   
   Compiling http v0.1.7
   Compiling num-complex v0.1.43
   Compiling chan v0.1.21
   Compiling syn v0.14.2
warning: src/c/mshabal_128.c: In function ‘simd128_mshabal_close’:
warning: src/c/mshabal_128.c:317:13: warning: unused parameter ‘ub0’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:              ^~~
warning: src/c/mshabal_128.c:317:27: warning: unused parameter ‘ub1’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                            ^~~
warning: src/c/mshabal_128.c:317:41: warning: unused parameter ‘ub2’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                          ^~~
warning: src/c/mshabal_128.c:317:55: warning: unused parameter ‘ub3’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                                        ^~~
warning: src/c/mshabal_128.c:317:69: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:     unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3, unsigned n,
warning:                                                                      ^
warning: src/c/mshabal_128.c: In function ‘simd128_mshabal_openclose_fast’:
warning: src/c/mshabal_128.c:650:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n)
warning:               ^
warning: src/c/mshabal_256.c: In function ‘simd256_mshabal_close’:
warning: src/c/mshabal_256.c:365:14: warning: unused parameter ‘ub0’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:               ^~~
warning: src/c/mshabal_256.c:365:28: warning: unused parameter ‘ub1’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                             ^~~
warning: src/c/mshabal_256.c:365:42: warning: unused parameter ‘ub2’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                                           ^~~
warning: src/c/mshabal_256.c:365:56: warning: unused parameter ‘ub3’ [-Wunused-parameter]
warning:      unsigned ub0, unsigned ub1, unsigned ub2, unsigned ub3,
warning:                                                         ^~~
warning: src/c/mshabal_256.c:366:14: warning: unused parameter ‘ub4’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:               ^~~
warning: src/c/mshabal_256.c:366:28: warning: unused parameter ‘ub5’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                             ^~~
warning: src/c/mshabal_256.c:366:42: warning: unused parameter ‘ub6’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                                           ^~~
warning: src/c/mshabal_256.c:366:56: warning: unused parameter ‘ub7’ [-Wunused-parameter]
warning:      unsigned ub4, unsigned ub5, unsigned ub6, unsigned ub7,
warning:                                                         ^~~
warning: src/c/mshabal_256.c:367:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n,
warning:               ^
warning: src/c/mshabal_256.c: In function ‘simd256_mshabal_openclose_fast’:
warning: src/c/mshabal_256.c:715:14: warning: unused parameter ‘n’ [-Wunused-parameter]
warning:      unsigned n)
warning:               ^
   Compiling tokio-threadpool v0.1.5
   Compiling num-bigint v0.1.44
   Compiling tokio-reactor v0.1.1
   Compiling h2 v0.1.10
   Compiling serde_yaml v0.7.4 
   Compiling serde_json v1.0.19
   Compiling idna v0.1.5
   Compiling tokio-fs v0.1.0   
   Compiling tokio-udp v0.1.0  
   Compiling tokio-tcp v0.1.0  
   Compiling num-rational v0.1.42
   Compiling serde_derive v1.0.65
   Compiling tokio v0.1.7
   Compiling num v0.1.42
   Compiling stopwatch v0.0.7  
   Compiling tokio-core v0.1.17
   Compiling hyper v0.12.5
   Compiling url v1.7.1
    Finished release [optimized] target(s) in 2m 28s

Running:

alexis@snuggles ~/b/s/t/release> ./scavenger 
using avx
valid plot file: 16968425741416032137_244056064_30507008
valid plot file: 16968425741416032137_274563072_30507008
valid plot file: 16968425741416032137_632979456_19066080
valid plot file: 16968425741416032137_30507008_30507008
valid plot file: 16968425741416032137_396591104_30509952
new block: height: 519574, scoop: 3181
fish: “./scavenger” terminated by signal SIGILL (Illegal instruction)

Adding an -O2 flag to build.rs does allow the miner to start.

alexis@snuggles ~/b/s/t/release> ./scavenger 
using avx
valid plot file: 16968425741416032137_244056064_30507008
valid plot file: 16968425741416032137_274563072_30507008
valid plot file: 16968425741416032137_632979456_19066080
valid plot file: 16968425741416032137_30507008_30507008
valid plot file: 16968425741416032137_396591104_30509952
new block: height: 519575, scoop: 2183
round finished after 17825ms

Low DL rejected as too high

`06:44:06 [INFO] new block: height=749499, scoop=442

06:45:01 [INFO] drive V:\ finished, speed=57 MiB/s
06:45:37 [INFO] deadline accepted: account=18084828890988000920, nonce=1204620186, deadline=6889505
06:46:25 [INFO] deadline accepted: account=18084828890988000920, nonce=103596427, deadline=3112792
06:46:52 [ERROR] submission not accepted: height=749499, account=18084828890988000920, nonce=1120535158, deadline=32092
code: 0
message: {"errorCode":"1008","errorDescription":"deadline exceeds deadline limit of the pool"}`

The rejected dl is smaller than two accepted moments earlier. This cannot be correct.

Win10 on AMD-64 mining 9 NAS drives over SMB.
v 1.7.8 on GPU only.

Thank you for creating this great simple miner.

DL Problem

Hi i have problem with new version. When i use version scavenger 1.6.8 i get better DL and pool show me all of my capacity.I install new version 1.7.0 and miner give bad DL and pool show me 50% of my capacity. I make picture first i start 1.6.8 affter that i star 1.7 - https://www.dropbox.com/s/chud0wh50cuigjv/burst2.png?dl=0

Want to compile to SSE PC

Sorry to disturb .
Is there a flag to compile in sse ( old pc) on my pc (AVX2) ?

When running on my AVX2 PC , all is correct ( plot in synology network drive)

Copy to old pc and message is : SIMD extensions : SSE2
that's all.

Thx

WakeUp: Invalid argument (os error 22)

Running scavenger (latest master) on debian stretch in an non-root account called "miner". HDD Wakeup fails there, disabled it for now.

System info:

$ uptime
 15:36:29 up 31 days, 13:42,  1 user,  load average: 4.90, 2.73, 2.15
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 root=UUID=1a05597b-4ce0-47ec-a745-b0bb622f7281 ro quiet pti=off
$ cat /etc/debian_version
9.4
Aug  6 15:31:22 miner01 miner[3056]: wakeup!
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_610222096_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_190694405_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_724638739_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_419527691_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_533944334_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_305111048_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_381388810_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_572083215_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_76277762_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_648360977_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_152555524_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_495805453_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_686499858_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_228833286_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_0_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_38138881_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_114416643_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_343249929_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_457666572_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round
Aug  6 15:31:22 miner01 miner[3056]: error during wakeup 17633703707761102425_266972167_38138880: Invalid argument (os error 22)
Aug  6 15:31:22 miner01 miner[3056]: #011skip one round

No Deadlines submissions

I have been using BlagoMiner (@JohnnyFFM Fork) and all seems to work fine. However, when using Scavenger I even get messages as "accepted DL" but if I check my pool, there are no new Deadlines at all.

My config looks like this:

plot_dirs:
  - 'g:\'
url: 'http://0-100-pool.burst.cryptoguru.org:8124'

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

cpu_worker_thread_count: 1            # default 4 (0=GPU only)
cpu_nonces_per_cache: 65536           # default 65536
cpu_thread_pinning: false             # default false

gpu_platform: 0                       # default 0
gpu_device: 0                         # default 0
gpu_worker_thread_count: 0            # default 0 (=CPU only)
gpu_nonces_per_cache: 262144          # default 262144
gpu_mem_mapping: false                # default false

target_deadline: 57289751           # default u32::MAX

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: false               # default false 
benchmark_only: 'disabled'            # default disabled, options (disabled, I/O, XPU)

multi_chain: false                    # enable multi-chain mining
maximum_fork_difference: 1440         # maximum block-height difference to last block
minimum_block_height: 500000          # don't work blocks lower than this height

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}"

It's any kind of bug or I am doing something wrong?

Actually used on Windows 10, but I also tested it on Ubuntu 18.04 and some of it's flavors.

gpu error

C:\Users\Administrator\Desktop\scavenger-1.2.0-x86_64-pc-windows-msvc-cpu-only>scavenger.exe -o
19:50:33 [INFO] Scavenger v.1.2.0
19:50:33 [INFO] GPU extensions: OpenCL
19:50:33 [INFO] OCL: platform 0, Intel(R) OpenCL - OpenCL 2.1
19:50:33 [INFO] OCL: device 0, Intel(R) Corporation - Intel(R) UHD Graphics 630
19:50:33 [INFO] OCL: device 1, Intel(R) Corporation - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
19:50:33 [INFO] OCL: platform 1, AMD Accelerated Parallel Processing - OpenCL 2.1 AMD-APP (2580.6)
19:50:33 [INFO] OCL: device 0, GenuineIntel - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz

C:\Users\Administrator\Desktop\scavenger-1.2.0-x86_64-pc-windows-msvc-cpu-only>scavenger.exe
19:50:37 [INFO] Scavenger v.1.2.0
19:50:37 [INFO] GPU extensions: OpenCL
19:50:37 [INFO] SIMD extensions: AVX2
19:50:37 [INFO] OCL: Intel(R) OpenCL - OpenCL 2.1
19:50:37 [INFO] GPU: Intel(R) Corporation - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz
19:50:37 [INFO] GPU: RAM=65205MiB, Cores=12
19:50:37 [INFO] GPU: RAM usage (estimated)=82MiB
19:50:37 [INFO] path=D:\burst\burst14\burst, files=84, size=7.2770 TiB
19:50:37 [INFO] plot files loaded: total capacity=7.2770 TiB
19:50:37 [INFO] CPU-worker: 0, GPU-worker: 1
thread 'main' panicked at 'called Result::unwrap() on an Err value: Kernel work-group info unavailable', libcore\result.rs:945:5
note: Run with RUST_BACKTRACE=1 for a backtrace.

NEON architecture for AArch64 uses 32 × 128-bit register, twice as many as for ARMv7

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/CEGDJGGC.html
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/CJHECGIH.html

The NEON architecture for AArch64 uses 32 × 128-bit register, twice as many as for ARMv7.

If I right understand, then it can improve performance for aarch64?
If yes, I will be grateful for implementation, I think it take for me long time.
I ready to test.

Progress bar mis-calculating total

scav
I just noticed the finished/total size of the progress bar was inacurate. Total cap of drives was 32.7412 TiB but bar showing 8.19 GB. If I'm wrong and that's a different number, I'm sorry.

Scavenger not discovering plots on aarch64

Running Scavanger on on Rock64 SBC (aarch64 RockChip CPU) results in it not finding any plots.
Console output of scavenger and ls of the plot directory:

rock64@rock64:~/git/scavenger/output$ ./scavenger
13:07:37 [INFO]  Scavenger v.1.6.8
13:07:37 [INFO]  SIMD extensions: NEON
13:07:37 [INFO]  path=/mnt/plot, files=0, size=0.0000 TiB
13:07:37 [WARN]  no plots in /mnt/plot
13:07:37 [INFO]  plot files loaded: total drives=0, total capacity=0.0000 TiB
13:07:37 [INFO]  CPU-worker: 4, GPU-worker: 0
13:07:37 [INFO]  new block: height=573495, scoop=2295
rock64@rock64:~/git/scavenger/output$ ls -l /mnt/plot
total 1464731464
-rw-r--r-- 1 rock64 rock64 499961036800 Dec 31 05:40 5373760232911902050_15578371051501912064_1907200
-rw-r--r-- 1 rock64 rock64 499961036800 Jan  1 00:46 5373760232911902050_15578371051503819264_1907200
-rw-r--r-- 1 rock64 rock64 499961036800 Jan  2 08:28 5373760232911902050_15578371051505726464_1907200.plotting
drwx------ 2 root   root          16384 Dec 30 11:08 lost+found

/mnt/plot is a spanned LVM2 volume across three drives connected with USB 3.0 through a docking station, this same setup works on my PC just fine.

FR: Display plotfile/plothdd on error 1008

Usually when it comes to an error '1008' from the pool, something is wrong with the plot and you may wan't to check it.

So it'd be usefull if the log also tells us the affected plotfile/plothdd which lead to the

Aug  6 22:47:48 miner01 miner[15495]: error submitting nonce:
Aug  6 22:47:48 miner01 miner[15495]: #011code: 0
Aug  6 22:47:48 miner01 miner[15495]: #011message: {"errorCode":"1008","errorDescription":"deadline exceeds deadline limit of the pool"}

An output like

Aug  6 22:47:48 miner01 miner[15495]: causing plotfile: /path/to/plot/file

would be neat.

Some problems

I am newer,it didnt work when i use scavenger by my private burstnet(about 3 or 4 burstcoin runing in the local area network),when i use scavenger to mining ,the window appear my computer massage and then it said dismatch,but i use blagominer will normal work,can u give me some recommendations about solution this problem,thx.

Slow reading speeds with 4Kn disks on Linux

I have a server setup with 9 x 10TB disks in it. 2 of these disks are 4Kn.

When running I see the same sort of speeds all the time:-
06:24:50 [INFO] drive fe15 finished, speed=187 MiB/s
06:24:51 [INFO] drive fe0f finished, speed=184 MiB/s
06:24:51 [INFO] drive fe0a finished, speed=184 MiB/s
06:24:51 [INFO] drive fe0e finished, speed=184 MiB/s
06:24:51 [INFO] drive fe14 finished, speed=184 MiB/s
06:24:51 [INFO] drive fe0c finished, speed=183 MiB/s
06:24:55 [INFO] drive fe16 finished, speed=140 MiB/s
06:25:06 [INFO] drive fe0b finished, speed=83 MiB/s
06:25:07 [INFO] drive fe17 finished, speed=81 MiB/s

The two 4Kn disks are running substantially slower always around the 80MB/s. The 512Ke disks run between 120MB/s upto 190MB/s.

If I run a simple DD from the disks reading then they are the same speed as the other disks.
All disks are 7.2K SAS disks dual connected to the HBA.
This performance difference was the same on 1.4 and now on 1.6.

c compiler warnings with gcc

As mentioned in 5b92bc9 all compiler warnings should have been solved. With gcc (debian stretch) they arent :-(

warning: src/c/shabal_sse2.c: In function ‘find_best_deadline_avx’:
warning: src/c/shabal_sse2.c:31:35: warning: unused parameter ‘scoops’ [-Wunused-parameter]
warning:  void find_best_deadline_avx(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                    ^~~~~~
warning: src/c/shabal_sse2.c:31:52: warning: unused parameter ‘nonce_count’ [-Wunused-parameter]
warning:  void find_best_deadline_avx(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                                     ^~~~~~~~~~~
warning: src/c/shabal_sse2.c:31:71: warning: unused parameter ‘gensig’ [-Wunused-parameter]
warning:  void find_best_deadline_avx(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                                                        ^~~~~~
warning: src/c/shabal_sse2.c:32:39: warning: unused parameter ‘best_deadline’ [-Wunused-parameter]
warning:                              uint64_t* best_deadline, uint64_t* best_offset) {}
warning:                                        ^~~~~~~~~~~~~
warning: src/c/shabal_sse2.c:32:64: warning: unused parameter ‘best_offset’ [-Wunused-parameter]
warning:                              uint64_t* best_deadline, uint64_t* best_offset) {}
warning:                                                                 ^~~~~~~~~~~
warning: src/c/shabal_sse2.c: In function ‘find_best_deadline_avx2’:
warning: src/c/shabal_sse2.c:33:36: warning: unused parameter ‘scoops’ [-Wunused-parameter]
warning:  void find_best_deadline_avx2(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                     ^~~~~~
warning: src/c/shabal_sse2.c:33:53: warning: unused parameter ‘nonce_count’ [-Wunused-parameter]
warning:  void find_best_deadline_avx2(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                                      ^~~~~~~~~~~
warning: src/c/shabal_sse2.c:33:72: warning: unused parameter ‘gensig’ [-Wunused-parameter]
warning:  void find_best_deadline_avx2(char* scoops, uint64_t nonce_count, char* gensig,
warning:                                                                         ^~~~~~
warning: src/c/shabal_sse2.c:34:40: warning: unused parameter ‘best_deadline’ [-Wunused-parameter]
warning:                               uint64_t* best_deadline, uint64_t* best_offset) {}
warning:                                         ^~~~~~~~~~~~~
warning: src/c/shabal_sse2.c:34:65: warning: unused parameter ‘best_offset’ [-Wunused-parameter]
warning:                               uint64_t* best_deadline, uint64_t* best_offset) {}
warning:                                                                  ^~~~~~~~~~~
warning: src/c/shabal_sse2.c: In function ‘find_best_deadline_sse2’:
warning: src/c/shabal_sse2.c:91:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:          d0 = *((uint64_t*)res0);
warning:          ^~
warning: src/c/shabal_sse2.c:92:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:          d1 = *((uint64_t*)res1);
warning:          ^~
warning: src/c/shabal_sse2.c:93:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:          d2 = *((uint64_t*)res2);
warning:          ^~
warning: src/c/shabal_sse2.c:94:9: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
warning:          d3 = *((uint64_t*)res3);
warning:          ^~

Version Details of 'cc'

$ cc -v
Using built-in specs.
COLLECT_GCC=cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)

Error compile

git done :
windows 10
try compile :
get this error :

Compiling ring v0.13.2
Compiling scavenger v1.0.0 (file:///C:/scavenger-master)
error: failed to run custom build command for scavenger v1.0.0 (file:///C:/scavenger-master)
process didn't exit successfully: C:\scavenger-master\target\debug\build\scavenger-a243bc2bb4d251ec\build-script-build (exit code: 101)
--- stderr
thread 'main' panicked at '

Internal error occurred: Command "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX64\x64\cl.exe" "/nologo" "/MD" "/Z7" "/W4" "/O2" "/Oi" "/Ot" "/Oy" "/GT" "/GL" "/FoC:\scavenger-master\target\debug\build\scavenger-94ec921e0eed4d95\out\src/c\shabal_sse2.o" "/c" "src/c/shabal_sse2.c" with args "cl.exe" did not execute successfully (status code exit code: 2).

', C:\Users\Marc.cargo\registry\src\github.com-1ecc6299db9ec823\cc-1.0.18\src\lib.rs:2181:5
note: Run with RUST_BACKTRACE=1 for a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed

unix compile unresolved import `utils::set_thread_ideal_processor`

error[E0432]: unresolved import utils::set_thread_ideal_processor
--> src/miner.rs:30:5
|
30 | use utils::set_thread_ideal_processor;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no set_thread_ideal_processor in utils

error[E0432]: unresolved import utils::set_thread_ideal_processor
--> src/reader.rs:17:5
|
17 | use utils::set_thread_ideal_processor;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no set_thread_ideal_processor in utils

warning: unused import: utils::set_thread_ideal_processor
--> src/miner.rs:30:5
|
30 | use utils::set_thread_ideal_processor;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: #[warn(unused_imports)] on by default

warning: unused import: utils::set_thread_ideal_processor
--> src/reader.rs:17:5
|
17 | use utils::set_thread_ideal_processor;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

how to miner mutil hard disk coin?

i want to miner mutil coin containing from BHD AETH etl.
but i use linux , the ddproxy can't use on linux ,
did you have some related project? or some recommand.

Failed to read chunk

nonce 823345717 -> deadline: 2170608
nonce 758560213 -> deadline: 25280
thread '' panicked at 'failed to read chunk: Os { code: 87, kind: Other, message: "Paramètre incorrect." }', libcore\result.rs:945:5
note: Run with RUST_BACKTRACE=1 for a backtrace.
Rayon: detected unexpected panic; aborting

Install on embedded Linux ARM v7l

Any chance to obtain a statically linked version?

I have two NAS boxes and accessing over the net takes 2 minutes. It runs Busybox and the libs are all different from what you find on Debian, etc. When I run scavenger it gives a 'segmentation fault'.

[/share/CACHEDEV1_DATA/scavenger] # ldd scavenger ./scavenger: /lib/libc.so.6: version GLIBC_2.15' not found (required by ./scavenger)
./scavenger: /lib/libc.so.6: version GLIBC_2.16' not found (required by ./scavenger) ./scavenger: /lib/libc.so.6: version GLIBC_2.18' not found (required by ./scavenger)
libdl.so.2 => /lib/libdl.so.2 (0x2b0e8000)
librt.so.1 => /lib/librt.so.1 (0x2b109000)
libpthread.so.0 => /lib/libpthread.so.0 (0x2b12a000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2b15d000)
libc.so.6 => /lib/libc.so.6 (0x2b177000)
ld-linux-armhf.so.3 => /lib/ld-linux-armhf.so.3 (0x2b27b000)
libm.so.6 => /lib/libm.so.6 (0x2b2ac000)
/lib/ld-linux-armhf.so.3 (0x2b0b7000)
`

I've tried copying libc.so.6 from the SBC that it does run on and setting the lib path, but that doesn't help, either.

I also tried installing Rust, but the installer fails.

Running on alpine docker doesn't work anymore

Hi,

i just tried using the latest (v1.6.0) binary in alpine docker, but it always fails with the following error:

bash-4.4# ./scavenger --help
bash: ./scavenger: No such file or directory

or when running it directly via docker CMD:

docker run --rm -it scavenger:latest --help
standard_init_linux.go:190: exec user process caused "no such file or directory"

1.4.0 worked just fine. I'm possibly missing some lib/dependency for it to work?

My dockerfile is as follows:

FROM alpine:latest

RUN apk update && apk upgrade && \
apk add --no-cache bash wget tar util-linux xz

WORKDIR /app

RUN wget -O scavenger.tar.xz 'https://github.com/PoC-Consortium/scavenger/releases/download/v.1.6.0/scavenger-1.6.0-x86_64-unknown-linux-gnu-cpu-only.tar.xz' && \
tar xf scavenger.tar.xz && rm -rf test_data && rm config.yaml && rm scavenger.tar.xz

ENTRYPOINT ["./scavenger"]
CMD ["--config","/data/config.yaml"]

Will not start

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

submit: deadlines mismatch

12:11:46 [INFO] round finished: roundtime=181ms, speed=13.47MiB/s
12:11:46 [ERROR] submit: deadlines mismatch, height=635539, account=4827488958201067556, nonce=9077, deadline_miner=484024290, deadline_pool=188039037078246
12:15:49 [INFO] HDD, wakeup!

pls help me! thanks!

Scavenger doesnt mine drives that have disconnected / reconnected automatically

Last time i used scavenger 1.2, it doesnt recover like blago does on the next block if your disks disconnected / reconnected for a short time until you restarted scavenger. I also noticed when i closed scavenger while in this state, it would be a laggy close (not instant). Is this fixed in 1.4?

Windows 10 64bit LTSB
i7-7700k

add miners name

Excavating the burst in the HPOOL mining pool, the mining pool will provide API-KEY. I don't know the part of the editing configuration file. The running scavenger is submitted normally, but I can't find my miner in the mining pool.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.