[ANN][ROI] ROI Coin | CPU Only Solo Mining | 15% POS | 18.07% Term Deposit

[t166err]

Update on cluster...

Had a long conversation with provider regarding the mess that's going on with the connection and they have stated that the problem is "fixed" BUT it's far from fixed. The line is down more than its up so I will be disabling the cluster for the next week or maybe sooner if the line gets sorted. I would rather it be off than guess when its on.

When things are stable again I shall post here.

Happy New Year folks :/

Mic.

[DisasterFaster]

Update on cluster...

Had a long conversation with provider regarding the mess that's going on with the connection and they have stated that the problem is "fixed" BUT it's far from fixed. The line is down more than its up so I will be disabling the cluster for the next week or maybe sooner if the line gets sorted. I would rather it be off than guess when its on.

When things are stable again I shall post here.

Happy New Year folks :/

Mic.

Thanks for the update on this and thanks for your efforts on the cluster!

[Junktroep]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Are you mining in the pool?

Nope I solo mine.
I have a central wallet on a low watt server.
And have 4 machines with 20 treats each mining and getting work of the central wallet server.
All the machines who connect to the central wallet, report blocks found, but since last night everything gets rejected.

If your interested I can send you the central wallet config file and output from a debug windows on a miner.

[DisasterFaster]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Are you mining in the pool?

Nope I solo mine.
I have a central wallet on a low watt server.
And have 4 machines with 20 treats each mining and getting work of the central wallet server.
All the machines who connect to the central wallet, report blocks found, but since last night everything gets rejected.

If your interested I can send you the central wallet config file and output from a debug windows on a miner.

can you search your debug log for the word "error" and see if you can see the reason the blocks are getting rejected..

[Plainkoin]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where. 

PK

[kostepanych2]

What is an advantage of using Cluster Mining Pools http://roicluster.miner-pools.com/ for solo mining in compare with solo mining with my wallet?

[Plainkoin]

What is an advantage of using Cluster Mining Pools http://roicluster.miner-pools.com/ for solo mining in compare with solo mining with my wallet?

Hello,

As I understand it, roicluster.miner-pools.com is down due to network issues that the ISP is handling.  So solo mining on the current version 1.1.2.0 would be best bet at the moment.  If you are running 250+ H/s and have the luck factor, might get a block per day.  Some times 2-3.  I have an i7-3770 that often gets more blocks than my bigger hashers.

https://roi-coin.com/roi-coin-downloads

http://coinspool.cu.cc/ is another pool option.  But there might be an issue going on.  We are currently trying to determine why there is a difference in Hashrates being reported.

Let us know if you have any questions, concerns, anything....  

[maxente]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Are you mining in the pool?

Nope I solo mine.
I have a central wallet on a low watt server.
And have 4 machines with 20 treats each mining and getting work of the central wallet server.
All the machines who connect to the central wallet, report blocks found, but since last night everything gets rejected.

If your interested I can send you the central wallet config file and output from a debug windows on a miner.

Those settings are working in windows ? If yes, please post wallet config file. I have 2 computers on a local network, maybe i can make them to mine on a same wallet.

[DisasterFaster]

What is an advantage of using Cluster Mining Pools http://roicluster.miner-pools.com/ for solo mining in compare with solo mining with my wallet?

In my mind the single biggest advantage with the cluster mine vs. solo mining with the built in wallet miner is when your solo mining hash is just too low to find blocks. In this case the cluster mine may give you a way to actually find blocks even with the lower hash rate.

[Junktroep]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where. 

PK

Could you please tell me how to get the on screen debug output to a log.txt file?

[DisasterFaster]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where. 

PK

Could you please tell me how to get the on screen debug output to a log.txt file?

There will be a file in your wallet folder called debug.log and you can view it as a text file no problem.

[LuckLurker]

I wish I had a ryzen

[DisasterFaster]

I wish I had a ryzen

I have ryzen 1800's and they are not as profitable as my i7 3770's. The i7's give much more bang for the buck.

[Junktroep]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where. 

PK

Could you please tell me how to get the on screen debug output to a log.txt file?

There will be a file in your wallet folder called debug.log and you can view it as a text file no problem.

Cool! Thanks I found the debug.
Here is a portion of the logfile where the block failed to create:

