Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 598. (Read 2171065 times)

Still got problem on one me miners will not start for the love of BURST

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   miner.exe
  Application Version:   0.0.0.0
  Application Timestamp:   54492bca
  Fault Module Name:   miner.exe
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   54492bca
  Exception Code:   c0000094
  Exception Offset:   000000000002443e
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   2057
  Additional Information 1:   e0de
  Additional Information 2:   e0de893a2be1f1e91b0348aa3162a656
  Additional Information 3:   a6b6
  Additional Information 4:   a6b642ef68620d23c9e33cb92fa53fb6

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Nice progress being made with the coin. debating to get  60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more.

Nice to see  burst finaly over 100 satoshi lets see 1k next

I've noticed over the last month or so that the difficulty is always much lower at night (Pacific Time Zone (UTC-08:00)). It's been happening so consistently that I doubt its just coincidence. I wonder if there are entities that throw a lot of big data centre mining power at Burst only during off-peak hours. I wonder if they replot the data every time, or just kill the mining program during peak hours so their bosses don't notice...

No problem, thank you for your understanding during these rough times, I will make sure to get everything back in perfect order as soon as I possibly can.

Ok Thanks! 

Pool hasn't found a block in quite a while, payouts have been re-enabled, and the amount you're seeing there is not a scheduled amount to be paid out. That's your current round score.

No one will lose any pay, we just need to make sure all of our miners restart and get connected to the backup pool, then we'll start hitting blocks again.

You can always check the block explorer to see the pool's balance, it will have a balance after hitting a block, then you'll see the payouts happen.

Wow!You are back now.Please,post something funny for us.All our community did missed for your funny monologues.Please tell me what you are still mining with 10 GB solo,or what putting password each time you start wallet is too hard for you.Write something please,just for fun

I have not seen payouts for over 5 hours.

Are the payouts working on the failover server.

My miners have been reset several times to make sure I am mining on the failover server.  My miners show they are mining and no errors.

I see over 1000 coins qued upped for my address ==>  CJNP-KCEQ-6545-2FF4M

 

Yea, we've definitely been through the ringer on this server. Then we finally had everything going perfectly, and this happens. I will say it has nothing to do with the reliability of the actual hardware or the pool anything like that, it's a completely personal reason that this had to come to an end.

Wish I would have known sooner, but it is what it is. I will get a new server up in it's place as soon as I can. But for now we're still okay, the server it's running on now is dedicated hardware on a nice dedicated connection. So we're all good. Just gotta get the miners to restart their miners and reconnect.

Mate who is hosting all this for you. You seem to be quite out of luck with them

-Announcement-


Due to circumstances beyond our control... the main server AND host have to be taken down indefinitely...

What this means for the pool is...

Right now the pool will stay on the failover server, so the miners once they get connected to the failover server, shouldn't notice any interrupts in service. So, in theory there should be no difference for current miners.

If your miner is currently not connected, restart it to get the failover server's IP and get connected.

Once you're connected you're good. From this point, we will continue to use our backup server until I can get a new main server setup and running. I don't expect this to take me that long, but it will take a little time.

I will for now, make some changes to the failover pool and make the payouts start from there, so don't worry everyone, you will get all of your mined coins.


Once I have the new main server up, I will configure the failover setup to the new main IP, and everything will be back up and running, with failover, like it was before.


So, in theory the miners on the pool should only see a few seconds of downtime, enough for them to restart their miners, and connect to the failover IP, then await me getting the new server up and running.

I am sorry for the inconvenience, and I will let everyone know when the situation has been resolved. Thank you!

here is an example of the script batch file I used to restart automatically every 5000 seconds... This was using Uray's miner, but you can replace the line with burst-miner.exe with the line that starts the java miner, and it will work the same for that...


@echo off
timeout 3
:mine
echo Mining for howevermany min calc, after that the miner will restart.
start burst-miner.exe
timeout 5000
taskkill /IM burst-miner.exe
goto mine

Which sets of commands should restart cmd on windows automaticaly

Just so that everyone knows, right now burst.ga is running on it's backup server, so be sure to restart your miners to reconnect, and setup a restart script, or restart them every so often so that they will go back to the main server when it's back on line. Thanks!

Or, just run Blago's miner, which I will be switching to soon, because it automatically picks up the change in IP, awesome.

waiting for this feature !!! ;-)

4*1024*1024, but blocktime is 4 min, so /4 = about 1M/min.

OP has a link to calculator

How many coins do you make pr day from those 33TB?

ok im staying, your reward is still there to grab ?

(just asking before I take screenshots...)