search

signum-network / signum-miner

The official signum-network miner
GNU General Public License v3.0
17 stars 4 forks source link

Error when running on Raspberry Pi 4 #4

Closed arielylim closed 3 years ago

arielylim commented 3 years ago

Downloaded the aarch64 binary and tried running it. Getting this error. What does it mean? How do I get it to run? 

[INFO] signum-miner v.1.8.0
[INFO] SIMD extensions: NEON
thread 'main' panicked at 'called `Option::unwrap()` in a `None` value', src/libcore/option.rs:105:60
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace
boner-cmd commented 3 years ago

Do you get the same error using this binary? https://github.com/PoC-Consortium/scavenger/releases/download/1.7.8/scavenger-1.7.8-aarch64-unknown-linux-android-cpu-only.tar.xz

boner-cmd commented 3 years ago

For dev reference, error is https://doc.rust-lang.org/std/option/enum.Option.html#method.unwrap

P72B commented 3 years ago

Download the binaries and compile on the raspberry Pi 4 itself.

Download binaries: ~ wget https://github.com/signum-network/signum-miner/archive/refs/tags/v1.8.0.tar.gz Unzip: ~ tar -xf v1.8.0.tar.gz Navigate into it: ~ cd signum-miner-1.8.0 Compile version: ~ cargo build --release Test the version with: ~ cargo test Find the version in: ~ cd target/release Copy the miner into your prefered dir where your config.yaml is located at: ~ cp signum-miner /home/ubuntu/

Run the miner within /home/ubuntu (example directory here): ~ ./signum-miner

I just tested it a few minutes ago and it worked out in my case running on a RaspberryPi4+ (8GB)

jjos2372 commented 3 years ago

Downloaded the aarch64 binary and tried running it. Getting this error. What does it mean? How do I get it to run?

[INFO] signum-miner v.1.8.0
[INFO] SIMD extensions: NEON
thread 'main' panicked at 'called `Option::unwrap()` in a `None` value', src/libcore/option.rs:105:60
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Maybe your config file has something invalid. Unfortunately it is not the best reporting those.

arielylim commented 3 years ago

Download the binaries and compile on the raspberry Pi 4 itself.

Will it only work on Ubuntu? I'm running raspberry pi os 64-bit.

I do have another Pi where I can follow this but would be great if I can use the same pi.

arielylim commented 3 years ago

tried it first on Raspberry pi os 64-bit (current system) and encountered this error during the cargo test

failures:

---- config::tests::test_load_cfg stdout ----
thread 'config::tests::test_load_cfg' panicked at 'assertion failed: `(left == right)`
  left: `[]`,
 right: `["test_data"]`', src/config.rs:327:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    config::tests::test_load_cfg

test result: FAILED. 10 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.40s
arielylim commented 3 years ago

Again, on Raspberry Pi OS 64-bit, continuing the instructions despite the test error above, i.e. copy signum-miner inside target/release to a my /home/pi/signum and edited the config.yaml i downloaded directly and added to the same folder

Tried running and got a bunch of errors. I followed each one and modified the config.yaml and finally got it to run.

My problem now is it's not reading any of my plots. 

pi@raspberrypi:~/signum $ ./signum-miner 
10:57:30 [INFO]  signum-miner v.1.8.0
10:57:30 [INFO]  path=/media/pi/USB01/Burst, files=0, size=0.0000 TiB
10:57:30 [WARN]  no plots in /media/pi/USB01/Burst
10:57:30 [INFO]  path=/media/pi/DAS03/Burst, files=0, size=0.0000 TiB
10:57:30 [WARN]  no plots in /media/pi/DAS03/Burst
10:57:30 [INFO]  plot files loaded: total drives=0, total capacity=0.0000 TiB
10:57:30 [INFO]  reader-threads=3 CPU-threads=4
10:57:30 [INFO]  CPU-buffer=4(+4)
10:57:31 [INFO]  new block: height=892103, scoop=926                                             
10:57:34 [INFO]  new block: height=892104, scoop=2733

A couple of questions:

  1. I plotted on my mac using turbo plotter. I then transferred my external drive then connected to the pi. In file manager, i can see the plots. two 23 GiB and one 140GiB. Does that mean it's not reading it? Not compatible? Anything else i need to check?
  2. Assuming i get signum miner to read the plots, how do i know im mining correctly? I'm seeing new block: heaight=892105, scoop=2756 and after a while, adds another block. Does that mean it's working properly? Anything i need to watch out for?
arielylim commented 3 years ago