2018-01-01 18:31:40 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:31:42 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:31:42 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:31:43 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2018-01-01 18:31:55 UpdateTip: new best=000005400a98ea88289b7e82d1ee370c0763307c88a72c1aec05e98ba39944d5  height=33224  log2_work=39.161193  tx=57326  date=2018-01-01 18:30:24 progress=0.999963  cache=0.0MiB(163tx)
2018-01-01 18:31:55 Block:CBlockIndex(pprev=0xe5d1da0a0, nHeight=33224, merkle=9a1d2a5b1702f790400f83378d23e80736e5a7830141e2d7709f05c222af83da, hashBlock=000005400a98ea88289b7e82d1ee370c0763307c88a72c1aec05e98ba39944d5, nNonce=15, nTime=1514831424, location=170093, finalcalculation=1050706621)
2018-01-01 18:31:55 Creating Block...
2018-01-01 18:31:55 CreateNewBlock(): total size 1000
2018-01-01 18:31:55 CreateNewBlock(): nfees 0
2018-01-01 18:31:55 Created Block with miningaddress
2018-01-01 18:31:56 sort earnings flag = 1
2018-01-01 18:33:17 UpdateTip: new best=000003defb5d70702d478a84dedcafd76b79af79ad53284e896b6e7fe1a84b70  height=33225  log2_work=39.1612  tx=57327  date=2018-01-01 18:31:58 progress=0.999968  cache=0.0MiB(164tx)
2018-01-01 18:33:17 Block:CBlockIndex(pprev=0xe5d1da140, nHeight=33225, merkle=ebf50339152f52f9261560df3ff1d62b258a86eff5460e1c68d6ab34b06aebda, hashBlock=000003defb5d70702d478a84dedcafd76b79af79ad53284e896b6e7fe1a84b70, nNonce=16, nTime=1514831518, location=114318, finalcalculation=690435665)
2018-01-01 18:33:17 Creating Block...
2018-01-01 18:33:17 CreateNewBlock(): total size 1000
2018-01-01 18:33:17 CreateNewBlock(): nfees 0
2018-01-01 18:33:17 Created Block with miningaddress
2018-01-01 18:33:18 sort earnings flag = 1
2018-01-01 18:33:29 ERROR: ContextualCheckBlock: block height mismatch in coinbase
2018-01-01 18:33:29 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-01-01 18:33:49 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:33:51 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:33:56 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:34:49 ERROR: ContextualCheckBlock: block height mismatch in coinbase
2018-01-01 18:34:49 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-01-01 18:36:03 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:36:07 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:36:08 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2018-01-01 18:36:29 Creating Block...
2018-01-01 18:36:29 DEBUG: TXID: fc29737ec6def0d4b9b1d42e393fa2bd247943d03115f1ae594899f62edea64c nHeight: 33226 nTxFees: 0 vout: 12009798258 TX: CTransaction(hash=fc29737ec6, ver=1, vin.size=1, vout.size=2, nLockTime=33225)
    CTxIn(COutPoint(d1562f18c9, 0), scriptSig=3045022100db29b44733241a, nSequence=4294967294)
    CTxOut(nValue=100.00000000, scriptPubKey=OP_DUP OP_HASH160 c538b15616da)
    CTxOut(nValue=20.09798258, scriptPubKey=OP_DUP OP_HASH160 575250a77c52)

[DisasterFaster]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where.  

PK

Could you please tell me how to get the on screen debug output to a log.txt file?

There will be a file in your wallet folder called debug.log and you can view it as a text file no problem.

Cool! Thanks I found the debug.
Here is a portion of the logfile where the block failed to create:


2018-01-01 18:33:29 ERROR: ContextualCheckBlock: block height mismatch in coinbase
2018-01-01 18:33:29 ERROR: ProcessNewBlock: AcceptBlock FAILED

Okay if you see that exact error once in a while that can be normal. This can happen when 2 miners mine the block at nearly the exact time. One miner gets to win the block and the other miner loses it. If you see this error on every mined block and block after block then this is not normal and we have a problem that needs to be looked into right away. Also you have connection issues showing up in that log. Have you checked your firewall settings to make sure everything is ok there?

[LuckLurker]

I wish I had a ryzen

I have ryzen 1800's and they are not as profitable as my i7 3770's. The i7's give much more bang for the buck.

Oh thanks you've cheered me up. I have a 6700 which im getting 289-302 hps on

[DisasterFaster]

I wish I had a ryzen

I have ryzen 1800's and they are not as profitable as my i7 3770's. The i7's give much more bang for the buck.

Oh thanks you've cheered me up. I have a 6700 which im getting 289-302 hps on

That 6700 will do more than that. Please make sure you are using the -optimineraes=1 flag okay

[Junktroep]

