Bitcoin Forum
December 10, 2016, 06:54:42 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 [91] 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 ... 376 »
  Print  
Author Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff]  (Read 776162 times)
WhitePhantom
Sr. Member
****
Offline Offline

Activity: 349



View Profile
September 29, 2012, 07:01:41 AM
 #1801

The site's down, but my miners are still running fine.

Back up again. There's a problem with the web server. It locks up randomly with no error message and becomes completely unresponsive. So it's a bit difficult to figure out what the problem is. I'll keep a watch on it and see if I can find out what's going on. Sorry for the instability. Sad

You're the man Doc.  Your efforts are appreciated by us all.
1481396082
Hero Member
*
Offline Offline

Posts: 1481396082

View Profile Personal Message (Offline)

Ignore
1481396082
Reply with quote  #2

1481396082
Report to moderator
1481396082
Hero Member
*
Offline Offline

Posts: 1481396082

View Profile Personal Message (Offline)

Ignore
1481396082
Reply with quote  #2

1481396082
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481396082
Hero Member
*
Offline Offline

Posts: 1481396082

View Profile Personal Message (Offline)

Ignore
1481396082
Reply with quote  #2

1481396082
Report to moderator
loshia
Legendary
*
Offline Offline

Activity: 1372


View Profile
September 29, 2012, 07:21:45 AM
 #1802

The site's down, but my miners are still running fine.

Back up again. There's a problem with the web server. It locks up randomly with no error message and becomes completely unresponsive. So it's a bit difficult to figure out what the problem is. I'll keep a watch on it and see if I can find out what's going on. Sorry for the instability. Sad

You're the man Doc.  Your efforts are appreciated by us all.
+1

Please help the Led Boy aka Bicknellski to make us a nice Christmas led tree and pay WASP membership fee here:
https://bitcointalk.org/index.php?topic=643999.msg7191563#msg7191563
And remember Bicknellski is not collecting money from community;D
DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
September 29, 2012, 10:02:21 AM
 #1803

Thanks, guys Smiley

Sorry, had to restart the mining backend just now. A memory leak is causing slow response after it's been running a couple of days.

I'll be working on that memory leak today, and also the issue with the website locking up.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
squid
Member
**
Offline Offline

Activity: 112


View Profile
September 29, 2012, 06:19:36 PM
 #1804

Can't wait for ASICS so I can park them on this server Cheesy
willphase
Hero Member
*****
Offline Offline

Activity: 770


View Profile
September 30, 2012, 09:10:55 PM
 #1805

Thanks, guys Smiley

Sorry, had to restart the mining backend just now. A memory leak is causing slow response after it's been running a couple of days.

I'll be working on that memory leak today, and also the issue with the website locking up.


perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

Will

DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
September 30, 2012, 09:57:49 PM
 #1806

Can't wait for ASICS so I can park them on this server Cheesy

Something tells me I better get the server ready for some big miners.  Grin

perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

I fixed the memory leak in the mining backend. Hopefully it can sit there for a while now without requiring any more restarts or work.

Made some changes just now to the web application as well. Hopefully it will fix the issue with it locking up.

If there is still a problem I'll have a look at writing a script to detect when the website is unresponsive and automatically restart it.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
hahahafr
Sr. Member
****
Offline Offline

Activity: 241



View Profile
October 02, 2012, 04:59:29 AM
 #1807

Can't wait for ASICS so I can park them on this server Cheesy

Something tells me I better get the server ready for some big miners.  Grin

perhaps worth just setting the frontend to reboot every so often until you resolve the issue - it seems to go down quite a lot.

I fixed the memory leak in the mining backend. Hopefully it can sit there for a while now without requiring any more restarts or work.

Made some changes just now to the web application as well. Hopefully it will fix the issue with it locking up.

If there is still a problem I'll have a look at writing a script to detect when the website is unresponsive and automatically restart it.

Was the memory leak coming from the 0.7 bitcoind daemon?

Fortega
Full Member
***
Offline Offline

Activity: 155

bitcoinAdd.net


View Profile WWW
October 02, 2012, 09:44:40 AM
 #1808

I'm currently having a problem with the client:

Everything looks fine, I'm mining at a normal rate, and suddenly a popup comes up, saying 'wrong username or password'. I press ok, and everything goes back to normal.
A few minutes later, this repeats...

Anybody else with this problem? What can I do? Strange thing is the password is not wrong, as I just press ok and the mining continues (for about 5 mins)


Logs:
2012.10.02 [11:46]  Warning - slow network or server. Request took 52 sec.
2012.10.02 [11:46]  Work rejected. Server says: Duplicate proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 43 sec.
2012.10.02 [11:46]  Warning - slow network or server. Request took 66 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 68 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:48]  Warning - slow network or server. Request took 22 sec.
2012.10.02 [11:50]  Request failed: bad credentials

DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
October 02, 2012, 09:53:18 AM
 #1809

Was the memory leak coming from the 0.7 bitcoind daemon?

No, it was my own code. I reworked the data structures to increase parallelism. Accidentally ended up with proofs of work being kept in memory indefinitely. After a couple days the mining backend was lugging around 3.7 GB of proofs of work. Shocked

Everything looks fine, I'm mining at a normal rate, and suddenly a popup comes up, saying 'wrong username or password'. I press ok, and everything goes back to normal.
A few minutes later, this repeats...

Hmm, I only see one failed login from you in the server logs, at 2012-10-01 11:51:05 UTC, which is 22 hours ago as I write this.

Did you change password on a worker recently?

Does it help if you shut down the client and start it fresh again?

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
abeaulieu
Sr. Member
****
Offline Offline

Activity: 295



View Profile
October 02, 2012, 12:39:04 PM
 #1810

... the mining backend was lugging around 3.7 GB of proofs of work. Shocked

That's a lot of proof...  Smiley
testconpastas2
Full Member
***
Offline Offline

Activity: 199



View Profile
October 02, 2012, 04:07:47 PM
 #1811

I'm currently having a problem with the client:

Everything looks fine, I'm mining at a normal rate, and suddenly a popup comes up, saying 'wrong username or password'. I press ok, and everything goes back to normal.
A few minutes later, this repeats...

Anybody else with this problem? What can I do? Strange thing is the password is not wrong, as I just press ok and the mining continues (for about 5 mins)


Logs:
2012.10.02 [11:46]  Warning - slow network or server. Request took 52 sec.
2012.10.02 [11:46]  Work rejected. Server says: Duplicate proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 43 sec.
2012.10.02 [11:46]  Warning - slow network or server. Request took 66 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:46]  Warning - slow network or server. Request took 68 sec.
2012.10.02 [11:46]  Work rejected. Server says: Stale proof of work
2012.10.02 [11:48]  Warning - slow network or server. Request took 22 sec.
2012.10.02 [11:50]  Request failed: bad credentials