On a separate pi running Ubuntu Desktop 20.04, i encountered the same thing. I downloaded the aarch64 package and it worked right away. Now, my issue is signum miner isn't recognizing my plots.

Some other steps I did:

Does that mean Signum miner doesn't recognize the plots from TurboPlotter? Or I'm doing something wrong?

(screenshot: terminal log showing zero plots in directory but finder has the plots)

signum

arielylim commented 3 years ago

So there's definitely something wrong. I forgot about the test_data and just added it to the config. It reads the path but returns zero files.

Maybe there's something I need to download for signum to read the plots?

arielylim commented 3 years ago

i did it! i think. does this mean it's now mining properly?

pi@raspberrypi:~/scavenger-1.7.8-cpu-gpu $ ./scavenger 
19:03:43 [INFO]  Scavenger v.1.7.8
19:03:43 [INFO]  SIMD extensions: none
19:03:43 [INFO]  path=/media/pi/USB01/Burst, files=0, size=0.0000 TiB
19:03:43 [WARN]  no plots in /media/pi/USB01/Burst
19:03:43 [INFO]  path=/media/pi/USB02/Burst, files=3, size=0.1824 TiB
19:03:43 [INFO]  plot files loaded: total drives=1, total capacity=0.1824 TiB
19:03:43 [INFO]  reader-threads=3 CPU-threads=4
19:03:43 [INFO]  CPU-buffer=4(+4)
19:03:43 [INFO]  new block: height=892224, scoop=1004                                            
19:03:44 [INFO]  round finished: roundtime=388ms, speed=120.33MiB/s                              
19:03:44 [INFO]  deadline accepted: account=1234567, nonce=17001491091888819781, deadline=28033856
19:04:31 [INFO]  new block: height=892225, scoop=3707                                            
19:04:32 [INFO]  round finished: roundtime=508ms, speed=91.90MiB/s

anything i should watch out for?

for reference, i went back at some threads and the people referenced scavenger. i looked thru the previous releases and tried them all.

i copied my config.yaml to all the installations. the one that worked was the scavenger 1.7.8 arm linux cpu gpu version

1, does this mean it's now mining properly?

  1. i sometimes see an outage then gets connected again. that's okay right?
  2. i also noticed one log saying deadline not accepted, does that mean it scanned my drives too slow? so far it only happened once but how can i prevent that?
  3. what happens next? if my pool wins a block, i'll just see some burstcoin/signumcoin in my wallet after some time?
boner-cmd commented 3 years ago

I'll try to do some testing in the emulated environment to investigate (and also see if I can build a working binary for signum miner). In response to your questions:

  1. Yes, although I see that your USB01 has no plots, which you might want to check
  2. Outages are just fine, it's a network issue on your end or the pool's end, but as long as it's brief that's no issue
  3. Deadlines not being accepted are fine. It's because your maximum deadline is longer than the pool's. No issue there, your shorter deadlines will still go through. You can avoid it by reducing your maximum deadline in the config.
  4. You are all set! You just let it run, and as you said, the pool will send rewards accordingly. Note that the pool will have a minimum payout (which is usually configurable). So you will not see Signa in your wallet until you hit that minimum, but you often can set it very low, even as low as 2 coins I think on some pools.
boner-cmd commented 3 years ago

Going to try to replicate this issue in Qemu, I'll PR if I find anything.

arielylim commented 3 years ago

Gotcha. Thanks. Let me know if you need more info from me to replicate the issue or something.

Yes, although I see that your USB01 has no plots, which you might want to check

I was moving around some plots so this was expected. Thanks for checking the small details.

I do have other questions but I think discord might be better place for it.

jjos2372 commented 3 years ago

Please close the issue if the problem was on your config file or on your end.

arielylim commented 3 years ago

I was able to get it to run but had to revert back to an older version. Anyway, I'll close this now thanks for all the help!

boner-cmd commented 3 years ago

When I'm doing my testing, I may reopen this if the same config doesn't succeed on all builds. That'll be no sooner than Saturday.

From: arielylim @.> Sent: Friday, June 11, 2021 6:53 AM To: signum-network/signum-miner @.> Cc: Dimelo Waterson @.>; Comment @.> Subject: Re: [signum-network/signum-miner] Error when running on Raspberry Pi 4 (#4)

Closed #4https://github.com/signum-network/signum-miner/issues/4.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/signum-network/signum-miner/issues/4#event-4875265970, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4UEJEU43WER6ZZC4PAC5TTSFXTNANCNFSM46LIG4BQ.