[18 GH] Swepool.net 0% fee proportional, LP, API, SSL!

[innervisi0nn]

well, I see that at least one of you that use phoenix like me was complaining of disconnections..
so I just got home from work and was dismayed to find that both of my machines that were mining here had been disconnected for a long time..let's see:

machine 1: (ubuntu linux, pyopencl, ATI SDD SDK 2.4, phoenix 1.48) was disconnected 4 hrs ago, 2:55 UTC, "Work queue empty, miner is idle."
Okay lets check machine 2:
(win 7, SDK 2.4, phoenix 1.48):  last time on the clock was 3:20 UTC, and then error message:

0 Khash/sec] [2286 Accepted] [95 Rejected] [RPC (+LP)]Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "twisted\internet\defer.pyc", line 361, in callback

  File "twisted\internet\defer.pyc", line 455, in _startRunCallbacks

  File "twisted\internet\defer.pyc", line 542, in _runCallbacks

  File "twisted\internet\defer.pyc", line 1076, in gotResult

--- <exception caught here> ---
  File "twisted\internet\defer.pyc", line 1020, in _inlineCallbacks

  File "minerutil\RPCProtocol.pyc", line 220, in _requestComplete

  File "minerutil\RPCProtocol.pyc", line 166, in parse

minerutil.RPCProtocol.ServerMessage: upstream RPC error

=============================

so, would going to poclbm solve these problems, or is something awry at swepool.

I'm a little bummed. oh well, I know that there are many of you who have better knowledge of automation of these miners....

(the linux multiple pools script looked appealing...)

Im definately on the same boat with you mate.
I've tried all versions of phoenix, tempted to try poclbm but dont have much time to mess around.
Just wish this thing was fixed, all the other pools including deepbit work flawlessly except with swepool which is my favorite pool bah humbug

Im hoping DINOX reads this and tries to fix it.

[1529578296]

1529578296

[1529578296]

1529578296

[ancow]

Tycho over at the deepbit pool mentioned that phoenix won't reconnect in case of connection problems, so while switching to a different miner won't solve the connection problems, it will allow you to continue mining once they're over.

[innervisi0nn]

Tycho over at the deepbit pool mentioned that phoenix won't reconnect in case of connection problems, so while switching to a different miner won't solve the connection problems, it will allow you to continue mining once they're over.

Not sure I understood what you just said...

once phoenix detects a connection failure, it wont reconnect back? What? for me it does, but then it disconnects again.

[bodhipraxis]

also regarding poclbm:
innervisi0n: yeah, i haven't wanted to switch, since the phatk kernel does a little better on my 5870 cards.

but:
on these forums in several places is instructions on how to run poclbm with multiple instances, using the ' -f ' switch so that if the primary one (say swepool, set it at like 92%) goes down, the backup (say deepbit, or any other pool you like, normally at some single digit percentage) will take up the slack.

I have known about this for a few days, like I said there are many people who know way more than I do.

I will hunt down this information in the next hour and post here how to do this with poclbm.

like you, v*, swepool is my favorite.

[innervisi0nn]

ty

[kiwiasian]

No issues with poclbm here

[innervisi0nn]

that looks like msi afterburner hardware monitor..its working with phoenix again

[kiwiasian]

that looks like msi afterburner hardware monitor..its working with phoenix again

Yes, it is. I am showing you that with poclbm I'm not getting disconnected.

[dinox]

Hi guys!

I cant see any problems here, can you please try to ping swepool and see if you got a high ping? That has been a cause before. I know innervisi0n has done this and I think your ping was ok so I cant see the problem there. Is the problem continuous or after some time?

EDIT: I see the problem is not continuous. It may depend on some packets getting lost on their way (We have had this problem before), I'll make further investigations in this.

[kiwiasian]

Lol 40 hour block, yay

[Grike_SixEcho]

53 hour block, WHY

[ancow]

Tycho over at the deepbit pool mentioned that phoenix won't reconnect in case of connection problems, so while switching to a different miner won't solve the connection problems, it will allow you to continue mining once they're over.

Not sure I understood what you just said...

once phoenix detects a connection failure, it wont reconnect back? What? for me it does, but then it disconnects again.

I don't use phoenix, nor am I affiliated with them, so I don't know any details. From what I read, phoenix has problems reconnecting. Whether that means that it doesn't attempt to or simply fails is beyond me. Basically, you may want to look at whatever phoenix threads are in the forum, if you want details.

[kiwiasian]

60 hour block

Glad I did not mine on Swepool today. (or yesterday)

[tohwis]

93 hour block... The hash rate has seemed to drop to only 12Ghash/s

[JA37]

Difficulty is too high for me now. I won't be able to mine any more. I have some bitcents that I've mined. Please send it to the wikileaks account if you don't want to send it to me. My payout address should be registered, or send it to 1HB5XMLmzFVj8ALj6mfBsbifRoD4miY36v which should be WikiLeaks (according to http://wikileaks.org/support.html)

[MikesMechanix]

121h and counting... Hashrate seems to fluctuate a lot between 12 - 18.

[MikesMechanix]

Almost a week now...

[kiwiasian]

Lol are you guys serious?

[Jine]

Pool hashrate 6.69 GHash/s

[crazy987]

pointed my miner to you guys for some time to give ya a hand, its not much but its 150mhash