[1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]

[jamesg]

last 3 days we have no luck!

Did you notice the 10 days before that....

[aadje93]

guys, you can complain here, but better complain to yourself that you are not using a backup pool setup.

my miners (including the one from p4man puppetmaster setup) is just mining on the backup pool.... until bitminter comes on again.... So i lost no hashing.

[narousberg]

last 3 days we have no luck!

Did you notice the 10 days before that....

I agree that a week ago, it was very good. The average income for the past 10 days 20BTC/day. I was just hoping that this will continue in the future))))

[loshia]

I am not complaining just trying to help. Posting the potential problem.  Besides i think that each one of us shall donate (I am donating) to help the pool stay alive and improve.

[AmDD]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

[davidspitzer]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

Can you have a backup pool in the bitminter client?

[aadje93]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

want a good way to test backup pools in bamt?

make the main pool a wrong url, then it cannont contact it. then restart mining and see what happens .

Works like a charm here

[misternoodle]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

Can you have a backup pool in the bitminter client?

From what I remember, it can't be setup...yet.

[AmDD]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

Can you have a backup pool in the bitminter client?

No clue, Ive only ever used gcminer and BAMT.

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

want a good way to test backup pools in bamt?

make the main pool a wrong url, then it cannont contact it. then restart mining and see what happens .

Works like a charm here

I'll try that, thanks!

[aadje93]

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

Can you have a backup pool in the bitminter client?

No clue, Ive only ever used gcminer and BAMT.

This is the first time Ive ever had a pool fail on me, and apparently I have my backup pool in BAMT setup wrong...

want a good way to test backup pools in bamt?

make the main pool a wrong url, then it cannont contact it. then restart mining and see what happens .

Works like a charm here

btw look at the comments on the pools file, there are multiple setup. Mine is mining 180secs (3 mins) on the backup pool and then trys the main pool again, not working backup again. Its bit network intensive maybe, but that way its mostly mining on the main pool

I'll try that, thanks!

[narousberg]

Pool work again 

[aadje93]

Pool work again 

you are wright my miners are on pool 1 again

[DrHaribo]

Pool is up and running again.

I want to apologize that it was down for so long. I was on a guided tour of Batterie Dietl, german bunkers and coastal guns from WWII. I had only a cellphone and was far from my laptop. Perhaps stupid, but the pool was running smoothly and I thought it would be ok for a couple hours. Took a while before I was back to the laptop and could fix things.

Backup pools is still not implemented in BitMinter client, which of course makes downtime much worse. It is one of the top development priorities now, below supporting ASIC mining speeds better.

Not sure what caused the problem yet. But it may be the bug in cgminer 2.5 and below that we had problems with earlier. If you use cgminer please use the latest (2.6+) version. I am changing the server software to better handle a client bombarding it, but I haven't finished this work yet.

Sorry for the inconvenience.

Edit: Yes, rollntime is implemented, but turned off for all miners except bitminter client and diablominer. I'll turn it on for all miners as soon as I have implemented some defenses against old cgminer versions that can suddenly bombard the server with thousands of getwork requests.

[AmDD]

Pool is up and running again.

I want to apologize that it was down for so long. I was on a guided tour of Batterie Dietl, german bunkers and coastal guns from WWII. I had only a cellphone and was far from my laptop. Perhaps stupid, but the pool was running smoothly and I thought it would be ok for a couple hours. Took a while before I was back to the laptop and could fix things.

Backup pools is still not implemented in BitMinter client, which of course makes downtime much worse. It is one of the top development priorities now, below supporting ASIC mining speeds better.

Not sure what caused the problem yet. But it may be the bug in cgminer 2.5 and below that we had problems with earlier. If you use cgminer please use the latest (2.6+) version. I am changing the server software to better handle a client bombarding it, but I haven't finished this work yet.

Sorry for the inconvenience.

Thanks for all your hard work!

[SgtMoth]

i switched the rest of my miners to bitminter app, no more cgminer....

[P4man]

Pool is up and running again.

I want to apologize that it was down for so long. I was on a guided tour of Batterie Dietl, german bunkers and coastal guns from WWII. I had only a cellphone and was far from my laptop. Perhaps stupid, but the pool was running smoothly and I thought it would be ok for a couple hours. Took a while before I was back to the laptop and could fix things.

Backup pools is still not implemented in BitMinter client, which of course makes downtime much worse. It is one of the top development priorities now, below supporting ASIC mining speeds better.

Not sure what caused the problem yet. But it may be the bug in cgminer 2.5 and below that we had problems with earlier. If you use cgminer please use the latest (2.6+) version. I am changing the server software to better handle a client bombarding it, but I haven't finished this work yet.

Sorry for the inconvenience.

Edit: Yes, rollntime is implemented, but turned off for all miners except bitminter client and diablominer. I'll turn it on for all miners as soon as I have implemented some defenses against old cgminer versions that can suddenly bombard the server with thousands of getwork requests.

Doc, how hard is it to restart the backend? If its just a matter of ssh-ing in to the server and restarting the db or something, maybe you should consider making a "killswitch" and giving one or two trusted users access to it. They may not even need full ssh access, just a trigger. It will not resolve all possible problems of course, but someone else being able to restart the backend could be enough to help you  sleep a bit more easily and not get stressed out just because you leave your laptop for a few hours.

[nomnomnom]

Huh, was it completly down?

Because from here it looks like I was mining on bitminter all the time,
backup pools have no shares listed in cgminer ... hmm.

Oh and I have cgminer 2.4.3 so its probably all my fault lol.
Going to upgrade now

[Isokivi]

Huh, was it completly down?

Because from here it looks like I was mining on bitminter all the time,
backup pools have no shares listed in cgminer ... hmm.

Oh and I have cgminer 2.4.3 so its probably all my fault lol.
Going to upgrade now

One of my rigs hung in there for 2h while others were in backup pools, I guess you got lucky.

[DrHaribo]

Doc, how hard is it to restart the backend? If its just a matter of ssh-ing in to the server and restarting the db or something, maybe you should consider making a "killswitch" and giving one or two trusted users access to it. They may not even need full ssh access, just a trigger. It will not resolve all possible problems of course, but someone else being able to restart the backend could be enough to help you  sleep a bit more easily and not get stressed out just because you leave your laptop for a few hours.

Hmmm. That is an awesome idea, thank you. I will think about a good way to implement this.

Huh, was it completly down?

Because from here it looks like I was mining on bitminter all the time,
backup pools have no shares listed in cgminer ... hmm.

One of my rigs hung in there for 2h while others were in backup pools, I guess you got lucky.

No, it wasn't completely down, but it wasn't accepting new connections. If you were running a miner supporting persistent HTTP connections and that already had a connection it could be able to keep mining perhaps the whole time the pool was having issues. I think by the time I fixed it half the hash power was still there.

[narousberg]

..