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

Minerclaim not accessible now.

pom-miner is down as well.

Minerclaim has a notice :

Minerclaim has either shutdown or is like a chicken with its head chopped off. Body is running around still while the head is on the chopping block.

OH Great more issues. I'm Seeing the exact same dam thing!!!!!!!!!!!

if it wasn't fucked before its fucked now

Bend over boys and girls we are getting screwed in the ass.

OK! which chain is the correct one?!?!

my wallet is either 540 or 34 blocks behind (it keeps jumping between them)

Is it a case of just wait and see? or a delete the local copy and downloading the chain again?

Linux botnets may be rarer but they do exist. Linux systems also get compromised in other ways and often part of what happens now is a miner gets installed (I saw one mining Monereo like that recently).

Don't worry my rig should be up and running soon again, AND THAN the network will be stable again. 10 MH/s  Noooo just kidding, barely 100KH/s, but wouldn't that be sweet. 

I splited blockchain accidentally. Now I understand how, will try not to do this in future.

LOL irony is her name!!!!!

This network is falling apart.

https://chainz.cryptoid.info/xmg/ on wrong chain

you need to open ports and port forwarding on your router and add the VPS's IP address into the magi.config

i can show my my configs if you want.

Here's how I have mine setup:

But it keeps on saying "stratum_subscribe timed out... retry after 30 seconds"
I've tried mining from one of my remote VPSes, one of my local linux boxes, and from the same computer that the wallet is running on. Am I missing something?

feels so unnerving solo mining cos dont get any feedback if anything is mined or not, etc.

No problems. no point reinventing the wheel if you dont have to and save you alot of work.

Never thought of that, thanks.

couldnt you do a script that just checks the CPU % at certain intervals and posts it to a page or something?

If it's showing hash instead of connect error, it's working. Look at my example.
Bad part is wallet shows nothing unless you get a block. I've been VNCing into all 9 machines to make sure they're still hashing, but I'm going to build a remotely accessible power meter to save me from that. If 1 machine stops mining, drop in power consumption is quite noticeable.

i've set the coinbase in mine

Set up magi.conf as follows:

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
rpcuser=*user*
rpcpassword=*pass*

# Listen for RPC connections on this TCP port:
rpcport=8232

# server=1 to accept JSON-RPC commands
server=1

# listen=1 to accept connections from outside
listen=0

# RPC connection from localhost allowed
# set this to your LAN address range to allow other local machines to connect. * means 0-255 IOW any machine on LAN
rpcallowip=192.168.0.*

# Add nodes to connect to specific peers
#connect=104.128.225.215

# Add nodes to connect to specific peers
addnode=104.128.225.215
addnode=45.35.251.73

# posii=1 to enable PoS staking; default = 0
posii=1

# Transaction under stake with a value greater than the threshold is being splitted
stakesplitthreshold=1000

# Transactions with values less than the threshold will combine into one
stakecombinethreshold=500


Launch your miner with:

C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u *user* -p *pass* --threads 12

this breaks down as follows:
"C:\XMGpoolminerWin64\m-minerd.exe"  *** adjust to path of miner
                                            
-a m7mhash *** for magi mining

-o http://192.168.0.141:8232 *** address and port of wallet server

*user* *** user from magi.conf  don't use any *

*pass* *** pass from magi.conf

--threads 12 *** number of threads you want, no more than 1 per core

Don't forget to open your firewall for incoming connections to your wallet.

No yay or boo when mining solo, what you'll see if all is well is this:

C:\XMGpoolminerWin64>C:\XMGpoolminerWin64\m-minerd.exe -a m7mhash -o http://192.168.0.141:8232 -u ***** -p ***** --threads 12
[2018-05-05 02:06:23] Binding thread 0 to cpu 0
[2018-05-05 02:06:23] Binding thread 1 to cpu 1
[2018-05-05 02:06:23] Binding thread 2 to cpu 2
[2018-05-05 02:06:23] Binding thread 3 to cpu 3
[2018-05-05 02:06:23] Binding thread 4 to cpu 4
[2018-05-05 02:06:23] Binding thread 5 to cpu 5
[2018-05-05 02:06:23] Binding thread 6 to cpu 6
[2018-05-05 02:06:23] Binding thread 7 to cpu 7
[2018-05-05 02:06:23] Binding thread 8 to cpu 8
[2018-05-05 02:06:23] Binding thread 9 to cpu 9
[2018-05-05 02:06:23] Binding thread 10 to cpu 10
[2018-05-05 02:06:23] 12 miner threads started, using 'm7mhash' algorithm.
[2018-05-05 02:06:23] Binding thread 11 to cpu 11
[2018-05-05 02:06:23] No payout address provided, switching to getwork
[2018-05-05 02:06:52] thread 6: 262144 hashes, 9.29 khash/s
[2018-05-05 02:06:52] thread 9: 262144 hashes, 9.26 khash/s
[2018-05-05 02:06:52] thread 11: 262144 hashes, 9.25 khash/s
[2018-05-05 02:06:52] thread 8: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 0: 262144 hashes, 9.20 khash/s
[2018-05-05 02:06:52] thread 4: 262144 hashes, 9.16 khash/s
[2018-05-05 02:06:52] thread 1: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 7: 262144 hashes, 9.10 khash/s
[2018-05-05 02:06:52] thread 3: 262144 hashes, 9.07 khash/s
[2018-05-05 02:06:53] thread 2: 262144 hashes, 8.97 khash/s
[2018-05-05 02:06:53] thread 10: 262144 hashes, 8.82 khash/s
[2018-05-05 02:06:53] thread 5: 262144 hashes, 8.72 khash/s
[2018-05-05 02:06:56] thread 2: 35872 hashes, 9.22 khash/s
[2018-05-05 02:06:57] thread 9: 46314 hashes, 9.35 khash/s
[2018-05-05 02:06:57] thread 6: 46457 hashes, 9.18 khash/s
[2018-05-05 02:06:57] thread 0: 45994 hashes, 9.27 khash/s
[2018-05-05 02:06:57] thread 11: 46261 hashes, 8.99 khash/s
[2018-05-05 02:06:57] thread 8: 45994 hashes, 9.23 khash/s
[2018-05-05 02:06:57] thread 4: 45778 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 1: 45507 hashes, 9.21 khash/s
[2018-05-05 02:06:57] thread 7: 45497 hashes, 9.26 khash/s
[2018-05-05 02:06:57] thread 10: 35265 hashes, 8.72 khash/s
[2018-05-05 02:06:57] thread 3: 45349 hashes, 9.29 khash/s
[2018-05-05 02:06:57] thread 5: 34876 hashes, 9.29 khash/s

If you get message about connect error, make sure wallet is running, check wallet address & port, user & pass, etc.
Also, try running a miner on same machine as wallet by using 127.0.0.1:port , this shoulg get around firewall problems.
Wallet must be in sync for mining to work.