shads (OP)
|
|
November 23, 2011, 02:10:17 PM |
|
What is the difference between 0.3.X and a Workmaker edition? Also, do i really need the 4diff patch? Cause i am using 0.3.24(I can upgrade if the problem is resolved) on windows, and it would be a pain in the ass to compile Bitcoin(with or without gui) on windows.
The differences are all explained here: https://bitcointalk.org/index.php?topic=51226.0It runs with vanilla bitcoin 0.5.0. I've seen the rpc thread crash in bitcoind a few times in my test environment but I've never heard of it happening in a production environment so it could just be something peculiar to my setup. I do put my poor little bitcoind through some pretty horrible contortions that probably don't happen on a normal pool setup.
|
|
|
|
Remember remember the 5th of November
Legendary
Offline
Activity: 1862
Merit: 1011
Reverse engineer from time to time
|
|
November 23, 2011, 03:43:32 PM |
|
5619 [shared-httpclient-60] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc 5623 [shared-httpclient-60] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc 5627 [shared-httpclient-61] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc [17:41:28.137] [WARN] Bad HTTP response connecting to auxDaemon http://localhost:8335. Work generated from this AuxInfo will not be valid for chain: namecoin. HTTP response code: 401 Dunno what is wrong. Using 0.3.24.64 and get that. Password AND username are correct. WorkMaker edition, pushpool compatibility is OFF
|
BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
|
|
|
|
shads (OP)
|
|
November 27, 2011, 11:15:26 PM |
|
That's fantastic cablepair! I'll put a link to it on the PSJ site and in the other thread. My only suggestion is that you point people to download page rather than linking to the specific versions. I leave the old versions on the server so those links will be valid long after the psj version has incremented.
|
|
|
|
cablepair
|
|
November 28, 2011, 12:02:14 AM |
|
will do, and thats mostly a rough draft I am polishing it up a bit more Also just want to let you know I started from scratch when testing this tutorial to make sure everything worked the way I laid it out I tested on a old dell with a Pentium 4 1.7 Ghz CPU and 256 mb ram and PoolServerJ is mining on both BTC/NMC networks right now with no problems talk about efficiency!
|
|
|
|
pooler
|
|
December 01, 2011, 11:55:50 AM |
|
Any chance PoolServerJ will support difficulties less than 1? I have tried setting it up for Litecoin (current difficulty is about 0.66), but with version 0.4.0rc2 all I get is a bunch of com.google.bitcoin.core.VerificationException: Difficulty target is bad: 40474064220290374717375238241067511033434108403022755503819899011072 at com.google.bitcoin.core.Block.getDifficultyTargetAsInteger(Block.java:582)
|
BTC: 15MRTcUweNVJbhTyH5rq9aeSdyigFrskqE · LTC: LTCPooLqTK1SANSNeTR63GbGwabTKEkuS7
|
|
|
doublec
Legendary
Offline
Activity: 1078
Merit: 1005
|
|
December 01, 2011, 12:33:29 PM |
|
I created a PoolserverJ tutorial
Why do the conf files for bitcoin/namecoin in the tutorial specify "rpcallowip=*". Doesn't this open the JSON-RPC port of the daemon for anyone to connect to? This gives access to 'sendtoaddress' and other commands for sending coins out of the wallet. Or am I missing something?
|
|
|
|
DavinciJ15
|
|
December 01, 2011, 12:48:37 PM |
|
I created a PoolserverJ tutorial
Why do the conf files for bitcoin/namecoin in the tutorial specify "rpcallowip=*". Doesn't this open the JSON-RPC port of the daemon for anyone to connect to? This gives access to 'sendtoaddress' and other commands for sending coins out of the wallet. Or am I missing something? You are correct DoubleC However I do that but I have a firewall and I open up the port to the IP's I trust, in other words IP's I own and control.
|
|
|
|
cablepair
|
|
December 01, 2011, 02:57:49 PM |
|
I created a PoolserverJ tutorial
Why do the conf files for bitcoin/namecoin in the tutorial specify "rpcallowip=*". Doesn't this open the JSON-RPC port of the daemon for anyone to connect to? This gives access to 'sendtoaddress' and other commands for sending coins out of the wallet. Or am I missing something? This is an interesting security concern you bring up and very valid. The idea of the tutorial is to be something for people who really have little or no idea what they are doing. It does not seem very plausible however that there are going to be people out there scanning IP addresses for open RPC ports to that may have used my tutorial. I tried to make it as fool proof as possible thus the reason for the *, people have different network setups and I am trying to eliminate needless problems and the possibility that this could turn into an actual security incident seems very remote to me. I am doing some polishing up soon of this tutorial and I will take this in mind. Thank you.
|
|
|
|
cablepair
|
|
December 01, 2011, 04:26:29 PM |
|
So I thought about it for a sec and your right about the security issue and in that setup it's not needed to allow rpcallowip=* anyways. It's just a habit I got into when helping people to setup pools to skip over needless problems So I finished polishing up the tutorial today http://devtome.org/wiki/index.php?title=How_to_Setup_a_Merged_Mining_Bitcoin_Pool_with_PoolServerJI also included step by step instructions on how to access the database with phpmyadmin and add a worker. Also if anyone would like to see a public pool in action that I setup check out http://pool.devcoin.orgOf course it is for mining devcoins and not Bitcoins.
|
|
|
|
Remember remember the 5th of November
Legendary
Offline
Activity: 1862
Merit: 1011
Reverse engineer from time to time
|
|
December 01, 2011, 05:43:25 PM |
|
This still does not answer my problem.
|
BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
|
|
|
cablepair
|
|
December 01, 2011, 05:45:02 PM |
|
5619 [shared-httpclient-60] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc 5623 [shared-httpclient-60] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc 5627 [shared-httpclient-61] WARN org.eclipse.jetty.util.log - Unknown Security Realm: jsonrpc [17:41:28.137] [WARN] Bad HTTP response connecting to auxDaemon http://localhost:8335. Work generated from this AuxInfo will not be valid for chain: namecoin. HTTP response code: 401 Dunno what is wrong. Using 0.3.24.64 and get that. Password AND username are correct. WorkMaker edition, pushpool compatibility is OFF why not upgrade? I may be able to help you but I need a little more info do you want to send me your config? send to tom@devcoin.org and I will see if anything pops out at me are you using coinbassing? local work generation?
|
|
|
|
g2x3k
Full Member
Offline
Activity: 147
Merit: 100
PooL-X.eu
|
|
December 12, 2011, 04:50:34 PM |
|
have to vote on poolers suggestion it would be nice if worked with diff being lower then 1
|
|
|
|
Furyan
|
|
December 16, 2011, 04:36:38 PM |
|
Has anyone added MS SQL support to PoolServerJ? Because it uses JDBC this should be (almost) trivial as MS SQL is fully ODBC 92 compliant, just wondering if anyone's made the effort to actually write the associated bit of code. I can dive in myself, I'm reasonably proficient in Java but I look to save time where possible Also... shads.. you're outdoing yourself man... I'm very impressed with the built-in coinbasing & work generation now. It eliminates almost all of the custom mods I had made to my version of bitcoind, which lowers my support profile and barrier to upgrades. Really impressed here.
|
|
|
|
DavinciJ15
|
|
December 16, 2011, 05:21:31 PM |
|
Has anyone added MS SQL support to PoolServerJ? Because it uses JDBC this should be (almost) trivial as MS SQL is fully ODBC 92 compliant, just wondering if anyone's made the effort to actually write the associated bit of code. I can dive in myself, I'm reasonably proficient in Java but I look to save time where possible Also... shads.. you're outdoing yourself man... I'm very impressed with the built-in coinbasing & work generation now. It eliminates almost all of the custom mods I had made to my version of bitcoind, which lowers my support profile and barrier to upgrades. Really impressed here. Yes he has done an amazing job.
|
|
|
|
mu50stang
|
|
January 09, 2012, 09:57:13 PM |
|
I keep getting this message everyone once in a while. I was wondering what it meant or if it was an issue.
5470046 [HttpClient-upstream-work-submit-handler-38] WARN org.eclipse.jetty.util.log - EXPIRED ContentExchange@1769400994=POST//127.0.0.1:8444/#8
|
|
|
|
Remember remember the 5th of November
Legendary
Offline
Activity: 1862
Merit: 1011
Reverse engineer from time to time
|
|
January 09, 2012, 10:33:54 PM |
|
I really hope PSJ soon gets completed X extensions.
Such as X-rollntime etc.
|
BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
|
|
|
DavinciJ15
|
|
January 10, 2012, 12:12:53 AM |
|
Shadders
If you are not coming back?
|
|
|
|
cablepair
|
|
January 10, 2012, 12:21:55 AM |
|
ive been wondering the same thing
|
|
|
|
mu50stang
|
|
January 10, 2012, 02:55:35 AM |
|
JSON-RPC getmemorypool update failed.
Whats happens when I get this error.
|
|
|
|
|