They were while I brought up some more capacity.
They should be up now though. I'll be replacing some hardware this week to speed things up as well. Someone dropped a ton of workers on the server and it apparently couldn't handle the strain - that's the part I can't test myself unfortunately. Should be ok now though I think, until I can get the new DB server installed and running.
Topic: [1200 TH] EMC: 0 Fee DGM. Anonymous PPS. US & EU servers. No Registration! - page 223. (Read 499781 times)
June 19, 2011, 05:53:49 PM
June 19, 2011, 05:49:58 PM
US server down?
June 19, 2011, 04:59:23 AM
@Inaba,
I suggest you change the thread name, since it isn't attractive. I suggest you change it to something like this
[0% FEES!] EclipseMC | SMS Notification | PayPal payout | EU, USA and PACRIM servers!
Like other pool's thread
In this way you can get more thread view = more workers in EclipseMC = More hash power =
I suggest you change the thread name, since it isn't attractive. I suggest you change it to something like this
[0% FEES!] EclipseMC | SMS Notification | PayPal payout | EU, USA and PACRIM servers!
Like other pool's thread
In this way you can get more thread view = more workers in EclipseMC = More hash power =
June 18, 2011, 10:34:53 PM
Inaba,
If you decide to go opensource with your pool software and setup, I would like to see it. A friend of mine and I are working on creating our own pool, using pushpool and a bevity of custom work for DB and frontend. If you would like to work together, let me know, and we can share information with what we have.
If you decide to go opensource with your pool software and setup, I would like to see it. A friend of mine and I are working on creating our own pool, using pushpool and a bevity of custom work for DB and frontend. If you would like to work together, let me know, and we can share information with what we have.
June 18, 2011, 08:00:05 AM
Shit, the share server is down. I'm getting a Failed to connect, retrying error from like 1 minute now.
https://eclipsemc.com/forums/showthread.php/36-BUG-Failed-to-connect-retrying
EDIT: I can now mine using the US server, it seems that the EU one is down.
EDIT2: Now the US one is down too, trying the PACRIM now.
EDIT3: Can't connect to the PACRIM server.
https://eclipsemc.com/forums/showthread.php/36-BUG-Failed-to-connect-retrying
EDIT: I can now mine using the US server, it seems that the EU one is down.
EDIT2: Now the US one is down too, trying the PACRIM now.
EDIT3: Can't connect to the PACRIM server.
June 17, 2011, 06:56:05 PM
Well, Bahnfire has been helping out but it's mostly me at this point.
I've tried to automate as much as possible so it doesn't require constant interaction from the operator. I've also been considering open sourcing my pool software, but it's fairly complicated and I'm not sure it would be terribly useful to anyone but me without a lot of effort to understand what's going on and the thought processes involved.
As far as some of the things on the list, there's the obvious stuff like:
Graphs (I have been avoiding this because I'm not a statistician so I can only make rudimentary graphs)
Dynamic Mining Signatures - I can't figure what I want specifically for this, so I've been putting it off.
+/- avg per block calc/display
IM integration to go along with Email and SMS alerts, the system will alert you over your favorite IM client.
I'd like to reduce the failed miner spam. I have 28 miners and if something happens to my connection or the pool, I get a deluge of SMS messages.
PPS mode
Adding timezone support for the times displayed, so they are displayed in your chosen timezone instead of UTC
A generate API key button. Currently, a random on is generated when you sign up, but no way to generate a new one randomly, but you can set it to whatever you want.
A payout history
IPv6 support
Lots of other little things.
Right now I am working on finishing up the cheat-proof code - I just pushed the worker half of the code to the work servers with the speed improvements to test it out. If all goes well and it doesn't crash, I will push another update that eliminates the SSLLOOWWW update method I was using to this faster method. Right now, the worker server is doign double duty with the old code and the new code.
I have to rewrite the share processing functions to handle the new data tables and share calculation before I can turn off the old share method (proportional). I hope to have that done tonight or tomorrow at the latest. Then I'll switch off proportional and go to strictly scoring. This will have the drawback of having a potentially wildly inaccurate "estimated payout" number, since the number you get will be dependent on when the round ends... since we never know when that's going to be you can't really calculate a real estimate. It will, however, prevent any pool hopping and increase profits for everyone in the end since the pool hoppers will get zip.
I've tried to automate as much as possible so it doesn't require constant interaction from the operator. I've also been considering open sourcing my pool software, but it's fairly complicated and I'm not sure it would be terribly useful to anyone but me without a lot of effort to understand what's going on and the thought processes involved.
As far as some of the things on the list, there's the obvious stuff like:
Graphs (I have been avoiding this because I'm not a statistician so I can only make rudimentary graphs)
Dynamic Mining Signatures - I can't figure what I want specifically for this, so I've been putting it off.
+/- avg per block calc/display
IM integration to go along with Email and SMS alerts, the system will alert you over your favorite IM client.
I'd like to reduce the failed miner spam. I have 28 miners and if something happens to my connection or the pool, I get a deluge of SMS messages.
PPS mode
Adding timezone support for the times displayed, so they are displayed in your chosen timezone instead of UTC
A generate API key button. Currently, a random on is generated when you sign up, but no way to generate a new one randomly, but you can set it to whatever you want.
A payout history
IPv6 support
Lots of other little things.
Right now I am working on finishing up the cheat-proof code - I just pushed the worker half of the code to the work servers with the speed improvements to test it out. If all goes well and it doesn't crash, I will push another update that eliminates the SSLLOOWWW update method I was using to this faster method. Right now, the worker server is doign double duty with the old code and the new code.
I have to rewrite the share processing functions to handle the new data tables and share calculation before I can turn off the old share method (proportional). I hope to have that done tonight or tomorrow at the latest. Then I'll switch off proportional and go to strictly scoring. This will have the drawback of having a potentially wildly inaccurate "estimated payout" number, since the number you get will be dependent on when the round ends... since we never know when that's going to be you can't really calculate a real estimate. It will, however, prevent any pool hopping and increase profits for everyone in the end since the pool hoppers will get zip.
June 17, 2011, 03:55:43 PM
no, i meant one person alone cannot run a big pool with all those problems andd DDos 
by the way, alot of "miner is idle" the last minutes in eu server!
by the way, alot of "miner is idle" the last minutes in eu server!
June 17, 2011, 03:34:51 PM
i hope you are not alone in all this!
one person pool is just impossible!
You aren't alone :pone person pool is just impossible!
I'm here mining with you
June 17, 2011, 03:32:40 PM
i hope you are not alone in all this!
one person pool is just impossible!
one person pool is just impossible!
June 17, 2011, 01:53:02 PM
I will look into that once I get everything stable and most of the features finished. I still have a giant list of features I plan on adding, it's sitting on my desk (the list) staring and me and mocking me.
Share it with us, so we can give you some little tips EDIT: Read my PM please
June 17, 2011, 01:52:19 PM
I will look into that once I get everything stable and most of the features finished. I still have a giant list of features I plan on adding, it's sitting on my desk (the list) staring at me and mocking me.
June 17, 2011, 01:40:08 PM
Excellent... I tried to code it as carefully as possible without being able to test it!
What about putting some giveaways for miners? Like for the top 10 miners..
That would increase the pool hashrate and many users will join!
June 17, 2011, 01:38:49 PM
Excellent... I tried to code it as carefully as possible without being able to test it!
June 17, 2011, 01:30:02 PM
If you want to force an alert, setup an alert for a failed worker for like 1 minute, then turn off that worker for a minute and it should try to SMS you. I'd set an email alert as well, so you know when it fires the alert.
Works!Miner alert -> Myworkername has failed! Last activity was (putdatehere)
June 17, 2011, 12:54:10 PM
If you want to force an alert, setup an alert for a failed worker for like 1 minute, then turn off that worker for a minute and it should try to SMS you. I'd set an email alert as well, so you know when it fires the alert.
June 17, 2011, 12:10:04 PM
Organofcorti: I am glad the speed is improving. I still have a major speed improvement push to the worker server process that I plan on today and if that doesn't completely solve the PACRIM issue, I have one more thing that I'm fairly certain will fix it, it just adds more complexity and cost to the non-US servers, so I've been avoiding it. Keep it simple and there's less to break!
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Going to test the SMS phone support when a block will get solved Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Could you check the thread I made in the official forum of the pool? Thank you!
June 17, 2011, 12:08:05 PM
Organofcorti: I am glad the speed is improving. I still have a major speed improvement push to the worker server process that I plan on today and if that doesn't completely solve the PACRIM issue, I have one more thing that I'm fairly certain will fix it, it just adds more complexity and cost to the non-US servers, so I've been avoiding it. Keep it simple and there's less to break!
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
Boing: I haven't been able to test the non-US phone SMS support. It *should* work, or at least I have provisions for it to work - but no way to test it. If you could let me know, I would appreciate it. I'm fairly certain the country code is required if you use it on a non-US phone, since it won't know which country to route it to without it.
As far as IPv6 goes, I'm actually looking into that as well. I have about 1% experience with IPv6 so that may be a "I'm going to try it and see" kind of thing - so you'll have to be the one to test it and make sure it's working!
Share validation period will eventually be removed, but not until the pool is a bit bigger, as a failed block right now would be costly to me personally
As far as the servers going down this morning, I think the DB server got overloaded. The changes I'm pushing to the work servers should alleviate some of that, but I will probably eventually need to get a much beefier DB backend server, although it's pretty beefy now so I'm trying to figure out where the bottleneck is.
Okama: The work servers don't respond to ping (it drops ICMP packets) for a couple of reasons, so you won't be able to ping them and get a response.
June 17, 2011, 08:50:48 AM
Hey Inaba, a bit better on pacrim tonight (20:05 to 23:35 AEST)
gpu1: 3 and a half hours on pacrim, poclbm reporting ~ 376 Mhps: 875 shares (expected hashrate=298 Mhps)
gpu2: 3 and a half hours on other pool, poclbm reporting ~ 369 Mhps: 1009 shares (expected hashrate=344 Mhps)
That's about 15% better - whatever you're doing keep it up! Thanks so much for the work you're doing on it. As soon as you have the pacrim wrinkles ironed I'll be fulltime. Also looking foward to your implementation of the anti-pool hopping algo.
Cheers!
gpu1: 3 and a half hours on pacrim, poclbm reporting ~ 376 Mhps: 875 shares (expected hashrate=298 Mhps)
gpu2: 3 and a half hours on other pool, poclbm reporting ~ 369 Mhps: 1009 shares (expected hashrate=344 Mhps)
That's about 15% better - whatever you're doing keep it up! Thanks so much for the work you're doing on it. As soon as you have the pacrim wrinkles ironed I'll be fulltime. Also looking foward to your implementation of the anti-pool hopping algo.
Cheers!
June 17, 2011, 06:56:06 AM
Pointed my 186 MHash/s here!
Little question, will the SMS notifications arrive to my Italian phone? I inserted the prefix in the cellular number but I wanna be sure
Also, remove the share validation period and add IPV6 and this will be the best pool ever!
Little question, will the SMS notifications arrive to my Italian phone? I inserted the prefix in the cellular number but I wanna be sure
Also, remove the share validation period and add IPV6 and this will be the best pool ever!
June 17, 2011, 04:20:39 AM
very nice site! 0% fee is wining 
Jump to: