Site keeps going down for me D:
What error, if any? Everything works here... |
|
|
|
|
Veldy, I wrote simple watchdog monitoring bitcoind and restarting it when it hangs. Hope it will solve situation till Monday, then I'll compile patched bitcoind.
|
|
|
|
|
OK, I wrote simple watchdog which will restart bitcoind once it crash again, because I'll be out for following two days. This surely helps and I'll definitely compile patched bitcoind on monday.
|
|
|
|
Well, I'm almost sure he only changed his identity and he is still around, watching what happen and discussing major issues with Gavin. He started great project which started to be self-sufficient and now he can be satisfied by looking on us, incognito  . |
|
|
|
|
Well, I understand why are people asking - it really looks weird, I know. But unfortunately it is minor issue which need a lot of time, which I'm currently don't have. I hope people understand this, I'm also fixing that ASAP.
|
|
|
|
|
Please always discuss pool troubles on pool thread - I'm busy and often don't read rest of the forum for many days.
I'm finishing other projects with strict deadlines those days, I'm going to sleep at 5am every day, so for now I'm restarting bitcoind manually every time the hangs happen (it was twice yesteday and once today, but it usually keeps running many days without any problem). It is easier than spending one or two evenings on patching & testing & deploying new version of bitcoind. Those hangs are ugly, but they don't break mining.
|
|
|
|
SYN flooding should be easy for the provider to handle.
...which is also already solved on the server, so this is not an issue. |
|
|
|
My point is that they don't like a DOS attack passing through their network either and will often stop it at their routers. The advantage is that their network is not strained, they have removed the traffic going into your network and taking up your resources and they also [usually] have a better idea how to best stop the attack and not just filter it.
How do they know which traffic is needed and which is not? Currently SYN flooding and similar is solved by pool server itself and the rest of possible attacks are usually application related, so I don't know how Linode can help with this... |
|
|
|
You have business class hosting through your ISP, right? Can't they get a handle on this for you?
Handle what? IP blacklist? I'm completely OK with managing this blacklist for myself. To connection problems - I don't think it is problem on the pool side, because it works without problems for two thousands of workers, only two or three people reported some troubles. It definitely looks like problem of their firewalls, routers etc. I once had similar problems with my router box - I had high packet loss, slow roundtrips. Restarting helped. It's common problem of cheap router boxes... |
|
|
|
Getting a 502 Bad Gateway error on the main page right now, even though my miners can connect fine. Hmmm.
Was fixed in few minutes. I really have to recompile bitcoind for webserver tomorrow... |
|
|
|
Any explanation?
No, this IP isn't in blacklist and I don't know about any connection troubles on server side... |
|
|
|
Maybe slush recently made a change to not allow connections to worker account if one is already "connected"?
No, more miners using same worker account should not lead to connection troubles... |
|
|
|
|
Plese send me your IPs to PM. It's possible that they fall into IP blacklist because of server flooding - I'll check it.
|
|
|
|
|
Is better Mac or Linux?
Somebody prefer instant payouts, somebody prefer score system, somebody prefer anything else.
|
|
|
|
|
'Block #0' is fixed. Long polling - I was quite busy this month until now, I'll continue on pool improvements from next week again.
|
|
|
|
Today's 1.1mil round was really crazy. Hope we will have better luck now . All payments were processed before few minutes, I'm very sorry for troubles. I had suspect for some bug in the payment system, so I stopped transfers until some investigation. Automatic payments are turned on again. |
|
|
|
|
Payouts are currently stopped due to some problems. I'll solve it during day.
|
|
|
|
Yes, I blocked him with iptables, too. Easiest solution. Currently site has rate limiter and iptables blacklist. Can you please create a list of the attackers?
Nice idea, I'll join this effort if fairuser & tycho agree (and I already published the one IP . |
|
|
|
|
Attacker flooding the server had IP 69.72.189.147
|
|
|
|
|
Show Posts
