search

vergecurrency / verge

Official Verge Core Source Code Repository :muscle:
https://VergeCurrency.com
MIT License
1.41k stars 394 forks source link

Connected nodes from pool wallet daemon. v 4.01 - 4.02 #708

Closed 0xcore closed 6 years ago

0xcore commented 6 years ago

Hi!

wallet version branch: 80de5df827e6f67c941cb2d15b76bedb6766c911 pool software: yiimp

Is it normal wallet connections to nodes running version 4.01 ? Should the wallet connect only to wallets with the latest version 4.02 ?

Thanks!

xvg_nodes_v2

pool2mine commented 6 years ago

Also running 4.0.2 on Yiimp, same for me, mixed 4.0.1 and 4.0.2 nodes...

justinvforvendetta commented 6 years ago

its ok that 4.0.1 nodes are still connecting. they will all update soon. since all the pools and exchanges are on 4.0.2 the correct chain is being broadcast and there never was much of a fork even though the rules changed. i am confused by how you can be connected to both clearnet and onion nodes at the same time though..

0xcore commented 6 years ago

Can it affect mining or it's not important? Would it be better to disconnect pool from 4.01 nodes?

tor & clearnet nodes. It could be because I have added clearnet nodes in VERGE.conf addnode = X.X.X.X ¿?

jrsikors commented 6 years ago

Mining over Tor is a bad idea ... too much latency. Stick to clearnet nodes only.

0xcore commented 6 years ago

Would it be better to use clearnet branch v4.0.2.0-c66e16d-beta ?

jrsikors commented 6 years ago

that's the right one yes

0xcore commented 6 years ago

it's normal that localhost 127.0.0.1 addresses appear in the peer list?

jrsikors commented 6 years ago

Unsure at the moment ... have you fired up the clearnet branch v4.0.2.0-c66e16d-beta ? I'm wondering if they will go away. Let me know if they still appear after the clearnet branch v4.0.2.0-c66e16d-beta

jrsikors commented 6 years ago

@pool2mine were you on the clearnet branch? Or is your other issue different?

justinvforvendetta commented 6 years ago

if you switch to clearnet from tor, or vice versa, you should delete your peers.dat first.

0xcore commented 6 years ago

Thank's for your quick responses.

I'm testing with clearnet, I only find 8 nodes, is that correct ? Is it necessary to add a list of nodes via addnode ?

I think it would be very interesting to be able to add or remove nodes without having to restart the wallet daemon. Maybe it could be added in future release.

justinvforvendetta commented 6 years ago

sure, more will propagate over time

justinvforvendetta commented 6 years ago

and yes node control will be coming soon

0xcore commented 6 years ago

In case someone wants to change from tor to clearnet. To compile clearnet4.0 branch

git clone https://github.com/vergecurrency/VERGE.git
cd VERGE
git checkout 4.0clearnet
./autogen.sh
./configure
make

delete peers.dat from verge config directory before start daemon.

pool2mine commented 6 years ago

Thanks everyone for the help, i started over on a fresh yiimp install, compiled 4.0 branch as @0xcore posted above, wallet started to sync, but then start finding lots of VVraith:2.1.0 nodes and hangs, start over adding peers for VVraith:4.0.2 manually but after a few minutes got lots of VVraith:2.1.0 and hangs, tried to delete peers.dat and start again but same result, some ideas? about my previous install, i was using tor, can this be the reason for not finding blocks?

0xcore commented 6 years ago

@pool2mine What error can you see in debug.log ?

This is the output from my pool, new clearnet wallet running since last night. Total 8 nodes, first two nodes are 4.0.1, rest 6 nodes 4.0.2 Previous to fork we found some blocks, after fork neither have we been able to find a valid block, after fork only two orphan and nothing else.

./VERGEd getinfo

