It seems that my magi.conf file still works. My pool http://104.207.149.217 has the same block number with https://poolinfo.systms.org/. And the Net Hashrate is only 13,520.47 KH/s . The recently found block: 1447973 119 left lervito 08/20/2017 00:56:41 0.6509 43.25 42,661 15,464 36.25 1447970 116 left anonymous 08/20/2017 00:24:22 1.0152 43.25 66,530 69,884 105.04 Rewards at 43.25. Not sure if it is correct or not. Take your own risk to mine. |
|
|
|
This is my conf file. Nothing special. rpcport=8232 daemon=1 server=1 rpcallowip=127.0.0.1 rpcuser=rpcuser rpcpassword=rpcpass gen=0 posii=0 addnode=104.128.225.215 Yep. I just set one node in my conf file and use the compiled magid from Joe. And the pool just found a new block. Payout is temporarily suspended. I did the same for TrasMaMod XMG Pool to, but I decided to also remove IRC. But still it was able to get into a potential fork-chain. Here is the details I have set in my pool wallet config: gen=0
staking=0
posii=0
irc=0
addnode=104.128.225.215 |
|
|
|
Yep. I just set one node in my conf file and use the compiled magid from Joe. And the pool just found a new block. Payout is temporarily suspended. |
|
|
|
|
Is any other coin good for cpu mining now? Any suggestion?
|
|
|
|
|
Pool shutdown. Waiting for a solution.
|
|
|
|
|
Need Joe to make something official.
What should the magi.conf be? If use a different conf, there could be another fork again?
|
|
|
|
Did you change the connect to addnode? It looks another fork happen again? My pool is at block 1446733. And supernova is at 1446595. MinerClaim is at 1446733. It seems my pool and minerclaim are connected. But supernova is on a different fork. |
|
|
|
|
Possible you need remove all other addnode in your original magi.conf. Just keep those connects in the conf file.
|
|
|
|
Not include the two nodes Joe provided? Another split... My pool is at 1444932 block with net hash 50Mh/s, but supernova is at 1445149 block with net hash 106Mh/s. It seems the nodes are not connected. before syncing your wallet with new blockchain, set in magi.conf connect=213.32.21.37
connect=192.99.63.44
connect=89.34.96.133
connect=185.38.149.64
connect=193.124.182.62
connect=172.86.179.30
connect=95.211.186.214
connect=37.48.118.8
connect=37.48.118.9
connect=37.48.80.94
connect=5.79.74.141
connect=5.79.74.142
connect=5.79.74.140
connect=37.48.80.201
connect=95.211.209.73
connect=193.105.134.118
connect=193.105.134.120
this will force your wallet only to these nodes Thanks, I'll try that - I had addnode before |
|
|
|
LOL. At now i cant login to http://104.207.149.217 pool. Registered today. username and password do not match. starngly oops. I backed up the database yesterday and use that database as a start. I have the copy of the old one. I will move those info to the database. Just wait a few minutes. Just moved the new registration information. Should work now. Sorry for that. Need some time to clean the old database. |
|
|
|
I use a new wallet, it works now on http://104.207.149.217. The registration info is kept and other table are truncated for a fresh start. Current height is 1444440. |
|
|
|
|
I will temporarily shut down the pool and use a new wallet to do some test.
|
|
|
|
|
Misbehaving: 182.239.128.11:50250 (0 -> 100) DISCONNECTING
disconnecting node 182.239.128.11:50250
ERROR: ProcessBlock() : block with too little proof-of-stake
accepted connection 86.145.68.129:63996
send version message: version 71051, blocks=1444083, us=104.207.149.217:8233, them=86.145.68.129:63996, peer=86.145.68.129:63996
Added time data, samples 28, offset -1 (+0 minutes)
Moving 86.145.68.129:8233 to tried
receive version message: version 71051, blocks=1446244, us=104.207.149.217:8233, them=86.145.68.129:8233, peer=86.145.68.129:63996
connection from 81.95.126.198:57885 dropped (banned)
received block 0000008b14e2845e0a8c
Misbehaving: 86.145.68.129:63996 (0 -> 100) DISCONNECTING
disconnecting node 86.145.68.129:63996
ERROR: ProcessBlock() : block with too little proof-of-work
connection timeout
ThreadRPCServer method=getinfo
accepted connection 67.173.120.250:44629
send version message: version 71051, blocks=1444083, us=104.207.149.217:8233, them=67.173.120.250:44629, peer=67.173.120.250:44629
Added time data, samples 31, offset -66 (-1 minutes)
nTimeOffset = +0 (+0 minutes)
Added 67.173.120.250:8233 from 67.173.120.250: 28 tried, 1979 new
Moving 67.173.120.250:8233 to tried
receive version message: version 71041, blocks=1447355, us=104.207.149.217:8233, them=67.173.120.250:8233, peer=67.173.120.250:44629
trying connection 90.150.185.182:8233 lastseen=0.2hrs
received block 20c147f37299c555b43e
ProcessBlock: ORPHAN BLOCK, prev=22fd36aec606919c3883
In my pool, the nethash is jus 222kH/s, weird. I guess my pool is on another fork?
|
|
|
|
There seems have a problem with wallet. My pool has different block height with supernova. I redo the fix but still found some problem. It stucks on some block. Do not know what's going on. Just restart to see if I can fix it. |
|
|
|
|
Looks like the network still has problem. My pool shows 1444045 block but supernova shows 1444238. Another fork?
|
|
|
|
Good job, joe! The pool http://104.207.149.217 is back to normal. Cleaned the database to remove the bad blocks. |
|
|
|
|
Show Posts
