How to Solo Mine

Started by wowario, Jun 12, 2021, 01:39 PM

Previous topic - Next topic
Print
Go Down Pages 1 ... 6 7 8 9 10
User actions

orklemerkle

#105
Oct 18, 2021, 08:10 AM
That message seems to be mostly harmless.

stalker9

#106
Oct 28, 2021, 05:23 AM
I have error at wallet
Known ring does not include the spent output: xxxx
version of wallet and daemon is last
how i can send transaction???

onesmartfellow

#107
Oct 28, 2021, 11:03 PM
Hey all,
i've been at the mining game full on for about 6 months, I'm still learning and have even more to learn!  

I've set up a monster WinX laptop with pathetic nvidea card, 2015 Macbok, 2020 M1 Macbook Air, and put a 32bit 1Gb netbook to good use a few months back as my xmrig-proxy, which has actually allowed me to block my mining specific devices at the router as their mining traffic is sent to the proxy.

But now I'm well out of my league and I'm hoping the community can help out as I can get everyone on the wownero train here and maybe find a block!  Currently, the M1 is running the wownerod which is working fine and it can use xmrig to mine on itself.  But that's as far as I can go.  Nothing can mine against the M1, "connection is refused".  I've gone so far as turning the firewall off completely and still no luck, yet I can ping it no problem.

I'm thinking it's not an Apple M1 firewall thing (as wownerod has been added and allowed) but more of a wownero configuration issue.  I'm somewhat savvy with the xmrig setup so I naturally went configuration file route when setting up the wownero daemon.  But it seems I have the "ultra black ops" Tor enabled configuration and it may be too restrictive for even local network mining.  I'll put that config at the bottom is someone wants to take a quick look.

I then shifted to the 'bare bones' approach since most mining walk-throughs basically 1)download wownero and 2) run ./wownerod --spend-key ......   So I tried just firing it up with the --log-file /Volumes/MINIX/Chains/WOW/wownero.log --data-dir /path/to/external/ssd  with still the same "connection refused".

Finally, I thought I may need to be less restrictive on my firewall (less restrictive than off!?!) so I dug around the Sharing but that's for access to my files, or remote control it.  I just want to connect the xmrig-proxy to it and get everyone going.

So I think it's just the config of wownerod is not accepting external connections or isn't listen on ports.  I just tried --add-peer IP.of.Peer.2add. with no luck.  Any tips of commands I should be using?  Seems like you can set --allow-local or --add-peer at start/run time but not while it's running?

Anyways, I'll leave it here as I suspect it's a total n00b issue and most everyone knows what's up.  Please share!  Thanks.  
osf

```
#anonymous-inbound=YOUR_ONION_ADDRESS:34566,127.0.0.1:34566,64
check-updates=disabled
log-level=0
no-igd=1
no-zmq=1
restricted-rpc=1
p2p-bind-ip=0.0.0.0
p2p-bind-port=34567
public-node=1
confirm-external-bind=1
rpc-bind-ip=0.0.0.0
rpc-bind-port=34568
rpc-ssl=autodetect
disable-rpc-ban=1
db-sync-mode=safe
out-peers=64
in-peers=64
limit-rate-up=1048576
limit-rate-down=1048576
tx-proxy=tor,127.0.0.1:9050,23
add-priority-node=v2admi6gbeprxnk6i2oscizhgy4v5ixu6iezkhj5udiwbfjjs2w7dnid.onion:34568
add-priority-node=iy6ry6uudpzvbd72zsipepukp6nsazjdu72n52vg3isfnxqn342flzad.onion:34568
add-priority-node=7ftpbpp6rbgqi5kjmhyin46essnh3eqb3m3rhfi7r2fr33iwkeuer3yd.onion:34568
add-priority-node=j7rf2jcccizcp47y5moehguyuqdpg4lusk642sw4nayuruitqaqbc7ad.onion:34568
add-priority-node=aje53o5z5twne5q2ljw44zkahhsuhjtwaxuburxddbf7n4pfsj4rj6qd.onion:34568
add-priority-node=nepc4lxndsooj2akn7ofrj3ooqc25242obchcag6tw3f2mxrms2uuvyd.onion:34568
add-priority-node=666l2ajxqjgj5lskvbokvworjysgvqag4oitokjuy7wz6juisul4jqad.onion:34568
add-priority-node=ty7ppqozzodz75audgvkprekiiqsovbyrkfdjwadrkbe3etyzloatxad.onion:34568
```

orklemerkle

#108
Oct 29, 2021, 12:36 AM
That is indeed odd. You've already set `confirm-external-bind`, `restricted-rpc`, and `rpc-bind-ip`. Can you show your log file as `wownerod` starts up? I'm specifically interested in any log lines around `Initializing core RPC server`.