{
    "version" : "v4.0.2.0-c66e16d-beta",
    "protocolversion" : 90001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 2056118,
    "moneysupply" : 14868703191.96872520,
    "connections" : 8,
    "proxy" : "",
    "ip" : "(edited) Wallet Public IP",
    "pow_algo_id" : 3,
    "pow_algo" : "blake",
    "difficulty" : 15759526.00169134,
    "difficulty_x17" : 15830.17924080,
    "difficulty_scrypt" : 322141.35217378,
    "difficulty_groestl" : 1090841.20726278,
    "difficulty_lyra2re" : 61092.17035077,
    "difficulty_blake" : 15759526.00169134,
    "testnet" : false,
    "keypoololdest" : 1523010692,
    "keypoolsize" : 101,
    "paytxfee" : 0.10000000,
    "errors" : ""
}

./VERGEd getmininginfo

{
    "blocks" : 2056120,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "pow_algo_id" : 3,
    "pow_algo" : "blake",
    "difficulty" : 15759526.00169134,
    "difficulty_x17" : 20712.89562777,
    "difficulty_scrypt" : 322141.35217378,
    "difficulty_groestl" : 1090841.20726278,
    "difficulty_lyra2re" : 55261.21667524,
    "difficulty_blake" : 15759526.00169134,
    "errors" : "",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "pooledtx" : 3,
    "testnet" : false
}

./VERGEd getpeerinfo

[
    {
        "addr" : "118.190.75.66:21102",
        "services" : "00000003",
        "lastsend" : 1523618471,
        "lastrecv" : 1523617434,
        "conntime" : 1523573744,
        "version" : 90001,
        "subver" : "/VVraith:4.0.1/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1844132,
        "banscore" : 0
    },
    {
        "addr" : "138.197.69.53:21102",
        "services" : "00000003",
        "lastsend" : 1523618470,
        "lastrecv" : 1523618468,
        "conntime" : 1523573747,
        "version" : 90001,
        "subver" : "/VVraith:4.0.1/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 1844132,
        "banscore" : 0
    },
    {
        "addr" : "145.239.0.126:21102",
        "services" : "00000003",
        "lastsend" : 1523618464,
        "lastrecv" : 1523618470,
        "conntime" : 1523573748,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054794,
        "banscore" : 0
    },
    {
        "addr" : "145.239.244.73:21102",
        "services" : "00000003",
        "lastsend" : 1523618451,
        "lastrecv" : 1523618470,
        "conntime" : 1523573748,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054794,
        "banscore" : 0
    },
    {
        "addr" : "148.251.3.242:21102",
        "services" : "00000003",
        "lastsend" : 1523618472,
        "lastrecv" : 1523618463,
        "conntime" : 1523573749,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054794,
        "banscore" : 0
    },
    {
        "addr" : "159.89.202.56:21102",
        "services" : "00000003",
        "lastsend" : 1523618471,
        "lastrecv" : 1523618472,
        "conntime" : 1523573749,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054794,
        "banscore" : 0
    },
    {
        "addr" : "176.9.25.79:21102",
        "services" : "00000003",
        "lastsend" : 1523618470,
        "lastrecv" : 1523618465,
        "conntime" : 1523573895,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054800,
        "banscore" : 0
    },
    {
        "addr" : "188.40.78.31:21102",
        "services" : "00000003",
        "lastsend" : 1523618470,
        "lastrecv" : 1523618470,
        "conntime" : 1523575070,
        "version" : 90001,
        "subver" : "/VVraith:4.0.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 2054829,
        "banscore" : 0
    }
]
pool2mine commented 6 years ago

@0xcore what is your actual hashrate? i got to 1.3T and did not get a block in 24 hrs, but i was on TOR, will try this new config to try to get one...

0xcore commented 6 years ago

@pool2mine After fork, 300 Gh/s, 0 blocks. Before fork, 1.5Th/s, 3-4 blocks/day

0xcore commented 6 years ago

707 What would be correct configuration in VERGE.CONF ?

rpcuser = userxxx
rpcpassword = passxxx

rpcport = 20102
port = 21102
rpcthreads = 16?