The most important thing you need to check into is that your wallet is on the exact same block as our block explorer. If you are mining blocks and those are being rejected it is very likely you are not on the active chain...

Well, I did a fresh install of the wallet.
Checked the blockchain number in the wallet, checked the blockchain number in the explorer. They were the same.
Turned on the debug in the miner, and checked it was running the correct blockchain number, the one in the wallet +1

But I still get: [2018-01-01 18:18:27] accepted: 0/1 (0.00%), 888.54 hash/s (booooo)
[2018-01-01 18:37:17] accepted: 0/1 (0.00%), 981.51 hash/s (booooo)

So I guess something else must be going on!

Hello,

When you did a fresh install, did you delete all files, except the conf and wallet.dat?  If you go to the wallet, Help > Debug > Peers.  Do you see any peers on a version other than 112 or 113?

If you could also send us your debug log file (dev@roi-coin.com)  Please zip it as it can be a large file.  It would help us get a better picture of what is going on.

Thank you for your patience.  Wouldn't be New Year without a wrench in the works some where.  

PK

Could you please tell me how to get the on screen debug output to a log.txt file?

There will be a file in your wallet folder called debug.log and you can view it as a text file no problem.

Cool! Thanks I found the debug.
Here is a portion of the logfile where the block failed to create:


2018-01-01 18:33:29 ERROR: ContextualCheckBlock: block height mismatch in coinbase
2018-01-01 18:33:29 ERROR: ProcessNewBlock: AcceptBlock FAILED

Okay if you see that exact error once in a while that can be normal. This can happen when 2 miners mine the block at nearly the exact time. One miner gets to win the block and the other miner loses it. If you see this error on every mined block and block after block then this is not normal and we have a problem that needs to be looked into right away. Also you have connection issues showing up in that log. Have you checked your firewall settings to make sure everything is ok there?

Since I did a reinstallation of the wallet, and deleted all the files exept the wallet.dat and the ROICoin.conf
I have had 11 failed found blocks in about 2 hours. So yes, everything I find across those 4 mines are marked as failed, since yesterday evening
In mather of fact I havent had a single Block since yesterday evening, so for about 22 hours not a single successful block found.

I don't know what those connection errors are, but my nat, firewall and windows firewall are good to go ;-)
The miners just connect fine and since last night nothing changed on the firewall or nat config.

I am willing to provide my receiving address in an email, or other means, so you can check I was just solo mining fine.

[LuckLurker]

I wish I had a ryzen

I have ryzen 1800's and they are not as profitable as my i7 3770's. The i7's give much more bang for the buck.

Oh thanks you've cheered me up. I have a 6700 which im getting 289-302 hps on

That 6700 will do more than that. Please make sure you are using the -optimineraes=1 flag okay

Okay I'll give that a go, Is there a command to assign a set number of threads so my computer will be half usable whilst mining. Right now my cpu is at 100% but I want to mine on two cores and have the rest free for web browsing and youtube etc

[Junktroep]

I wish I had a ryzen

I have ryzen 1800's and they are not as profitable as my i7 3770's. The i7's give much more bang for the buck.

Oh thanks you've cheered me up. I have a 6700 which im getting 289-302 hps on

That 6700 will do more than that. Please make sure you are using the -optimineraes=1 flag okay

Okay I'll give that a go, Is there a command to assign a set number of threads so my computer will be half usable whilst mining. Right now my cpu is at 100% but I want to mine on two cores and have the rest free for web browsing and youtube etc

If you want to mine with a certain set of cores you can't do it from withing the wallet shut down the wallet.

You have to make a ROIcoin.conf file with:

rpcuser=mine
rpcpassword=miner
rpcallowip=0.0.0.0/0
rpcport=23110
rpcthreads=40
server=1
daemon=1
gen=0
miningaddress=PUT_YOUR_RECEIVING_ADDRESS_HERE

RPCport = 3377
addnode=99.198.174.212
addnode=188.226.134.103
addnode=178.62.105.207
addnode=46.101.241.241
addnode=46.101.139.91
addnode=52.211.179.241

Save this file in the data directory, if you left it default during install it is in %appdata%\ROIcoin

Next download a miner, you can get one from: http://roicluster.miner-pools.com/

Extract the files and create a bat file for you miner:
roiminer.exe -a hodl -o http://YOUR_IP_ADDRESS_Here:23110 -u mine -p miner -t 4 --coinbase-addr=PUT_YOUR_RECEIVING_ADDRESS_HERE -q

The -t 4 is the number of cores you want to assign, so in your case you would want to change it to 2.