You might also want to try setting `rpc-bind-ip` to your actual LAN IP address and see if that helps.

onesmartfellow

#109
Oct 29, 2021, 12:56 AM
Awesome.  I'll have that out right away.  Thanks!  I really just dumped that conf in there, knowing enough that I didn't feel it was dangerous.  Anyways, brb.

Sorry for the delay, I had wandered down the "put the proxy on the daemon" path even though that won't be my end setup.  Got 1 device connected to proxy plus itself.  Doesn't give a lot of feedback does it?

Anyways, started a fresh log.
|2021-10-29 02:08:30.502|     0x201d7fe00|INFO|logging|contrib/epee/src/mlog.cpp:273|New log categories: *:WARNING,net:FATAL,net.http:FATAL,net.ssl:FATAL,net.p2p:FATAL,net.cn:FATAL,daemon.rpc:FATAL,global:INFO,verify:FATAL,serialization:FATAL,daemon.rpc.payment:ERROR,stacktrace:INFO,logging:INFO,msgwriter:INFO|
|---|---|---|---|---|---|
|2021-10-29 02:08:30.503|     0x201d7fe00|INFO|global|src/daemon/main.cpp:294|Wownero 'Junkie Jeff' (v0.10.1.0-release)|
|2021-10-29 02:08:30.503|     0x201d7fe00|INFO|global|src/daemon/protocol.h:53|Initializing cryptonote protocol...|
|2021-10-29 02:08:30.503|     0x201d7fe00|INFO|global|src/daemon/protocol.h:58|Cryptonote protocol initialized OK|
|2021-10-29 02:08:30.505|     0x201d7fe00|INFO|global|src/daemon/core.h:63|Initializing core...|
|2021-10-29 02:08:30.505|     0x201d7fe00|INFO|global|src/cryptonote_core/cryptonote_core.cpp:515|Loading blockchain from folder /Volumes/MINIX/Chains/WOW/lmdb ...|
|2021-10-29 02:08:30.673|     0x201d7fe00|INFO|global|src/cryptonote_core/cryptonote_core.cpp:690|Loading checkpoints|
|2021-10-29 02:08:30.673|     0x201d7fe00|INFO|global|src/daemon/core.h:73|Core initialized OK|
|2021-10-29 02:08:30.674|     0x201d7fe00|INFO|global|src/daemon/p2p.h:63|Initializing p2p server...|
|2021-10-29 02:08:30.685|     0x201d7fe00|INFO|global|src/daemon/p2p.h:68|p2p server initialized OK|
|2021-10-29 02:08:30.685|     0x201d7fe00|INFO|global|src/daemon/rpc.h:63|Initializing core RPC server...|
|2021-10-29 02:08:30.686|     0x201d7fe00|INFO|global|contrib/epee/include/net/http_server_impl_base.h:79|Binding on 127.0.0.1 (IPv4):34568|
|2021-10-29 02:08:35.749|     0x201d7fe00|INFO|global|src/daemon/rpc.h:69|core RPC server initialized OK on port: 34568|
|2021-10-29 02:08:35.751|     0x201d7fe00|INFO|global|src/daemon/rpc.h:74|Starting core RPC server...|
|2021-10-29 02:08:35.751|[SRV_MAIN]|INFO|global|src/daemon/rpc.h:79|core RPC server started ok|
|2021-10-29 02:08:35.753|[SRV_MAIN]|INFO|global|src/daemon/p2p.h:78|Starting p2p net loop...|
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795||
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|       ██╗██╗   ██╗███╗   ██╗██╗  ██╗██╗███████╗ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|       ██║██║   ██║████╗  ██║██║ ██╔╝██║██╔════╝ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|       ██║██║   ██║██╔██╗ ██║█████╔╝ ██║█████╗   |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|  ██   ██║██║   ██║██║╚██╗██║██╔═██╗ ██║██╔══╝   |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|  ╚█████╔╝╚██████╔╝██║ ╚████║██║  ██╗██║███████╗ |
|2021-10-29 02:08:36.761|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1795|   ╚════╝  ╚═════╝ ╚═╝  ╚═══╝╚═╝  ╚═╝╚═╝╚══════╝   |
|2021-10-29 02:08:36.764|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823||
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                      @@@@&///////////////@                |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                       @@@@@@@@@@@@@@@@*/////////////////////#@            |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                     @#////////(&@@@@//////////////////////////////////@   |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                 @&////////////////////////////#@@@@@@@       *////////@   |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|               @%///////////////////////////&@@@@@@/            /////&@    |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|             @@//////////////////////////%@@@@@@              */////@      |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|           @@#//////////////#@@@@@@@@@@@@@@@& ,///////////*  /////#@       |
|2021-10-29 02:08:36.765|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|           @///////////*@@@@@@@@@@@@@     .////////////@@@#//////&@        |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|        @(///////////%@@@@/,%&&/     ,//////.  */////////(@@@%///#@        |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|    @%//////////// *////////////////////////////  //////////@@@@///&       |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|@%//////////. *///////////////S/v/n/g/V/f/G/u/r/C/b/b/e//////@@@@///      |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|  @////////////*.///////%/////////////Z/n/a/f/Z/b/a/r/l/////////@@@(//     |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|     @@@#////////////..///@@@(///////////////////////////////////@@@///    |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|           @@#//////////. //&@@(//////////////////////////((((*////(////   |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                 &//////// ///@@%////////////////////(((((((((,*/////////  |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                            //&@@///////////((((%%%%(/////%%%%(,*////////  |
|2021-10-29 02:08:36.766|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                            .//@@@/////////*(((///%%//%//%%/////*///////#  |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                             //(@@@@////////**////(%%%%%%%%%//////**////// |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                              ////////////////,/////%%%//%%////////#*////  |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                              .////////////////*///////////////..,**/////  |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                               ,////////////////*/////#...,***//////////   |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                &////////////////*,,**/////////////////    |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                  #///////////////////////////////////     |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                    %///////////////////////////////       |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                        //////////////////////////         |
|2021-10-29 02:08:36.771|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1823|                                             ////////////////                |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|        ██╗███████╗███████╗███████╗ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|        ██║██╔════╝██╔════╝██╔════╝ |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|        ██║█████╗  █████╗  █████╗   |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|   ██   ██║██╔══╝  ██╔══╝  ██╔══╝   |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|   ╚█████╔╝███████╗██║     ██║      |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831|    ╚════╝ ╚══════╝╚═╝     ╚═╝      |
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1831||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.775|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|**********************************************************************|
|2021-10-29 02:08:36.776|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|The daemon will start synchronizing with the network. This may take a long time to complete.|
|2021-10-29 02:08:36.776|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Caution: Wownero is highly experimental software compiled by a ragtag team of stoners with as much|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|skill as Verge developers. Storing your life savings in WOW is probably not a good idea.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|You can set the level of process detailization through set_log command,|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|where is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING).|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843||
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Use the help command to see the list of available commands.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|Use help to see a command's documentation.|
|2021-10-29 02:08:36.777|[P2P1]|INFO|global|src/cryptonote_core/cryptonote_core.cpp:1843|**********************************************************************|
|2021-10-29 02:08:37.326|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478||
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|**********************************************************************|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|You are now synchronized with the network. You may now start wownero-wallet-cli.|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478||
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|Use the help command to see the list of available commands.|
|2021-10-29 02:08:37.327|[P2P3]|INFO|global|src/cryptonote_protocol/cryptonote_protocol_handler.inl:2478|**********************************************************************|

