Topic: [ANN] New Primecoin Pool + GPU Miner - page 2. (Read 19667 times)

Please don't stop the pool. Ypool is boring...

If you change your mind, I'm happy to help a bit.  I think you've taken some really nice steps forward with your architecture thus far and it'd be cool to see a new pool design succeed.  (Particularly if you were, in the long run, interested in open sourcing parts of the protocol so that others could build upon it).  Getting rid of the hacked up mix of binary gloop and stuff-over-http would be great.

A good place to start is here:

http://www.lognormal.com/blog/2012/09/27/linux-tcpip-tuning/
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.edge.doc%2Fedge%2Fcp%2Fadmingd45.htm

A few are important - tuning time_wait will reduce your susceptibility to grade-school-level TCP attacks such as those that were happening the last few days.  But don't set it to 1 second like those guys did - 10 seconds should be adequate.

echo "1024 61000" > /proc/sys/net/ipv4/ip_local_port_range
echo "10" > /proc/sys/net/ipv4/tcp_fin_timeout
echo 32768 > /proc/sys/fs/file-max

syncookies should already be enabled, but if they're not:

echo 1 > /proc/sys/net/ipv4/tcp_syncookies

and check this page's suggestion for using iptables to rate-limit inbound synfloods:
http://www.liquidcomm.net/news/tech_tips/linux_os/how-to-manage-a-ddos-or-dos-attempt-directed-at-your-linux-server.html

It's very possible that the crash you're seeing from ConnectSocketDirectly is related still to running out of file descriptors or something very similar.  General server scalability tuning might make it disappear. 

http://www.nateware.com/linux-network-tuning-for-2013.html

has a few more - particularly the per-user open file limits, etc.  Don't bother with the congestion window and rmem/etc. stuff in there - your server isn't aiming for high tcp throughput on a single connection.

Doing it all via sysctl config in /etc/sysctl.conf is the most straightforward way to have your changes persist after a reboot.

Instead of releasing a new solo mining fee software, may-be you could release an open source miner and end this shameful madness right now.
You will do a favor to crypto community and you will certainly receive a lot of donation too.
(not mentioning the fact ddosing your pool wasn't really nice and they deserve a lesson)

You know other people might have better luck with the pool. Why not see about working with some one else on the forum? I for one have the $$ resources to help secure it just not the coding knowledge.

Dont kill a pool just because of a few bumps.

That's cool! I am trying to convert the opensource solo xpm miner to pool... may i can start with this..

excellent idea! solo mining  ftw.

now thats funny

You should just use beeeer or another one like it.

good rather it be solo

Can we use this miner to mine primecoins? http://www.coinion.com/2013/12/11/child-labor-bitcoin-mines-exposed/

Shame for the pool, but a solo miner with this speed would be best anyway...and a dev fee is fair I believe.

great for the SOLO MINING!!! Good work

same here

Server is now crashing consistenly. Some bug in bitcoin function ConnectSocketDirectly is causing the issue.

This is just too much, i've been baby sitting this thing for over 48h straight now.

FINAL UPDATE: The pool will close. All balances will be PAID once they are mature. I WILL release a solo miner.

Need to sleep now...

I think it is about stale shares?
I see a lot of them...

Doing a server restart, something aint right...

will it run on 58xx?

PM sent

PM sent..

PM sent