f04ever / noso-2m Goto Github PK

Hey @f04ever,

Looks like you forgot to implement a version report.

Cheers,
Gus

Hey @f04ever,

I have a 1 core 2 threads CPU(Yeah, really crappy :) ) and the miner does not seem to saturate the 2nd thread.

It makes one of the threads be 100% most of the time but the other thread is barely tickled, I think.

Is this intentional?

Cheers,
Gus

Hey @f04ever,

The noso-2m.log does not contain any DEBUG data and when I use -DDEBUG it clashes with:

file: logging.hpp

enum class CLogLevel { FATAL, ERROR, WARN, INFO, -->DEBUG<--, };

You do not log much. Not even the accepted/rejected/failed shares.

So how can I turn on DEBUG?

Cheers,
Gus

any clue ? maybe password support ?

Hey @f04ever,

If I remove the option -fuse-ld=lld or replace it with -fuse-ld=ld I then get this error:

$ clang++ noso-2m.cpp md5-c.cpp -o noso-2m -std=c++20 -O3 -DNDEBUG --stdlib=libc++ -lpthread -lc++abi -lncurses -lform -ltermcap
noso-2m.cpp:4:10: fatal error: 'map' file not found
#include <map>
         ^~~~~
1 error generated.

I guess I need to sudo apt install the dev version of the package that supports map ?

Cheers,
Gus

[04/16/23 07:39:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [46]
[04/16/23 07:39:46] INFO:(586)Wait target from pool fishing...
[04/16/23 07:39:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [46]
[04/16/23 07:39:46] INFO:(586)Wait target from pool propool...
[04/16/23 07:39:46] INFO:(586) Sent 2 / 0 / 0 | 0.1334658 NOSO [ 0]
[04/16/23 07:39:46] INFO:(586)Wait target from pool estripa...
[04/16/23 07:39:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [ 0]
[04/16/23 07:39:46] INFO:(586)Wait target from pool propool...
[04/16/23 07:39:46] INFO:(586) Sent 2 / 0 / 0 | 0.08962962 NOSO [ 0]
[04/16/23 07:39:46] INFO:(586)Wait target from pool noso-mn...
[04/16/23 07:40:20]DEBUG:(020) Computed 1759363 hashes within 5.79 minutes
[04/16/23 07:40:20] INFO:(020) Hashrate(Miner/Pool/Mnet) 5.1K / 18.1M / 325.6K

[04/16/23 13:09:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [42]
[04/16/23 13:09:46] INFO:(586)Wait target from pool fishing...
[04/16/23 13:09:46] INFO:(586) Sent 2 / 0 / 0 | 0.01713432 NOSO [ 0]
[04/16/23 13:09:46] INFO:(586)Wait target from pool noso-mn...
[04/16/23 13:09:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [41]
[04/16/23 13:09:46] INFO:(586)Wait target from pool propool...
[04/16/23 13:09:46] INFO:(586) Sent 2 / 0 / 0 | 0.10329931 NOSO [ 0]
[04/16/23 13:09:46] INFO:(586)Wait target from pool estripa...
[04/16/23 13:09:46] INFO:(586) Sent 2 / 0 / 0 | 0 NOSO [44]
[04/16/23 13:09:46] INFO:(586)Wait target from pool propool...

may be you should add password support ?

Hey @f04ever,

Sometimes the app dumps the core when accessing the net when it already has a past hint_nodes.txt file.
I'm sorry that it's so vague, but when I do have those core dumps, I delete the hint_nodes.txt file and the app runs again OK after creating a new hint_nodes.txt file.

Cheers,
Gus

Hey @f04ever,

For some unknown reason win64 versions of the software are now completely unable to connect to a pool as shown in the following image:

The Windows machine hosting the pool has a miner that can't even connect to itself.

Edit: They can still mine solo. But they cannot mine to any pool. We even tried devnoso

We have 6 Linux 64b machines that are having no issues connecting to the pool.

Is it a situation with to low of an integer?

Cheers,
Gus

Hey @f04ever,

Looks like there's something going boom:

getsockopt/socket failed: Operation now in progress
1650425912(512))WAITING TARGET FROM POOL Ravi (Retry 4/5)
getsockopt/socket failed: Operation now in progress
1650425915(515))WAITING TARGET FROM POOL Ravi (Retry 5/5)
1650425915(515))NO REDUNDANT POOL FOR FAILOVER. MAKE ANOTHER ATTEMPT!
getsockopt/socket failed: Operation now in progress
1650425918(518))WAITING TARGET FROM POOL Ravi (Retry 1/5)
^C
Ctrl+C pressed! Wait for finishing all threads...
getsockopt/socket failed: Operation now in progress
./noso-2m.sh: line 10: 397002 Segmentation fault      (core dumped)

Really sorry I can't give you more info ☹️

Cheers,
Gus

Hey @f04ever,

I've been noticing, more than 5 times by my count, that the new version of noso-2m will get stuck when transitioning from one block to the other.

The last info it shows is the Summary, and that's it.

The Waiting for block never shows up

Cheers,
Gus

Add support password. now you have to add password to mine

Hey @f04ever,

I get the following error when trying to use lld as the linker

$ clang++ noso-2m.cpp md5-c.cpp -o noso-2m -std=c++20 -O3 -DNDEBUG --stdlib=libc++ -fuse-ld=lld -lpthread -lc++abi -lncurses -lform -ltermcap
clang: error: invalid linker name in argument '-fuse-ld=lld'

Ubuntu 22.04 64b:

$ clang++ --version
Ubuntu clang version 14.0.0-1ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

Am I missing the installation of this new linker?

Cheers,
Gus

Hey @f04ever,

If one surrounds the binary with an infinite loop, like so:

while true
do
    noso-2m ....
done

It's nigh impossible to exit the bash script with CTRL+C.

The last time I tried it I had to kill -9 the parent bash process and then had to kill -9 the noso-2m cuz it didn't die when the parent was killed. Resilient bastard 😄

Cheers,
Gus

Hey @f04ever,

You need to have the mining process stop at 57 accepted shares.
You also need to correctly process the pool message that states that the pool has accepted 57 shares.

I had try at doing the stop after 57 accepted but I failed miserably 😄 !!

Cheers,
Gus

Hey @f04ever,

I've noticed that when running:

$ ./noso-2m --version

An empty log file is created.

I'm of the opinion that when ever the --version flag is present, event if there are others, it should always report the version and then exit.
This would imply that the log is not created.

What's your opinion?

Cheers,
Gus