Latest posts of: crimsonredmk

Show Posts
Pages: [1]

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 31, 2011, 04:35:57 AM

Thank you Xenland, that finally did it, along with clearing out MySQL completely and starting fresh there. I knew bitcoind took forever to download the blocks at first but I could connect on 8332 and not through pushpoold. All is better now! Thank you! Payment sent.

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 31, 2011, 12:15:33 AM

Tried this on a LAN with absolutely no firewalls anywhere and I'm still getting the 500 error. No one else has seen this? What IP should I put in where it says 10.0.0.1? I must be missing something, but I don't know what...

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 30, 2011, 01:16:45 PM

Sounds great My 500 error is what pushpoold spits out every time Phoenix tries to connect to it, not through a browser. Phoenix says "MSG: upstream RPC error". Looking around old IRC logs tells me that the connection between pushpoold and bitcoind is to blame here, but I can't find any solutions.

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 30, 2011, 06:26:37 AM

Ah, of course. Fixed with Code: INSERT INTO pool_worker (username, password) VALUES('mikes', 'waffleman' ) Next up: 500 error on pushpoold. Sorry to be such a damned bother to you, you'll be getting some Bitcoins soon! I have this in my ~/.bitcoin/bitcoin.conf: Code: rpcuser=mikes rpcpassword=waffles rpcport=8332 and run it with "./bitcoin-0.3.21/bin/64/bitcoind -daemon -gen=0". I of course have the right rpc details in server.json and memcached is running. Going to bed now, but I'll surely be back in the morning with more problems. Sorry!

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 30, 2011, 05:31:00 AM

I ran

Code:

CREATE TABLE shares (
  id int(11) NOT NULL AUTO_INCREMENT,
  rem_host text NOT NULL,
  username text NOT NULL,
  our_result text,
  upstream_result text,
  reason text,
  solution text,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

CREATE TABLE pool_worker (
  id int(11) NOT NULL AUTO_INCREMENT,
  mikes varchar(128) NOT NULL,
  `waffleman` varchar(128) NOT NULL,
  PRIMARY KEY (id)
) ENGINE=MyISAM  DEFAULT CHARSET=utf8;

And as a result got: http://www.cl.ly/152j0K0i383c2d1o4501 (phpMySQL print view)

Edit: No idea what print to PDF did, here's a screenshot: http://cl.ly/3J0n2b2p3V4345381c3V

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 30, 2011, 05:18:46 AM

OK, connecting to the right port this time gets me new errors (great...): [1306732202.090055] mysql pwdb query failed at prep [1306732202.090236] memcached store(/pushpoold/cred_cache/mikes) failed: WRITE FAILURE "mikes" is the username Phoenix is using to connect. I'm certain server.json has the right MySQL DB, username, and password.

Bitcoin / Bitcoin Technical Support / Re: pushpool - Tech Support

on: May 30, 2011, 04:30:11 AM

first off, thank you for the guide. Finally something simple enough to get started with. I followed everything just fine and have it running with the above server.json config (changed 10.0.0.1 to my computer's LAN IP (let's call it 192.168.1.123), which is an Ubuntu 10.04 x86_64 box with ufw (firewall) enabled. I'm using the phoenix miner on my 2 other worker PCs with http://randomworkername:randompassword@192.168.1.123:8338 - I've done "ufw allow 8338" and pushpoold gives me a weird: Code: [1306729067.519756] Listening on host 192.168.1.123 port 8338 #123 is the server [1306729257.683109] client host 192.168.1.101 port 50524 connected #101 is my worker [1306729272.724169] client host 192.168.1.101 port 50525 connected [1306729287.755354] client host 192.168.1.101 port 50526 connected while Phoenix says it can't connect. Any ideas? Edit: Turning off ufw didn't help. Same results. Edit x2: Do I have to make the username and password for each worker? Something like this in the MySQL DB: https://github.com/jine/pushpool/blob/master/example-mysql.sql

Pages: [1]