[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 569.

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: rotzbouf on March 02, 2017, 06:58:27 AM

Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.

Will change the connect line into addnode and try again.

Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.

Great to hear =) Hopefully everybody is back on the blockchain again now =D

rotzbouf

member

Activity: 112

Merit: 10

Well, purging data folder means delete all content except wallet.dat and magi.conf from the ~/.magi folder.

Will change the connect line into addnode and try again.

Edit: Ok the connect command seems to be the problem. After changing connect into addnode in my config, it starts syncing again.

Visi0n4ry

newbie

Activity: 24

Merit: 0

Quote from: rotzbouf on March 02, 2017, 05:15:07 AM

Having some sync issues with the wallet. I tried already to purge the data folder for a full resync but now I am stuck at block 0.
I have put the below to my conf.

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

What exactly do you mean with "I tried already to purge the data folder", you need to close the Wallet and delete "blocks" "database" "peers.dat" NOT wallet.dat go to your config and put

Code:

addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc

into it, save exit.

Go to http://coinmagi.org/bin/block-chain download m-block-chain.zip and unzip "blocks" and "database" into your wallet folder.

Start wallet, now it should recync the last few blocks.

rotzbouf

member

Activity: 112

Merit: 10

Having some sync issues with the wallet. I tried already to purge the data folder for a full resync but now I am stuck at block 0.
I have put the below to my conf.

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

111magic

legendary

Activity: 1750

Merit: 1005

Quote from: starmman on March 01, 2017, 02:57:03 AM

There was some great volume on XMG overnight - I'm loving that kind of volatility

Me also. Its very good for Magi to get some great volume.

th3.r00t

sr. member

Activity: 312

Merit: 250

I've notice that the price info disappeared from wallet from about 2 days.

Also the wallet isn't staking from atleast 10 hours

Code:

getmininginfo
{
"blocks" : 1220363,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 2.04336221,
"proof-of-stake" : 0.01807929,
"search-interval" : 1
},
"blockvalue" : {
"difficulty-V2" : 3.18456382,
"blockvalue" : 2.77791977
},
"netmhashps" : 44.34277312,
"netstakeweight" : 928195.69517220,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 17615,
"maximum" : 0,
"combined" : 17615
},
"Expected PoS (hours)" : 1,
"stakeinterest" : 0.03125170,
"testnet" : false,
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 44342773,
"testnet" : false
}

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: Visi0n4ry on March 01, 2017, 06:38:19 AM

Thank you for your quick answers!
Unfortunately i already followed starmman and did the resync.
But maybe this will help others with the same problem, also it would be interesting to know how this happened.

Indeed it was really good to see some alternative ways of debugging the wallets - I like this forum - I'm learning more each day

Visi0n4ry

newbie

Activity: 24

Merit: 0

Quote from: starmman on March 01, 2017, 04:33:29 AM

Quote from: Visi0n4ry on March 01, 2017, 04:09:34 AM

[SNIP]

I can upload the debuglog for you if you need.

I had a similar problem before and a full reload of the blockchain with the good nodes in my magi.conf helped me.

Quote from: joelao95 on March 01, 2017, 05:17:25 AM

Quote from: Visi0n4ry on March 01, 2017, 04:09:34 AM

Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine.

Code:

trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat  61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23  (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat  46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout

I can upload the debuglog for you if you need.

I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash

daemon:

Code:

magid getblockhash 1217757

qt-wallet under console:

Code:

getblockhash 1217757

819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htm

Once this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet:

Code:

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check.

Thank you for your quick answers!
Unfortunately i already followed starmman and did the resync.
But maybe this will help others with the same problem, also it would be interesting to know how this happened.

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: Visi0n4ry on March 01, 2017, 04:09:34 AM

Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine.

Code:

trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat  61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23  (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat  46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout

I can upload the debuglog for you if you need.

I suppose you already tried restarting the wallet. Firstly, see if block 1217757 is on the right chain. A quick verification is to check its hash

daemon:

Code:

magid getblockhash 1217757

qt-wallet under console:

Code:

getblockhash 1217757

819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960 should be the output. Some details of this block: https://chainz.cryptoid.info/xmg/block.dws?819506440fe4287e605022bac64465b36a26d9fc2e0c5d9423f0fe63428a3960.htm

Once this is confirmed, put the following in magi.conf to force connecting with these nodes only (no addnode), then restart wallet:

Code:

connect=104.128.225.215
connect=104.128.225.240
connect=104.128.225.241
connect=104.131.42.100
connect=216.189.144.186
connect=216.189.144.211
connect=216.189.144.212
connect=104.131.42.100
connect=xmg.suprnova.cc

If the above doesn't help, we might consider resync the blockchain; use the block data here: http://coinmagi.org/bin/block-chain. If you can upload the debug.log, I can double check.

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: Visi0n4ry on March 01, 2017, 04:09:34 AM

[SNIP]

I can upload the debuglog for you if you need.

I had a similar problem before and a full reload of the blockchain with the good nodes in my magi.conf helped me.

Visi0n4ry

newbie

Activity: 24

Merit: 0

Quote from: joelao95 on March 01, 2017, 12:19:36 AM

Quote from: Visi0n4ry on February 28, 2017, 09:51:19 AM

Quote from: crackfoo on February 28, 2017, 08:22:43 AM

I'm running the new wallet but I see this error and can't get past the block...

received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work

Also got those issues, always losing connection.

It seems due to connection with misbehaved peers, which are supposed to be disconnected. Pls try to remove peers.dat, add only the following nodes, and restart the wallet:

Code:

addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc

Doesnt help the Wallet cant get across block 1217757, curious is that only 1 Wallet is affected all others run fine.

Code:

trying connection [2a02:8108:8b40:d18:7c2b:c1cd:eab:179c]:8233 lastseen=211.4hrs
Added 618 addresses from 104.207.149.217: 9 tried, 9591 new
Added 659 addresses from 104.207.149.217: 9 tried, 9562 new
Added 334 addresses from 104.207.149.217: 9 tried, 9568 new
connection timeout
connection timeout
trying connection 87.78.184.144:8233 lastseen=66.4hrs
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection 97.102.77.41:8233 lastseen=5.1hrs
connection timeout
trying connection 190.142.243.32:8233 lastseen=156.6hrs
received block d6cf05d12962e8050414
ProcessBlock: ORPHAN BLOCK, prev=000000001a3ae11324ab
received block 000000001a3ae11324ab
ProcessBlock: ORPHAN BLOCK, prev=000000002ab5124acfec
received block 000000002ab5124acfec
ProcessBlock: ORPHAN BLOCK, prev=4ecb39f3529c09caee2e
received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
trying connection 2.236.133.147:8233 lastseen=89.7hrs
connection timeout
trying connection 84.215.7.210:8233 lastseen=1.1hrs
Flushed 9577 addresses to peers.dat  61ms
connection timeout
trying connection 46.188.1.45:8233 lastseen=1.1hrs
connection timeout
trying connection 37.214.136.230:8233 lastseen=44.6hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
socket no message in first 60 seconds, 0 1
disconnecting node 104.131.42.100:8233
connection timeout
trying connection 37.47.104.190:8233 lastseen=673.3hrs
connection timeout
trying connection 87.212.198.241:8233 lastseen=1.1hrs
connection timeout
trying connection 187.78.19.191:8233 lastseen=67.9hrs
connection timeout
trying connection 188.66.69.56:8233 lastseen=1.1hrs
connection timeout
trying connection 220.214.11.117:8233 lastseen=121.0hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
received block 0dcaf99ecad91eb3f70b
ProcessBlock: ORPHAN BLOCK, prev=d6cf05d12962e8050414
connection timeout
trying connection 95.42.179.205:8233 lastseen=1.1hrs
connection timeout
trying connection [2601:196:8901:898a:51c1:337c:5f7d:68fa]:8233 lastseen=177.7hrs
connection timeout
trying connection 89.204.155.43:8233 lastseen=890.8hrs
connection timeout
trying connection 154.119.225.5:8233 lastseen=1.1hrs
connection timeout
trying connection 96.248.122.64:8233 lastseen=6.2hrs
connection timeout
trying connection 24.140.248.78:8233 lastseen=1.1hrs
connection timeout
trying connection [2a06:8ec0:3::1:28e6]:8233 lastseen=2.3hrs
connected [2a06:8ec0:3::1:28e6]:8233
send version message: version 71051, blocks=1217757, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:8233, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
Added time data, samples 9, offset -22 (+0 minutes)
nTimeOffset = -23  (+0 minutes)
Moving [2a06:8ec0:3::1:28e6]:8233 to tried
receive version message: version 71051, blocks=1219032, us=[2003:c3:a3c3:7700:71bd:fbe5:cf03:5005]:50836, them=[2a06:8ec0:3::1:28e6]:8233, peer=[2a06:8ec0:3::1:28e6]:8233
trying connection 104.251.215.107:8233 lastseen=0.3hrs
connected 104.251.215.107:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.251.215.107:8233, peer=104.251.215.107:8233
received block 0000000003025a87a9cc
ProcessBlock: ORPHAN BLOCK, prev=0dcaf99ecad91eb3f70b
trying connection 46.188.1.45:8233 lastseen=1.1hrs
trying connection 104.128.225.215:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
Added 619 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9764 new
received block 0000000017106db73b6d
ProcessBlock: ORPHAN BLOCK, prev=0000000003025a87a9cc
Added 639 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9894 new
connection timeout
Added 332 addresses from 2a06:8ec0:3::1:28e6: 10 tried, 9940 new
trying connection 104.128.225.240:8233 lastseen=385654.5hrs
connection timeout
trying connection 91.155.183.83:8233 lastseen=1.1hrs
connection timeout
trying connection 104.128.225.241:8233 lastseen=385654.5hrs
Added time data, samples 10, offset -24 (+0 minutes)
receive version message: version 71041, blocks=1219033, us=87.157.60.239:63622, them=104.251.215.107:8233, peer=104.251.215.107:8233
Flushed 9950 addresses to peers.dat  46ms
connection timeout
trying connection 197.253.33.170:8233 lastseen=1.1hrs
connection timeout
trying connection 104.131.42.100:8233 lastseen=385654.5hrs
connected 104.131.42.100:8233
send version message: version 71051, blocks=1217757, us=87.157.60.239:8233, them=104.131.42.100:8233, peer=104.131.42.100:8233
trying connection 178.33.228.14:8233 lastseen=385654.5hrs
received block 0000000027ba1ac55030
Misbehaving: 110.11.227.163:8233 (0 -> 100) DISCONNECTING
disconnecting node 110.11.227.163:8233
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout

I can upload the debuglog for you if you need.

starmman

legendary

Activity: 1484

Merit: 1029

There was some great volume on XMG overnight - I'm loving that kind of volatility

joelao95

legendary

Activity: 1190

Merit: 1009

Coin of the Magi!

Quote from: Visi0n4ry on February 28, 2017, 09:51:19 AM

Quote from: crackfoo on February 28, 2017, 08:22:43 AM

I'm running the new wallet but I see this error and can't get past the block...

received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work

Also got those issues, always losing connection.

It seems due to connection with misbehaved peers, which are supposed to be disconnected. Pls try to remove peers.dat, add only the following nodes, and restart the wallet:

Code:

addnode=104.128.225.215
addnode=104.128.225.240
addnode=104.128.225.241
addnode=104.131.42.100
addnode=216.189.144.186
addnode=216.189.144.211
addnode=216.189.144.212
addnode=104.131.42.100
addnode=xmg.suprnova.cc

IncludeBeer

legendary

Activity: 1164

Merit: 1010

I'm having issues mining. It seems I'm not getting new work when I should be:

my config:

Code:

C:\Miners\wolf-m7m-cpuminer-V2-x64-0204\minerd-x64-corei7.exe -a m7mhash -t 12 -s 2 -o stratum+tcp://mining.m-hash.com:3334 -u satasnotreal.CPU -p derpy

Any ideas how to fix this?

Visi0n4ry

newbie

Activity: 24

Merit: 0

Quote from: crackfoo on February 28, 2017, 08:22:43 AM

I'm running the new wallet but I see this error and can't get past the block...

received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work

Also got those issues, always losing connection.

rotzbouf

member

Activity: 112

Merit: 10

Quote from: starmman on February 28, 2017, 07:54:17 AM

Quote from: goldlabel on February 28, 2017, 06:52:21 AM

We are now at 958 likes Grin

, so go to https://www.facebook.com/CoinMagi/ Like us and place your walletadress at the 1000 like post and maby you are the 1000 xmg winner Wink

.

I'd forgotten about the 1000 likes campaign, not far away now - how to get the word out there to more people?

Liked. Good that I didn't missed this one.

crackfoo

legendary

Activity: 3570

Merit: 1126

I'm running the new wallet but I see this error and can't get past the block...

received block 0000000027ba1ac55030
Misbehaving: 62.210.252.207:8233 (0 -> 100) DISCONNECTING
disconnecting node 62.210.252.207:8233
ERROR: ProcessBlock() : block with too little proof-of-work
received block 0000000027ba1ac55030
Misbehaving: 104.222.96.36:8233 (0 -> 100) DISCONNECTING
disconnecting node 104.222.96.36:8233
ERROR: ProcessBlock() : block with too little proof-of-work

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: goldlabel on February 28, 2017, 06:52:21 AM

We are now at 958 likes Grin

, so go to https://www.facebook.com/CoinMagi/ Like us and place your walletadress at the 1000 like post and maby you are the 1000 xmg winner Wink

.

I'd forgotten about the 1000 likes campaign, not far away now - how to get the word out there to more people?

goldlabel

hero member

Activity: 575

Merit: 502

We are now at 958 likes Grin

, so go to https://www.facebook.com/CoinMagi/ Like us and place your walletadress at the 1000 like post and maby you are the 1000 xmg winner Wink

.

starmman

legendary

Activity: 1484

Merit: 1029

Quote from: joelao95 on February 27, 2017, 10:10:36 PM

Quote from: starmman on February 27, 2017, 01:02:27 PM

I just completed my first successful - fully automated Magi transaction =) exciting stuff.

Curious what you got?

I've written my own winforms based crypto forex client which can connect into multiple API's (currently only implements polo) - has most the features of a web based exchange, added in some basic trigger based trading algorithms which do exactly what I've been doing manually, and notifications once trades have completed, I've not optimised the routines yet (will write a back trace system) but manged four trades overnight which I previously would have missed. I'll post some screenshots later if I work out how =)

Topic: [ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay] - page 569. (Read 2376034 times)