rpcallowip = 127.0.0.1
listen = 1 
# onlynet = ipv4
maxconnections = 512
timeout = 75000
daemon = 1
algo = blake
server = 1

alertnotify = echo% s | mail -s "Verge alert!" a@b.com
blocknotify = /var/stratum/blocknotify ip_stratum:port coin_id %s
jrsikors commented 6 years ago

I personally don't know the answers, but you can read through some of Justin's responses on https://github.com/vergecurrency/VERGE/issues/694

to see if it gives you any ideas, while you wait on someone else to answer

pool2mine commented 6 years ago

this is what i'm talking about, in both logs, debug.log (on .VERGE) and on blake2s.log i am getting this meesages

on debug.log (~/.VERGE) runCommand error: system(/var/stratum/blocknotify pool2mine.com:5766 561 45aaa79fc446e6e80ff52dec5b04fc5d22382e630fcd5467a390d75f8cea4396) returned -1

on blake2s.log (/var/stratum/config)

00:56:30: XVG 2058042 - diff 11919160.186457949 job 117 to 112/112/112 clients, hash 498016.533/1599762599.894 in 1.5 ms 00:56:50: Verge 2058042 not reporting

any ideas?

0xcore commented 6 years ago

Definitely clearnet has not helped me, stratum is disconnected from the wallet every few minutes. When no xvg job yiimp automatic change to another coin in same algo.

log_stratum

very long response times from wallet.

pool2mine commented 6 years ago

Thanks to @0xcore @justinvforvendetta @jrsikors my pool is running now, averaging 1 block every 20 to 30 hours at 700 Ghs, 2 valid blocks so far, my error message was not related to the wallet, it was related to the blocknotify on yiimp, still working on that, it does not affect mining, just the way things are displayed on the website, changing to clearnet resolved my problem, only found 8 nounces, 6 for 4.0.2 and 2 for 4.0.1, will be happy to help other pool operators, best regards

jrsikors commented 6 years ago

good to know @pool2mine , thanks for offering assistance.

@0xcore -- where are you at with this issue? Is it any better? Or is your last post from a couple days ago still legit ?

0xcore commented 6 years ago

I'm at the same point as 4 days ago. I'm stuck, every day the stratum show "clients with no job" and I have to restart it to connect to the wallet. No blocks after fork, I have tried other coins to discard pool configuration, other coins works, we find blocks.

It is also true that we have lost almost all the miners, currently we are only 150 Ghs, with that little speed we can not do much.

pool2mine commented 6 years ago

@0xcore I haven't seen that error on my logs, but when running YENTEN on my pool my stratum became unstable and showed empty blocks because of running out of resources, 2 days ago I upgraded my VPS to 8 GB ram and 4 CPU Cores, my pool became more stable, I don't need to restart the stratum anymore and I feel that the VERGE error is improving, I still get the error (VERGE NO REPORTING) from time to time but it goes away after 20 minutes, it does not affect my mining and today we found 2 blocks, what kind of hardware at you running? having multiple coins daemons could be eating your resources, upgrading your VPS should be something to consider. hope this helps, Regards

0xcore commented 6 years ago

Thanks! @pool2mine I think that resources should not be my problem. I installed the pool on a load balanced configuration with 9 baremetal servers, 2 haproxy, 2 nginx, 2 mysql, 1 stratums, 2 daemon servers. Coin daemon servers has 4 cores and 8 Gb RAM, SSD, I have destined one of the daemon server to run only the VERGE daemon, there is nothing else running on that machine.

I have other coins setup with blake2s algo and they work well. Despite having a lot of resources, sometimes the verge daemon rpc gives me some timeout error and it takes a long time to respond.

ERROR Operation timed out after 30001 milliseconds with 0 bytes received

jrsikors commented 6 years ago

Sorry I know I'm not offering any real assistance on the issue -- this is beyond my skill set. I know Justin has been super busy the last couple weeks.

