[ANN] Stratum mining protocol - ASIC ready - page 9.

slush

legendary

Activity: 1386

Merit: 1097

As I mentioned above, you're running wrong code. This is not a pool server, it's just a stratum server. Please use launcher_demo.tac from stratum-mining.

c4n10

sr. member

Activity: 294

Merit: 250

Quote from: slush on March 27, 2013, 03:49:04 AM

Can you pastebin the output from the server log?

Here is the live output:

http://pastebin.com/3QKRAkbL

And here is the log:

http://pastebin.com/H7k444RQ

Thank you for taking the time to look =)

slush

legendary

Activity: 1386

Merit: 1097

Can you pastebin the output from the server log?

c4n10

sr. member

Activity: 294

Merit: 250

Quote from: slush on March 27, 2013, 03:45:48 AM

Quote from: c4n10 on March 26, 2013, 04:29:18 PM

We have the server installed, configured and running but when attempting to connect miners we are receiving: "method 'subscribe' not found for service 'mining'"...

What did you installed exactly? Looks like you installed Stratum server without mining service. You need this one: https://github.com/slush0/stratum-mining

We have installed the server and the mining service, the pastebin output directly above your post is from the mining-proxy output with "-v" flag...

slush

legendary

Activity: 1386

Merit: 1097

Quote from: c4n10 on March 26, 2013, 04:29:18 PM

We have the server installed, configured and running but when attempting to connect miners we are receiving: "method 'subscribe' not found for service 'mining'"...

What did you installed exactly? Looks like you installed Stratum server without mining service. You need this one: https://github.com/slush0/stratum-mining

c4n10

sr. member

Activity: 294

Merit: 250

Ok, so tried connecting via the mining-proxy protocol and same error, here is the output of the proxy "-v":

http://pastebin.com/iTD5LCXD

c4n10

sr. member

Activity: 294

Merit: 250

Hello,

We would like to implement Stratum protocol at minelitecoin.com and we are having a little trouble...

We have the server installed, configured and running but when attempting to connect miners we are receiving: "method 'subscribe' not found for service 'mining'"...

Any help would be greatly appreciated as we've spent hours going through Google and spent hours going through thousands of lines of code to try and figure this out to no avail...

Thank you in advance to anyone who can help us out and thank you Slush for putting in the work on the Stratum protocol to begin with...

crazyearner

legendary

Activity: 1820

Merit: 1001

Is their a chance of a feature to be added to status to in user part of how many shares have been mined total for user and paid and brake down...

Also question if share diff is higher do you earn double the amount more rewards Huh

cnbtcnews

newbie

Activity: 54

Merit: 0

I have change the bitcoin address to the server's bitcoind address

but cgminer still don't work.

Code:

No login credentials supplied for pool 0 http://192.168.183.130:3333

here is my config.py

Code:

'''
This is example configuration for Stratum server.
Please rename it to settings.py and fill correct values.
'''

# ******************** GENERAL SETTINGS ***************

# Enable some verbose debug (logging requests and responses).
DEBUG = False

# Destination for application logs, files rotated once per day.
LOGDIR = '/root/log/'

# Main application log file.
LOGFILE = None#'stratum.log'

# Possible values: DEBUG, INFO, WARNING, ERROR, CRITICAL
LOGLEVEL = 'INFO'

# How many threads use for synchronous methods (services).
# 30 is enough for small installation, for real usage
# it should be slightly more, say 100-300.
THREAD_POOL_SIZE = 10

ENABLE_EXAMPLE_SERVICE = True

# ******************** TRANSPORTS *********************

# Hostname or external IP to expose
HOSTNAME = 'localhost'

# Port used for Socket transport. Use 'None' for disabling the transport.
LISTEN_SOCKET_TRANSPORT = 3333

# Port used for HTTP Poll transport. Use 'None' for disabling the transport
LISTEN_HTTP_TRANSPORT = None

# Port used for HTTPS Poll transport
LISTEN_HTTPS_TRANSPORT = None

# Port used for WebSocket transport, 'None' for disabling WS
LISTEN_WS_TRANSPORT = None

# Port used for secure WebSocket, 'None' for disabling WSS
LISTEN_WSS_TRANSPORT = None

# Hostname and credentials for one trusted Bitcoin node ("Satoshi's client").
# Stratum uses both P2P port (which is 8333 already) and RPC port
BITCOIN_TRUSTED_HOST = 'localhost'
BITCOIN_TRUSTED_PORT = 8332
BITCOIN_TRUSTED_USER = 'starocean'
BITCOIN_TRUSTED_PASSWORD = '123'

# Use "echo -n '' | sha256sum | cut -f1 -d' ' "
# for calculating SHA256 of your preferred password
ADMIN_PASSWORD_SHA256 = None
#ADMIN_PASSWORD_SHA256 = '9e6c0c1db1e0dfb3fa5159deb4ecd9715b3c8cd6b06bd4a3ad77e9a8c5694219' # SHA256 of the password

IRC_NICK = None

'''
DATABASE_DRIVER = 'MySQLdb'
DATABASE_HOST = 'localhost'
DATABASE_DBNAME = 'pooldb'
DATABASE_USER = 'root'
DATABASE_PASSWORD = ''
'''