onesmartfellow

#110
Oct 29, 2021, 01:49 AM
This may be a dumb question(s) but is it an accurate statement to say that:

* only the device hosting the bc and daemon can actually mine directly against it
* only that device can run xmrig-proxy against it
* and only then can other devices on the local network (or elsewhere) can connect to the proxy?

Maybe I'm trying to do something not doable.  Again, M1 is currently running it, but the Chain, Daemon, and wallet is on a M2 SSD portable enclosure, hoping to delegate my old Macbook to that task as it's not a good miner.  Win7Starter netbook is my proxy that I'd like to connect to the daemon, then have my 2 good ones have the most resources to grind away and see if I can't land a block within the 20 days it says it will take me.

orklemerkle

#111
Oct 29, 2021, 11:07 AM
Quote from: "onesmartfellow, post:110, topic:551"Awesome. I'll have that out right away. Thanks! I really just dumped that conf in there, knowing enough that I didn't feel it was dangerous.

Whoops, sorry, I think I worded that wrong. I meant that your config was already fine. (But you can leave out `public-node=1`.)

Your log looks as if if you'd erased the `rpc-bind-ip`, `restricted-rpc`, and `confirm-external-bind` lines. According to the Monero docs. Could you please try to put the three lines back again, and then post *both* the config and relevant log here?

Awesome formatting on the log, btw.

---

Quote from: "onesmartfellow, post:111, topic:551"This may be a dumb question(s)

There are no dumb questions :stuck_out_tongue:

Quote from: "onesmartfellow, post:111, topic:551"but is it an accurate statement to say that:

* only the device hosting the bc and daemon can actually mine directly against it
* only that device can run xmrig-proxy against it

These two are only true if your daemon's RPC port is bound to 127.0.0.1 or localhost. If it's bound to 0.0.0.0 (which means all network interfaces) or a specific interface's address, then other devices on the connected network should be able to mine (or run a proxy) against the daemon.

Quote from: "onesmartfellow, post:111, topic:551"* and only then can other devices on the local network (or elsewhere) can connect to the proxy?