I`m having problems with lots of rejectings showing up randomly ( sometimes when a new block starts,  but i couldn't say if its cgminer 2.7.6 or last server modifications.

( i did change cgminer to the same time the server was updated).
I am mining in two servers with 2.7.6 and the rejectings are always in bitminter , this is why Im thinking in some kind of incompatibility (2.7.6 / Bitminter).

anyone with 2.7.6 is having rejecting issues?? 
Thank you.

Bitmessage: BM-2DAetLWJBKWHZoPbNCgg5z8jwaPpDYWwd4
gpg key id:C6EF5CE3
DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
October 02, 2012, 04:37:23 PM
 #1812

2012.10.02 [11:46]  Warning - slow network or server. Request took 52 sec.
2012.10.02 [11:46]  Work rejected. Server says: Duplicate proof of work

Duplicate proof of work is often caused by network issues. Also 52 second delay could also be due to a network problem.

Could you try "ping mint.bitminter.com" at commandline and see how that looks? Packetloss maybe?

I`m having problems with lots of rejectings showing up randomly ( sometimes when a new block starts,  but i couldn't say if its cgminer 2.7.6 or last server modifications.

The time the pool starts building upon a new block is usually the only time you get rejects.

How high a reject percentage are you getting?

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
testconpastas2
Full Member
***
Offline Offline

Activity: 199



View Profile
October 02, 2012, 05:08:15 PM
 #1813

only sometimes, usually i get less than average, i got over 5% but last block i got 38% (over 250 rejecteds of 1300)  and rejecteds didnt't seem to stop till  i had to close and open cgminer in 4 windows.


can a rejected share become valid later??? because i think it was this block and now i only have 98 rejected instead of ~200

Bitmessage: BM-2DAetLWJBKWHZoPbNCgg5z8jwaPpDYWwd4
gpg key id:C6EF5CE3
DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
October 02, 2012, 06:03:11 PM
 #1814

only sometimes, usually i get less than average, i got over 5% but last block i got 38% (over 250 rejecteds of 1300)  and rejecteds didnt't seem to stop till  i had to close and open cgminer in 4 windows.

Sometimes you will see 5% rejected for a moment after a new round starts. This is because rounds always start with rejects, then the accepted proofs of work start to come in.

But 250 rejected out of 1300 proofs of work sounds like something is very wrong. Pool-wide the rejects are pretty low too.

Did you get reject after reject in all 4 separate cgminer instances?

can a rejected share become valid later??? because i think it was this block and now i only have 98 rejected instead of ~200

No, if it went down it must have been because a new round (block) started.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
willphase
Hero Member
*****
Offline Offline

Activity: 770


View Profile
October 02, 2012, 07:01:43 PM
 #1815

blocks from the future?

https://blockchain.info/block-height/201556 placed by BitMinter into blockchain at 2012-10-02 18:49:44 but block timestamp is 2012-10-02 19:02:42 which is actually almost 15 minutes in the future (I am typing this at 19:01)

Confused?

Will


Mobius
Hero Member
*****
Offline Offline

Activity: 957



View Profile
October 02, 2012, 07:14:58 PM
 #1816

blocks from the future?

https://blockchain.info/block-height/201556 placed by BitMinter into blockchain at 2012-10-02 18:49:44 but block timestamp is 2012-10-02 19:02:42 which is actually almost 15 minutes in the future (I am typing this at 19:01)

Confused?

Will



Blockchain.info is not always accurate
willphase
Hero Member
*****
Offline Offline

Activity: 770


View Profile
October 02, 2012, 07:29:45 PM
 #1817


Blockchain.info is not always accurate

This isn't from blockchain.info - this timestamp is obtained from the block header, and the block header is generated by the pool.  In this case, it looks to me that BitMinter must be generating block headers with future timestamps on them, and passing them to pool workers.

Check the block also on blockexplorer http://blockexplorer.com/b/201556 or, you can decode it yourself and view the timestamp manually:

./bitcoind getblock 0000000000000135f985cccb9e7d87af327c85fa75c46d7532ae406a711c21ec

time: 1349204562

--> Tue, 02 Oct 2012 19:02:42 GMT

Will

hahahafr
Sr. Member
****
Offline Offline

Activity: 241



View Profile
October 02, 2012, 07:32:36 PM
 #1818

Well, does it matter?

willphase
Hero Member
*****
Offline Offline

Activity: 770


View Profile
October 02, 2012, 07:47:30 PM
 #1819

Well, does it matter?

no Smiley

More just a curiosity, but if the clock on BitMinter is incorrect and this isn't being done deliberately (I can imagine some reason related to miners that take a long time to submit shares, and a perception that it might be somehow 'better' to have block timestamps in the future rather than the past...?) then this could cause more problems for DrHaribo so he might want to know, clockdrift can cause issues with SSL validation, for example.

Will

DrHaribo
Legendary
*
Offline Offline

Activity: 1974


Bitminter.com Operator


View Profile WWW
October 02, 2012, 08:02:35 PM
 #1820

In this case, it looks to me that BitMinter must be generating block headers with future timestamps on them, and passing them to pool workers.

Yes, this is what roll-ntime is about. Miners are allowed to generate new work to hash by fiddling with the block's timestamp (referred to as "ntime"). This way they don't have to talk to the server several times per second (in the case of fast miners) to get new work. As long as you don't get too far away from actual time this is OK and the block will be accepted by the rest of the bitcoin network.

▶▶▶ Bitminter.com - Your trusted mining pool since 2011.
Pages: « 1 ... 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 [91] 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 ... 376 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!