Avalon users: bitcoind and slush's/generalfaults mining pool setup

[tiktoc]

you should be able to run it from anywhere if you copied it to /user/local/bin in the instructions.

just type bitcoind flags you need here

eg to test on testnet

Code:

bitcoind -testnet -daemon

[1715127992]

1715127992

[1715127992]

1715127992

[1715127992]

1715127992

[1715127992]

1715127992

[cypherdoc]

why am i seeing "unexpected operator"?

Code:

joe@cypher:~/git/stratum-mining$ ./scripts/generateAdminHash.sh password
./scripts/generateAdminHash.sh: 3: [: xpassword: unexpected operator
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
joe@cypher:~/git/stratum-mining$ 

[tiktoc]

Don't know ignore it. It still works.

[cypherdoc]

would this work also in 12.04 LTS which might arguably be a  little more stable?

[bitcoindaddy]

Why is the stratum proxy necessary. Can't you mine directly against the bitcoind (with getwork)? What benefit does the stratum bit do if bitcoind is on a local network?

Edit:  Also, can you use the regular bitcoind binaries instead of the latest git?

[cypherdoc]

Why is the stratum proxy necessary. Can't you mine directly against the bitcoind (with getwork)? What benefit does the stratum bit do if bitcoind is on a local network?

Edit:  Also, can you use the regular bitcoind binaries instead of the latest git?

regular getwork can't handle the load from what i understand.  the speed of the asics is too much for the standard bitcoind/getwork system so slush designed stratum.  if you look at the code tictok has provided above, you see that you are installing stratum software locally to enable this process.

someone who knows the specifics could explain more thoroughly.

[bitcoindaddy]

But the proxy is communicating with bitcoind using getworks, what's the difference? This makes sense for a remote installation, but I don't see how it makes sense for a local install?

[bitcoindaddy]

Seems to work,

I'm getting this though from the status web page (port 8889):

stratum-mining/lib/basic_stats.py, line 99 in render_GET
97                  wc = "#0A0"
98                r+="<tr bgcolor=\"%s\"><td>%s</td><td>%s/%s</td><td>%s/%s</td><td>%s</td><tr>"%(
99                        wc,wi,format(int(wd["speed"]),"n"),wd["difficulty"],format(int(wd["total_shares"]),"n"),
100                        format(int(wd["total_rejects"]),"n"),format(int(wd["total_found"]),"n"))

<type 'exceptions.TypeError'>: int() argument must be a string or a number, not 'NoneType'
It's complaining about line 99.


Does this require Python3?

Edit:  Also getting untracked shares - what does that mean?

[2013-04-05 13:09:27] Accepted untracked stratum share from pool 0
[2013-04-05 13:09:32] Stratum from pool 0 detected new block
[2013-04-05 13:09:57] Accepted untracked stratum share from pool 0
[2013-04-05 13:10:34] Accepted 0da078b4 Diff 18/6 GPU 1 pool 0

[tiktoc]

Bitcoind packages are available fro the same places as the libdb libraries, I have not tried them I assume they work, someone in the other thread for the eloipool said they were having trouble with binaries.

32bit

https://launchpad.net/~bitcoin/+archive/bitcoin/+files/bitcoind_0.8.1-quantal1_i386.deb

64bit

https://launchpad.net/~bitcoin/+archive/bitcoin/+files/bitcoind_0.8.1-quantal1_amd64.deb

[tiktoc]

Thats a no to python3 as far as  I know, I havent seen the error before, did the stats still display?

Maybe ask in this https://bitcointalk.org/index.php?topic=108533.0

Its the forum for the pool software.

[bitcoindaddy]

Thats a no to python3 as far as  I know, I havent seen the error before, did the stats still display?

Maybe ask in this https://bitcointalk.org/index.php?topic=108533.0

Its the forum for the pool software.

The stats screen displayed before I actually started mining (and it had no shares to display)

[bitcoindaddy]

I didn't see this note in the writeup:  "PREVHASH_REFRESH_INTERVAL = to the same value as MERKLE_REFRESH_INTERVAL". I had mine set to 300 instead of the recommended 60. The web display is working now. Still getting mostly untracked shares though.

[tiktoc]

Its in there.. its not in a code block though.

edit: the reason stats may not have been working properly before you mined, could be there was no values in the database for it to read and this was causing the error?

[cypherdoc]

per your instructions here:

at a new command prompt

Code:

./git/stratum-mining/scripts/blocknotify.sh --password somepassword1 --host localhost --port 3333

if its working it should display something like below (the amount of time it takes to notify will change each time)

blocknotify: done in 0.012 sec

i instead get this while server is running:

Code:

joe@cypher:~/git/stratum-mining$ ./git/stratum-mining/scripts/blocknotify.sh --password somepassword1 --host localhost --port 3333
bash: ./git/stratum-mining/scripts/blocknotify.sh: No such file or directory
joe@cypher:~/git/stratum-mining$ 

[tiktoc]

I have edited it to fix it. How it is was written will work from your home directory, but following the tute means you  are already in the stratum mining directory.

This should work as well

Code:

/home/joe/git/stratum-mining/scripts/blocknotify.sh --password somepassword1 --host localhost --port 3333

This will be needed in the end if you put it in the bitcoin.conf file anyway.

Just remember on most linux distributions the user home directories are nearly always in the format of /home/username


I

[cypherdoc]

i think you have an inconsistency in the passwords used in tute; "somepassword" & "somepassword1"

messed me up since i am just testing right now cutting and pasting everything.

[cypherdoc]

this looks good does it not?

Code:

9aea940cefe1faf5549840da80 (1) valid bitcoinrpc
2013-04-06 16:54:48,236 INFO interfaces # 00000000f8400ebc85c8eb041171b2d000a3930a52c46d4c69b0ecfbcdf6ec0b (1) valid bitcoinrpc
2013-04-06 16:55:19,929 INFO interfaces # 00000000505b58c68d9fc08ae1f87401fa6558dba4365bf72c6d4b132a491172 (3) valid bitcoinrpc
2013-04-06 16:55:21,250 INFO template_registry # We found a block candidate! 000000000179cce0c344803c172878b87a6ce63c8508b7c673e7564e78687040
2013-04-06 16:55:21,253 INFO interfaces # 000000000179cce0c344803c172878b87a6ce63c8508b7c673e7564e78687040 (173) valid bitcoinrpc
2013-04-06 16:55:21,486 INFO interfaces # Block 000000000179cce0c344803c172878b87a6ce63c8508b7c673e7564e78687040 ACCEPTED
2013-04-06 16:55:21,486 INFO DBInterface # Updating Found Block Share Record
2013-04-06 16:55:21,487 INFO DBInterface # Inserting 5 Share Records
2013-04-06 16:55:21,924 INFO stats # 2 peers connected, state changed 1 times
2013-04-06 16:55:21,925 INFO mining # New block notification received
2013-04-06 16:55:21,928 INFO stats # 1 peers connected, state changed 1 times
2013-04-06 16:55:21,934 INFO template_registry # New template for 000000000179cce0c344803c172878b87a6ce63c8508b7c673e7564e78687040
2013-04-06 16:55:21,934 INFO subscription # BROADCASTED to 1 connections in 0.000 sec
2013-04-06 16:55:21,934 INFO template_registry # Update finished, 0.002 sec, 1 txes

[cypherdoc]

can you help me decipher these times from bitcoind listtransactions?:

Code:

"time" : 1365293126,
        "timereceived" : 1365293162

[tiktoc]

looks ok, when the blocknotify runs from bitcoind does the out put say the same as when tested ? eg blocknotify done in 0.20 (the time changes)seconds?

Also the passwords are different as you are meant to be using your passwords that you choose, not the ones in the tute.

You didnt use the rpc password from the tute ? you used the one bitcoind generated when you first ran it ?

If its the one from the tute page I would change it.

[cypherdoc]

looks ok, when the blocknotify runs from bitcoind does the out put say the same as when tested ? eg blocknotify done in 0.20 (the time changes)seconds?

joe@cypher:~/git/stratum-mining$ blocknotify: done in 0.397 sec
blocknotify: done in 0.436 sec
blocknotify: done in 0.338 sec
blocknotify: done in 0.404 sec
blocknotify: done in 0.393 sec
blocknotify: done in 0.350 sec
blocknotify: done in 0.310 sec
blocknotify: done in 0.412 sec
blocknotify: done in 0.424 sec
blocknotify: done in 0.473 sec
blocknotify: done in 0.395 sec
blocknotify: done in 0.361 sec
blocknotify: done in 0.385 sec

Also the passwords are different as you are meant to be using your passwords that you choose, not the ones in the tute.

You didnt use the rpc password from the tute ? you used the one bitcoind generated when you first ran it ?

If its the one from the tute page I would change it.

as i said, i'm just testing right now so i will change pwd's when my avalons come