This is indeed the default on `xmrig-proxy`. You can play with forwarding or routing settings to access the proxy from elsewhere, but that doesn't sound like what you're trying to achieve.

**EDIT**: Sorry, I misunderstood your question. See above; if your daemon is set up to listen on the local network, then other devices can either connect directly to it or to the proxy.

Quote from: "onesmartfellow, post:111, topic:551"Maybe I'm trying to do something not doable.

Don't worry, it's perfectly doable! :grinning: It would just take some work that depends on your specific network setup.

semar

#112
Oct 30, 2021, 03:23 AM
using xmrig for mining
how to check if i found a blok?

orklemerkle

#113
Oct 30, 2021, 06:39 AM
Assuming you're mining directly from xmrig to the daemon (not using `xmrig-proxy`), type `s` into the xmrig window and see how many results are accepted. Zero means your miner hasn't found any blocks.

idontfindanyusername

#114
Nov 03, 2021, 02:46 AM
I'm trying to solo mine for the first time time but I have some issues. Everything seems to work properly but the p2p server doesn't work as for the IPv4.



How do I fix this?

orklemerkle

#115
Nov 03, 2021, 10:38 AM
What's your OS? Can you post your config/command line here?

Also, make sure that no other instance of wownerod is running.

onesmartfellow

#116
Nov 03, 2021, 01:48 PM
I'm happy to report that coming back fresh after a couple days, along with the invaluable guidance of @orklemerkle , I was able to get things up and running.  As it wasn't very intuitive for a 20 year IT veteran, I thought I'd share the snags I came across.

First off, I'd like to reiterate that my goal was to get the daemon running on one device, xmrig-proxy on another, then have a bunch of devices, including the daemon runner to mine using the proxy.  But most of my notes here will be helpful to first time installers just trying to get the daemon running and being able to connect to it.

The documentation seems to heavily rely on monero's, yet there are changes that I was not able to find the documentation for, granted I honestly didn't look too hard either as I assumed it was me that was doing something wrong and just troubleshot from that mentality.

The first piece is the config file, monero's documentation states that it looks by default for bitmonero.conf in the data directory (where the blockchain is located).  Putting wownerod.conf in this directory does NOT have it read in, which I discovered by tweaking the values I could see during start up and they were not changing.  Putting `--config-file path/to/config` resolved this.

The second hurdle encountered was an error message on start-up as follows:
```
2021-11-03 10:29:39.123   I Loading checkpoints
2021-11-03 10:29:39.124   E Invalid argument to --dns-versions-check: enabled
```
Through trial and error, as I had an original, yet not configured for my purposes wownerod.conf file that would not receive the error, was that `check-updates=disabled` is necessary.  If `enabled`, the error appears and the daemon won't start.

After this, the daemon would start and it was a matter of applying @orklemerkle 's guidance on setting the `rpi-bind-ip` to what I wanted the xmrig-proxy to connect to, along with `restricted-rpc=1`, `confirm-external-bind=1`, and `public-node=0`  

Once set up as above, I had no problem connecting xmrig-proxy and getting all miners to connect to it.  I actually prefer using the proxy as there's more feedback as to 'yes, it's mining and yes all is well' as the shares are accepted as opposed to just the miner category logs popping up with one's hashrate at the configured cadence.

Good luck everyone.  Hit me up with any xmrig miner or proxy related questions you may have as I've had a fair amount of exposure the past few months.

OSF

onesmartfellow

#117
Nov 04, 2021, 06:13 AM
How do you tell **if** you are using xmrig-proxy?  Does Owen Wilson run up behind me and whisper "Wow" in my ear? (I sure hope so)

orklemerkle

#118
Nov 04, 2021, 08:55 AM
WOW indeed. To see whether you're using a proxy, check xmrig's `config.json`. In the `pools` section, note the `url` and `daemon` values.

Assuming that the config works, `"daemon": false` indicates you're mining to a proxy (or pool) of some sort. `"daemon": true` implies you're mining directly to a daemon without a proxy.

To be extra sure, check the `url` value, denoted `"url": "`_`IP_ADDRESS_OR_HOST`_`:`_`PORT_NUMBER`_`"`. Note the colon before the port number. By default, `xmrig-proxy` listens on port `3333`, so the miner should connect to that port. Daemon mining uses `wownerod`'s RPC port, by default port `34568`. If your proxy and daemon IPs are different, check that too.

onesmartfellow

#119
Nov 04, 2021, 12:54 PM
Sorry, still figuring out the nuances of this forum's linkages.  Probably best if I just do this:




How do I check if I found a block **if** I'm mining to xmrig-proxy.

(lost the ability to preview the markdown so apologies if this looks weird)

OSF
Print
Go Up Pages 1 ... 6 7 8 9 10
User actions