# Pool related settings
INSTANCE_ID = 31
CENTRAL_WALLET = '16AASBVvTTQYgGZuR81mA43tdKXEixcqs3'
PREVHASH_REFRESH_INTERVAL = 5 # in sec
MERKLE_REFRESH_INTERVAL = 60 # How often check memorypool
COINBASE_EXTRAS = '/stratum/'

mysql database need configure?

Code:

mysql> use pooldb
Database changed
mysql> show tables;
Empty set (0.00 sec)

slush

legendary

Activity: 1386

Merit: 1097

Code:

[quote author=cnbtcnews link=topic=108533.msg1633641#msg1633641 date=1363515987]
2013-03-17 03:26:08-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:08-0700 [HTTPPageGetter,client] Stopping factory

This polls the bitcoin and checks for new blocks on the network.

Quote

Code:

ERROR coinbaser # Coinbase address '16AASBVvTTQYgGZuR81mA43tdKXEixcqs3' is NOT valid

Looks like this address doesn't belong to your instance of bitcoind, right?

Quote

Code:

No login credentials supplied for pool 0 stratum+tcp://192.168.183.130:8332

Are you sure the port is OK? From the log above it looks like there's bitcoind sitting on this port.

cnbtcnews

newbie

Activity: 54

Merit: 0

I install stratum pool server in my centos6.3 32bit

but what does this meaning?

Code:

3-03-17 03:26:02-0700 [HTTPPageGetter,client] Stopping factory 
2013-03-17 03:26:08-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:08-0700 [HTTPPageGetter,client] Stopping factory 
2013-03-17 03:26:10-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:10-0700 [HTTPPageGetter,client] Stopping factory 
2013-03-17 03:26:11-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:11-0700 [HTTPPageGetter,client] Stopping factory 
2013-03-17 03:26:12-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:12-0700 [HTTPPageGetter,client] Stopping factory 
2013-03-17 03:26:17-0700 [HTTPPageGetter,client] Starting factory 
2013-03-17 03:26:17-0700 [HTTPPageGetter,client] Stopping factory

Code:

ERROR coinbaser # Coinbase address '16AASBVvTTQYgGZuR81mA43tdKXEixcqs3' is NOT valid

when I use cgminer ,it shows

Code:

No login credentials supplied for pool 0 stratum+tcp://192.168.183.130:8332

slush

legendary

Activity: 1386

Merit: 1097

I just released 1.5.1. It adds just a workaround for RPCminer, which doesn't work with targets produced by Stratum proxy. If you have RPCminer, please test the proxy with --old-target parameter and let me know if it fixed your issues!

slush

legendary

Activity: 1386

Merit: 1097

Quote from: zvs on March 03, 2013, 11:06:58 AM

Oh, Windows 7 Ultimate 64bit

Windows already implemented Stratum protocol? Cool! :-)

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

Quote from: slush on February 27, 2013, 09:04:55 AM

zvs, what software is on server side? These late and duplicated notifications looks like bug in server side implementation.

Oh, Windows 7 Ultimate 64bit

I was going to retest it later with minerd running 1 thread and affinity to 1 core with graphic cards at something like 0 intensity to see if that might have been causing it... (minerd wasn't maxed before, but it was still pretty heavy on the cpu)

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

First official release of cgminer that supports the new agreed upon resume protocol is out, 2.11.0

slush

legendary

Activity: 1386

Merit: 1097

I just released Stratum proxy 1.5.0, which fixes many bugs from previous releases. All users are encouraged to update!

slush

legendary

Activity: 1386

Merit: 1097

zvs, what software is on server side? These late and duplicated notifications looks like bug in server side implementation.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Intrinsically stratum is inherently faster and lower overhead than longpoll for both the server and the client. Minerd is fast. Cgminer is fast. Stratum is fast. On the other hand I can't speak for any other implementation at the other end.

zvs

legendary

Activity: 1680

Merit: 1000

https://web.archive.org/web/*/nogleg.com

so, earlier, I posted a query about stratum causing too much cpu load and jerkiness in computers that didnt have problem with longpolling. turning back on nagle seems to have solved that for the most part

but, i also noticed this

is minerd just really fast, is cgminer slow, or is stratum slow? one of them was 2s late

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: DrHaribo on February 25, 2013, 02:14:52 AM

This looks good. Thanks for including the user-agent in there as well.

Quote from: -ck on February 24, 2013, 09:22:24 PM

Note the session ID has changed between the initial subscription and the resume, BUT the extranonce1 has remained the same. This tells the miner it can (re)submit shares before the disconnection.

If the resume fails, how should the server respond? Give an error, or just a new extranonce1?

If the old connection is still there, I guess the server could disconnect it. That means the session ID must be hard to guess so you can't disconnect other people. You must also be very sure that you don't give out the same session ID twice, or you'll have two workers disconnecting each other all day.

It's safer to never resume a connection that still appears up to the server. But I wonder how often it will happen that a client tries to resume before the server discovers that the old connection is dead.

Letting both connections stay seems like a bad idea. They'd both be doing the same hashes in the unlikely event that they both keep hashing.

I think submitting a new extranonce1 is all that is required. We should view the sessionid submission as a hint only and let the pool decide what to do. You will indeed need unique session IDs for this support to work. When luke-Jr tested it, he found that the old connection was not actually detached before I was requesting a new one with the sessionID. This is not surprising given how difficult it can be to tell that a raw socket is actually broken or not. I suspect that dropping the first connection there is the answer.

Topic: [ANN] Stratum mining protocol - ASIC ready - page 9. (Read 146083 times)