Page 1 of 1

Status as of Thursday, August 31, 2017

Posted: Thu Aug 31, 2017 9:37 pm
by Steve Sokolowski
Here's a brief status update:
  • The network connectivity issues continue to be a problem for some users. We resolved one issue, where the txqueuelen Linux setting was too small, causing some packets to be dropped. Once it was changed, the percentage of dropped packets in Chris's tests went down to zero from the previous 8%.
  • However, a second issue is still present that causes WAMP disconnects, both internally to our system and externally to users. Chris is continuing to investigate this issue to see if whatever is causing it might be responsible for some users being unable to connect.
  • If the connectivity issues can be resolved, Chris is considering opening 25 new accounts on Saturday at 1:00pm, but we'll see if the system is performing perfectly then or not. If it is, the accounts will be made available first come, first served.

Re: Status as of Thursday, August 31, 2017

Posted: Thu Aug 31, 2017 9:40 pm
by S3KshuN8
Perhaps you should send the current batch of new users through 'boot camp' first?

Re: Status as of Thursday, August 31, 2017

Posted: Fri Sep 01, 2017 4:11 am
by mycide
make new registrators have to through basic training to be able to connect, that would be nice, it feels like kindergarden in the forum chat, and when a 3 year old walks by you with 10 times the machines you got, looks at you and ask you how to i login to my machine? how to i connect? Please..

Yesterday again i got kicked of servers here, about the same time as the day before. and about the same length of time, is it like clockwork this?

Re: Status as of Thursday, August 31, 2017

Posted: Fri Sep 01, 2017 5:20 am
by AvPro
My 2 cent is that more user load should not be introduced until efficiency is back over 98%, just a few hours ago I was getting 80%

Re: Status as of Thursday, August 31, 2017

Posted: Fri Sep 01, 2017 8:10 am
by Steve Sokolowski
The connectivity problems are not related to server load, so allowing new users won't have any effect on them.

We haven't been able to determine why some users have these issues, as we cannot reproduce them. It's possible that the network issues occur somewhere in the middle of the Internet and we are not going through the same routers. Chris continues to look into these issues, but he does not have an ETA as to when, if ever, he'll be able to figure out these connectivity issues.

Re: Status as of Thursday, August 31, 2017

Posted: Fri Sep 01, 2017 10:41 am
by mycide
today again, for the last few hours i been unable to connect to the pool...
if and when it manages to connect back, it takes a very long time for the rigs to be announced on webpage only way of knowing they are running on pool again is looking at rigs ui and see earning tick up.

one things i noticed is that it comes when you restart the machines, i change settings or coin on my L3+s and then i cant get back on the pool.
This is not a rule, but it has happend several times when i do manual restarts, aswell as happening by itself randomly.

rofl, so while i wrote this, my machines were back hashing here, altough not announced. and now they all got kicked off again.

TThis problem is new, it was not here before. when pool was working shit, i had no problems connecting to the pool, since you fixed those issues i been kicked off like this every day, and it seems like every day that goes the time im unable to reconnect grow longer and longer.... still not able to get back on.. today been utter shit.

Update:

Still basically no connection to pool today, so indeed the gradual problem fast grew into completele lock out from PH.
"Socket connect failed: Connection refused" is what my L3+ tells me when i removed the backup pool.