Were you ever able to figure this one out ? Or are you still having the same issues you were having 9 days ago essentially?

If you are still having issues and haven't already -- I would also suggest: ~Post on reddit ~hop in the Discord channel , there is a room for Mining discussion

Otherwise you might be stuck waiting for Justin, and no ETA when he will get around to it -- but definitely make sure this is up to date with as much info as possible about your current situation.

pcp1985 commented 6 years ago

Even in the telegram, there is a Verge mining channel where I saw we get an immediate response. "Verge - Mining discussion" is the channel name.

On Fri, Apr 27, 2018 at 3:59 AM, Jeff S notifications@github.com wrote:

Sorry I know I'm not offering any real assistance on the issue -- this is beyond my skill set. I know Justin has been super busy the last couple weeks.

Were you ever able to figure this one out ? Or are you still having the same issues you were having 9 days ago essentially?

If you are still having issues and haven't already -- I would also suggest: ~Post on reddit ~hop in the Discord channel , there is a room for Mining discussion

Otherwise you might be stuck waiting for Justin, and no ETA when he will get around to it -- but definitely make sure this is up to date with as much info as possible about your current situation.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vergecurrency/VERGE/issues/708#issuecomment-384732886, or mute the thread https://github.com/notifications/unsubscribe-auth/AJWN2rZb-CYNnUZ21NjXP0rYgy1z2V8Kks5tsgr_gaJpZM4TSRs- .

-- Cheers PC

goodthebest commented 6 years ago

@pool2mine Could you please share with us a bit as you were successful in getting blocks.

1) Are you using POW or POS in Daemon tab of Yiimp admin?

2) And in Settings Tab, what are checked and unchecked options out of these

'has getinfo' = checked or unchecked 'Has submitblock' = checked or unchecked 'Txmessage' = checked or unchecked

3 verge.conf could you share of course excluding your username, password n ip,

pool2mine commented 6 years ago

@goodthebest here is what i'm doing 1) I'm using POS 2) has getinfo' = checked 'Has submitblock' = checked 'Txmessage' = checked

3) my verge.conf rpcuser=XXXXX rpcpassword=XXXXXXXXXXXXXXX rpcport=5610 rpcthreads=16 rpcallowip=127.0.0.1

onlynet=ipv4

maxconnections=256 daemon=1 gen=0 algo=blake server=1

alertnotify=echo %s | mail -s "Verge alert!" info@clouddatatech.net blocknotify=/var/stratum/blocknotify pool2mine.com:5766 561 %s

I hope this helps, we are not pool operators, we are miners running a private pool and have limited knowledge on running large pools, so far we could only be stable with VERGE, every time i try to add more coins my system becomes unstable, do you know if yiimp can be configured to have multiple stratums on different servers but connected to the same database and frontend? i would like to run separate instances because if one coin fails won't affect the others... Regards

goodthebest commented 6 years ago

@pool2mine Thanks for your response. I'm not sure what is your server configuration but if you remove these from verge.conf and let daemon use default values it will help your server stay stable. Yes, there is load balancing possible it depends on various factors. In the meantime, removing these from verge.conf and from other coin's config might help. rpcthreads=16 maxconnections=256

pool2mine commented 6 years ago

Thanks i will remove those lines and restart the deamon, Regards

pool2mine commented 6 years ago

would like to hear some opinions, i have 2 small farms in different locations, one in south america and the other in north america, they have about the same hash power, i would like to improve the latency time by installing a local server and connect the miners on LAN, i can do these by creating 2 pools, that would be the easy way, but is there a way to integrate 2 stratums to the same pool? i have installed the coin daemons in different servers and they work, then i have separated the stratum to another server and also work, but would like to know if is possible to have 2 servers running the coin daemon + stratum on each mining facility and then have them both connected to another server that runs the DB and frontend.... and how will the show on the pool? will they add the hash power and mine to the same wallet if i use the same wallet.dat on both servers or they will be shown as 2 different coins?