 Show Posts
|
|
Pages: [1]
|
Site is up. But clicking on my account tab shows this:
SSL connection error
Unable to make a secure connection to the server. This may be a problem with the server, or it may be requiring a client authentication certificate that you don't have.
Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
We are close though. Great work Slush!!!
And now the site is up again, it is looking good but I will wait and not log in until Slush announces that the homepage is safe and sound on this thread. Great work Slush! |
|
|
|
Now, if you don't trust Slush to have a sane scheme for distributing mined blocks according to your contributions until the pool goes back to normal, just go mine somewhere else for a while. No one will think any less of you. Heck, someone is even entitled to have a wacky theory that Slush is using the pool to mine only for himself, what do I know! Mine on your own then for now! But can we please stop spamming this thread with wild rumours, misconceptions about computer security and questions that could damn well have been answered within the thread if the thread itself wasn't spammed with said rumours and questions (negative reinforcement loop?).
Please go and watch TV, play games, work, have a wee, wank off or whatever and let's see when the only person that can bring clarity to all this (Slush) is done with priority number one (getting the pool infrastructure/homepage in order) and can motivate spending time on calming down a bunch a mining loons (myself included).
I read the post you qouted. I wasn't worried until I read this
3. mining is still working and we will be paid by slush per block instad of PPS
And since I didn't find anything else on that I was starting to wonder... I know we are not PPS but I was unsure what method slush will use and since database was down it look like something that is a possibility... Since I'm not on IRC all the time I thought that came from there... About my "Chinese whispers" point made early, Q.E.D.? And you trust "Mr. 15-Posts" enough to go bananas over reading three letters "PPS"? Slush also made a point that he wasn't on IRC and for good reasons. Now, I will just go and do one or more of the things on that list of suggestions I made in my previous post. Because I am quite frankly giving up on stemming the tide of this little gossiping sewing circle you have going on here. |
|
|
|
No the method that slush will use during outage. I know that... I would like to know do we solo mine... I don't think anyone know for sure at this point, but that is beyond the point. Slush has only made a single statement: Pool just found new block. Because database isn't running and shares are not stored, I'll spread blocks mined during database outage to miners who'll continue mining on the pool since the database will be up again.
Now, if you don't trust Slush to have a sane scheme for distributing mined blocks according to your contributions until the pool goes back to normal, just go mine somewhere else for a while. No one will think any less of you. Heck, someone is even entitled to have a wacky theory that Slush is using the pool to mine only for himself, what do I know! Mine on your own then for now! But can we please stop spamming this thread with wild rumours, misconceptions about computer security and questions that could damn well have been answered within the thread if the thread itself wasn't spammed with said rumours and questions (negative reinforcement loop?). Please go and watch TV, play games, work, have a wee, wank off or whatever and let's see when the only person that can bring clarity to all this (Slush) is done with priority number one (getting the pool infrastructure/homepage in order) and can motivate spending time on calming down a bunch a mining loons (myself included). |
|
|
|
Spewing stupid mis-information, especially when you know that you don't know... is not going to make you any friends!
People are restless, and while I can understand them we have so far had discussions on how to sort out the payouts during the outage, conspiracy theories and what-not. Personally, I just don't get why we can't accept that there was a major incident, with potentially major consequences, chill and wait for the man in charge to get things back on track. Currently it looks as if many of us are putting the cart before the horse... Give the man 24 hours and there will be no need to play Chinese whispers, making the thread longer and even harder to follow. @Slush: Thanks for all the time and effort you put into hacking on/maintaining the pool and Bitcoin in general. My little mining operation has been running smoothly all through this mess thanks to you. |
|
|
|
|
I believe I have already done the introduction round once, but it seems that I don't post "enough" to stay away from that blasted minimum post limit (the solution to "newbies" posting annoying and irrelevant messages is to force them to post?) being raised (didn't the limit use to be three posts?). I have a fairly technical understanding of Bitcoin and I tend to read rather than post, so here comes my fifth post so that I can once again post outside the newbie sub-forum (grrr...).
|
|
|
|
Most likely this was some local net issue, because pool was definitely up whole time. I'm using online monitoring from three continents (Europe, America, Asia), I usually receive a sms after one minute of unavailability and I didn't received any report. I was also online during the time and pool was running fine.
bitcoin.cz site is hosted in another country than the pool.
I think you are more likely to be right than I am, having more diagnostics data, experience etc. So I think we'll call it a local issue. I still find it damn odd that it would fail from a network close to the back-bone and from a well-established corporate network at the same time. If you are curious, for some reason, feel free to PM me since I won't disclose the locations and providers on a public forum. |
|
|
|
@slush: Sorry to drag you into this forum and onto a new thread for this one. '^^ Here is all the diagnostics I managed to get while it was down. I was unable to access: * https://mining.bitcoin.cz* http://api.bitcoin.cz:8332* http://api2.bitcoin.cz:8332From two independent locations for about an hour around 9AM UTC. Annoyingly, http://bitcoin.cz worked just fine all the time. I disagree with @tungsten by the way... you have been doing a fine job from my point of view and there is no need to be an arse and throw a fit over a single network failure reported by a single user. @nixu: I am slush-exclusive, ergo, no fall-backs. I am mining for fun, not profit. So I will stick with what works and the people I think deserves some computational power for their pool. |
|
|
|
I am generally a quite one, not much fuss and I am unlikely to be posting much unless things go wrong. I also dislike begging for mercy, but wouldn't it be a lot better if I could put the blasted post below as a reply to the main Slush pool thread instead? https://bitcointalk.org/index.php?topic=128644.0 |
|
|
|
Since... "If you are registering to ask a question, please ask it in the newbies section. Do not wait to ask it just because you must post it in "newbies": the question is very likely to have already been asked. If you don't end up getting good responses, you can ask it again elsewhere after you are established, or you can move the entire topic." I guess I will have to post this here in the "newbie" forum instead of where it belongs: https://bitcointalk.org/index.php?topic=1976.5680Hopefully things will be back to normal soon and enough, and hopefully even sooner I may be allowed to post in the rest of the forum. ^^ |
|
|
|
|
