Hey Multipool! Thanks for releasing your source, this is pretty exciting. I've been trying to get it up and running on my system this evening.
I've edited the URLs / IPs in Multipool.py for my local LAN.
I'm currently getting the following error in my log when trying to start things up for the first time:
starting pool from scratch (no data file provided)
starting pool status monitor
monitoring pools
starting getwork daemon
connection error to solo (p=0.50): 500 Internal Server Error
starting pool rewards and transactions monitor
connection error to solo (p=1.00): 500 Internal Server Error
connection error to solo (p=1.50): 500 Internal Server Error
connection error to solo (p=2.00): 500 Internal Server Error
starting rpc server daemon
connection error to solo (p=2.50): 500 Internal Server Error
main thread online Tue Jun 28 22:31:32 2011
thread 4: rpc daemon online
thread 1: status monitor online
thread 3: reward monitor online
thread 2: getwork daemon online
thread 5: website daemon online
0 users (0 active): hashrate=0 Mhash/s getworks=/min (queue size=30) shares=/min stale=/min
starting website
connection error to solo (p=3.00): 500 Internal Server Error
connection error to solo (p=3.50): 500 Internal Server Error
connection error to solo (p=4.00): 500 Internal Server Error
...lots more connection errors to solo...
I've tried restarting bitcoind, which didn't seem to help. If bitcoind
isn't running, it dies sooner with 'cannot communicate with bitcoind' (or something to that effect).
I tried changing some of the ports (I prefixed all of $port, $website_port, and $longpoll_port with an additional '1'), and the Multipool server started up cleanly
once and seemed to be able to connect to all the other servers I have configured just fine. I was able to connect my miner and submit shares.
While the server was running, I tried to browse to the local Multipool website (with the updated website_port) to check stats, and got:
404 Not Found
edit: I think this 404 was because I missed one edit, where you have something about tor exit.
After that, I ctrl+C'd to shut things down and it seemed to shut down cleanly. Trying to start up again with the exact same commandline params, and I'm back to the 'connection error to solo' issues.
Any ideas on the solo issue? FWIW, I'd be fine with (prefer, actually....) no solo mining and I can just configure something else [a PPS pool?] as a static fallback...