Quote from: gigabytecoin on June 26, 2011, 10:56:56 PM

Quote from: smoothie on June 26, 2011, 10:34:43 PM

Quote from: frizzl on June 26, 2011, 10:27:42 PM

Are you sure it is not dying right away after it comes up? I had a lot of initial issues getting pushpoold to even start up and stay started. Most of the time is was a database issue when pp tried to connect to mysql it was failing and causing pp to stop right away make sure pushpool is started and you should be able to telnet to ur port 8344

Okay I'm trying to figure out what could be stopping pushpool from running. I double checked the database name, username to database, and associated password by logging into mysql via the terminal and then doing a SELECT * FROM pool_worker to see if I could get that far.

I did have one suspicion about the port that is used to connect to the database. Is that port a default port if so how could I change it in mysql if I need to?

Is the method I used of finding the process ID associated with pushpoold a valid way of checking to see if pushpoold is running?

thanks for your help.

What version of pushpool are you trying to run? v0.5 or v0.4.1 Huh

If you are using v0.5 try v0.4.1 ...

To check to see if pushpool is running, simply type ps aux | grep pushpool and you should notice at least two references to pushpool. (One for the search command you just submit, and one for the running pushpoo program).

Also try running pushpool by typing ./pushpool -E

I can't seem to get ./pushpool running by simply running /pushpool but if I add the -E then it seems to work great.

Okay I am running v0.5. I tried running the command ps aux | grep pushpool and this was the result:

Code:

bitcoinminer2@ubuntu:~$ ps aux | grep pushpoold
1000 3004 0.0 0.0 13124 1032 pts/3 S+ 15:14 0:00 grep --color=auto pushpoold

this is of course after running:

Code:

bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$ ./pushpoold -E
bitcoinminer2@ubuntu:~/POOLINSTALL/pushpool-0.5$ [2011-06-26 23:15:47.680372] Listening on host :: port 8342
[2011-06-26 23:15:47.680703] Listening on host :: port 8341
[2011-06-26 23:15:47.680835] Listening on host :: port 8344
[2011-06-26 23:15:47.680934] Listening on host 127.0.0.1 port 8338

You think it could be the version? what version are you running? Have you had similar problems like this?