Profitability on AWS is very low right now. I shut all mine down. I hope people are doing their math or they will be in for a surprise when they get that bill. It's easy to get carried away trying to mine.

Quote from: doesntmatter on November 14, 2013, 07:30:37 PM
what do you mean? if you gave then the code, they import right into virus!
i have sent email to aws to see if they will remove the virus get address...
but that won't stop the prolly 100k machines that ARE MINING YOUR CHAIN!!!
if there's no point to mining, or even having a wallet, when 8/10th STOLEN!!!
I GUESS WHAT I AM ASKING IS are you in on it, or does pts keep running on 100k botnet...
BEEEEER seems to be only pool left... and gets like 5 blocks for every hundred...
somewhere the botnet is still hashing...

So, you letting them steal your futures?

Where are you getting this info that 100k machines are from a botnet? Wondering where to look to verify this.

And it's back. Maybe just an upgrade.

Probably because bytemaster released a coyote miner for solo mining. Now some solo miner (not him) is likely trying to dos ypool. That seems to be the pattern after a new miner comes out, use it and dos the 2nd player.

pool down?

@Bytemaster, What is the difference between protoshares and ipocoins?

I was under the impression that there would be 2 million protoshares & then (21-2) 19 million bitshares. How do ipocoins fit in? What is the progression of everything that will be mined up through bitshares?

Quote from: tyeken8 on November 13, 2013, 03:30:51 AM

Quote from: rando on November 13, 2013, 03:24:43 AM
Anybody know why the linux miner crashes/recovers so poorly?

When it goes down (b/c of the pool being inaccessible, etc) even supervisor cannot get it back up again. It's like the process hangs. I have to manually kill the PID and restart again. I wish I could get supervisor to bring it back up again successfully (like I can with the other miners).

update your code, this issue has been fixed 2 hrs ago.

Thank you

Anybody know why the linux miner crashes/recovers so poorly?

When it goes down (b/c of the pool being inaccessible, etc) even supervisor cannot get it back up again. It's like the process hangs. I have to manually kill the PID and restart again. I wish I could get supervisor to bring it back up again successfully (like I can with the other miners).

And that explains why the miner is crashing

Quote from: m0rph on November 13, 2013, 03:19:22 AM
Pool seems to be down. Also showing down on isup.me

And that explains why my miner is crashing.

Quote from: tyeken8 on November 13, 2013, 12:15:28 AM

Quote from: rando on November 12, 2013, 10:24:23 PM
@yago, When I run it, it connects successfully and says it logged in, but then says "Illegal instruction (core dumped)" and exits. Would you know why?

I have tried:

make CFLAGS="-O3 -march=native"
make CFLAGS="-O3 -march=corei7"
make CFLAGS="-O3 -march=generic"
make CFLAGS="-O3"

All create a binary that gives the same error.

Intel Xeon - 64 bit Linux Ubuntu

Try make CFLAGS=-g and run it with gdb until it crashes, then give me a backtrace.

Thanks. But I already got it. I just used a new machine. :) Then this one worked: make CFLAGS="-O3 -march=native"

Quote from: MessyCoin on November 12, 2013, 10:56:58 PM
Hi. Does this miner allow for solo mining? Pointing to 127.0.0.1 it connects but doesn't mine at all. Everything's set up for solo mining, just wondering if there is a reason it won't work. thanks!

Could you do a post or thread on how you solo mine with this please? I'm interested to learn how one can solo mine without directly using the main protosharesd client.

Quote from: yago on November 12, 2013, 10:35:44 PM

Quote from: rando on November 12, 2013, 10:24:23 PM
@yago, When I run it, it connects successfully and says it logged in, but then says "Illegal instruction (core dumped)" and exits. Would you know why?

I have tried:

make CFLAGS="-O3 -march=native"
make CFLAGS="-O3 -march=corei7"
make CFLAGS="-O3 -march=generic"
make CFLAGS="-O3"

All create a binary that gives the same error.

Intel Xeon - 64 bit Linux Ubuntu

Sorry but I don't know why that binary fails on your server.
Are you using a virtual machine?

Try to reboot if possible.

Found this using google, maybe it works for you:

Code Select Expand


try setting the following prior to building:
$ export C_INCLUDE_PATH=/usr/include/x86_64-linux-gnu

That didn't work. I must have screwed up the machine trying to get wine to work earlier. I started with a fresh machine and it's running well.

Thanks.

Is >512mb per thread supported in your version?
Edit: Nope. it's not yet. "unknown option"

@yago, When I run it, it connects successfully and says it logged in, but then says "Illegal instruction (core dumped)" and exits. Would you know why?

I have tried:

make CFLAGS="-O3 -march=native"
make CFLAGS="-O3 -march=corei7"
make CFLAGS="-O3 -march=generic"
make CFLAGS="-O3"

All create a binary that gives the same error.

Intel Xeon - 64 bit Linux Ubuntu

Quote from: Nuddi on November 12, 2013, 09:47:12 AM
Is there any problems with having several miners on the same payoutaddress? Just put 9 rigs on the same.....

No. It's fine. He mentioned this a page or two back.

Quote from: swknight on November 12, 2013, 05:06:36 AM
how do you overwrite the default setting of using all cores? I read you mentioned it somewhere but I failed to find that post again. Something like change the 3rd line or something. -_-

Add a number after the address

./coyote_miner <pools ip address> <address> 8