Author

Topic: Not mining first block (Read 249 times)

newbie
Activity: 27
Merit: 0
October 16, 2019, 12:59:08 PM
#3
You need a second rig mining to confirm the block..

On one node using internal miner, And another droplet node using as miner. totally 2 nodes.
newbie
Activity: 3
Merit: 0
October 16, 2019, 01:16:46 AM
#2
You need a second rig mining to confirm the block..
newbie
Activity: 27
Merit: 0
October 09, 2019, 11:01:17 PM
#1
Hello,

For Learning purpose i forked Litecoin 10.4, compiled and daemon running properly, but still first block is not minted more than 20 days gone.

Setup i did is:

Initially 2 nodes (both are Digital Ocean Droplets VMs, 1vCPU, 1GB RAM) for communicating each other.

Got error in main node
Code:
connect() to 157.245.94.144:4991 failed after select(): Connection refused (111)

And mining node is also from Digital Ocean droplet (2vCPU, 2GB RAM). Past 20 days shows hashespersec 0
Code:
getmininginfo
{
    "blocks" : 0,
    "currentblocksize" : 0,
    "currentblocktx" : 0,
    "difficulty" : 0.00024414,
    "errors" : "",
    "genproclimit" : 2,
    "networkhashps" : 0,
    "pooledtx" : 0,
    "testnet" : false,
    "chain" : "main",
    "generate" : true,
    "hashespersec" : 0
}

Some times i get this error also
Code:
socket recv error Connection timed out (110)

Nodes communicating each other properly, did nmap and ping test.

Main node
Code:
sudo netstat -ntlp | grep LISTEN            
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1456/sshd
tcp        0      0 0.0.0.0:4991            0.0.0.0:*               LISTEN      23550/newcoind
tcp        0      0 127.0.0.1:4992          0.0.0.0:*               LISTEN      23550/newcoind
tcp6       0      0 :::22                   :::*                    LISTEN      1456/sshd
tcp6       0      0 :::4991                 :::*                    LISTEN      23550/newcoind
tcp6       0      0 ::1:4992                :::*                    LISTEN      23550/newcoind

What could be the issue, miner is not minting because of low miner CPU (Digital ocean)or any other issue.

Answers Well Appreciated.
Thanks
Jump to: