CoiniumServ - open source & high performance pooled mining server software

[artbatista]

I just got around to build Alpha 5  in a Ubuntu 14.04 virtual machine in Hyper-V and the website works fine.

This website error must be a paths issue with windows.

Art

[bonesoul]

I am seeing a few of these with lottocoin, a straight SCRYPT coin:

Code:

09/05/2014 10:45:28 -04:00 [Error] [BlockProcessor] [Lottocoin] Queried transaction does not exist ea46fcbf06da83858d2df176719ca520e2ffbe2c083f1f4a2852239eb69f253b - Invalid or non-wallet transaction id

09/05/2014 10:45:28 -04:00 [Error] [ShareManager] [Lottocoin] Submit block failed - height: 757161, hash: f6ac98f3f966ca26b8584cbfff981d52009f2de52e42e8179b28ef819f977df8 - Object reference not set to an instance of an object.

09/05/2014 10:45:28 -04:00 [Information] [ShareManager] [Lottocoin] Submit block [757161] failed with hash: f6ac98f3f966ca26b8584cbfff981d52009f2de52e42e8179b28ef819f977df8


09/05/2014 11:28:03 -04:00 [Error] [BlockProcessor] [Lottocoin] Queried transaction does not exist b0a2ce730310641f2c1cfc1d523d7b9d19c7caeef4e9acda181b0ddf6e7f7bf0 - Invalid or non-wallet transaction id

09/05/2014 11:28:03 -04:00 [Error] [ShareManager] [Lottocoin] Submit block failed - height: 757252, hash: 9799eb560498940bd399e73bcf06a1f35891d94d87c41d4ec10b6b27f655af96 - Object reference not set to an instance of an object.

09/05/2014 11:28:03 -04:00 [Information] [ShareManager] [Lottocoin] Submit block [757252] failed with hash: 9799eb560498940bd399e73bcf06a1f35891d94d87c41d4ec10b6b27f655af96


09/05/2014 11:40:29 -04:00 [Error] [BlockProcessor] [Lottocoin] Queried transaction does not exist 0f122686f253141f779ea8732577e908944525d28a7ec45ebbcb48e38b220a8b - Invalid or non-wallet transaction id

09/05/2014 11:40:29 -04:00 [Error] [ShareManager] [Lottocoin] Submit block failed - height: 757268, hash: 5e7e5dbc4aa9482e90bcf5d3d572f888b133818f391e2ba8c4e3477dd5302e18 - Object reference not set to an instance of an object.

09/05/2014 11:40:29 -04:00 [Information] [ShareManager] [Lottocoin] Submit block [757268] failed with hash: 5e7e5dbc4aa9482e90bcf5d3d572f888b133818f391e2ba8c4e3477dd5302e18

Altogether, 4 instances in 12 hours

Art

Nothing goes wrong there except "Object reference not set to an instance of an object." message.

You are seeing that " Queried transaction does not exist" because, more than one miner can find a block solution at the very same (or close time intervals) and coiniumserv will submit both to get one accepted as a block. Then it just queries the coin daemon with the generation transaction id's too see which one was accepted.

[bonesoul]

On windows 2012 R2, running alpha 5:

Code:

Could not locate your error view! Details: Unable to locate view 'error'
Currently available view engine extensions: sshtml,html,htm
Locations inspected: /error,//error
Root path: C:\coinium\web\default
If you were expecting raw data back, make sure you set the 'Accept'-header of the request to correct format, for example 'application/json'

also getting this:

Code:

20:28:15 [Error] [PoolManager] [global] Error recaching statistics; Error getting value from 'Latest' on 'CoiniumServ.Pools.BlocksCache'.

created new issue entries;
* web issue; https://github.com/CoiniumServ/CoiniumServ/issues/411
* statistics issue; https://github.com/CoiniumServ/CoiniumServ/issues/427

[bonesoul]

I just got around to build Alpha 5  in a Ubuntu 14.04 virtual machine in Hyper-V and the website works fine.

This website error must be a paths issue with windows.

Art

seems an issue with binary distibutions, if you compile on windows, it just works okay, still examining the problem.

edit: found the problem, check the issue page for solution

[artbatista]

I just got around to build Alpha 5  in a Ubuntu 14.04 virtual machine in Hyper-V and the website works fine.

This website error must be a paths issue with windows.

Art

seems an issue with binary distibutions, if you compile on windows, it just works okay, still examining the problem.

edit: found the problem, check the issue page for solution

I guess I'll fire up VS and compile it.

Art

[artbatista]

The website works when I compile the source myself.

Running in Windows 2012 R2, I have the following setup in my config:

Code:

	"website": {
		"enabled": true,
		"bind": "192.168.1.109",
		"port": 80,
        "backend" : {
            "metrics": {
                "enabled": false
            }

When I access http://192.168.1.109 from my local network, the page displays as it's supposed to.

However, I forwarded port 80 thru my router, when I access from the internet with my domain name http://artbatista.com, I get a page timeout and this:

Code:

09/07/2014 11:17:02 -04:00 [Error] [HttpServer] [global] Unhandled web-server exception: Unable to locate base URI for request: http://artbatista.com/

Same error if I try the raw IP instead.


Art

[bonesoul]

try setting a domain there instead - like; "bind": "eu.coinium.org",

[artbatista]

try setting a domain there instead - like; "bind": "eu.coinium.org",

Interesting. Set it with artbatista.com does not work, set it to www.artbatista.com it works.

Can't you just make this so that it will allow connections to an ip number, without regard as to where the original http requested pointed to?

That way when I ask my browser to go to "artbatista.com", the router will sent to 192.168.1.109, and all I have to set in the config file is bind to 192.168.1.109

Art

PS. assuming you have the port forwarded in the router.

[artbatista]

you probably know this already, but the hash rate calculated and shown in the web interface are wildly inaccurate.

Art

[bonesoul]

try setting a domain there instead - like; "bind": "eu.coinium.org",

Interesting. Set it with artbatista.com does not work, set it to www.artbatista.com it works.

Can't you just make this so that it will allow connections to an ip number, without regard as to where the original http requested pointed to?

That way when I ask my browser to go to "artbatista.com", the router will sent to 192.168.1.109, and all I have to set in the config file is bind to 192.168.1.109

Art

PS. assuming you have the port forwarded in the router.

we need to fix the nancy configuration and guess then it's quite possible.

and yes for hashrate calculation: https://github.com/CoiniumServ/CoiniumServ/issues/332

[artbatista]

try setting a domain there instead - like; "bind": "eu.coinium.org",

Interesting. Set it with artbatista.com does not work, set it to www.artbatista.com it works.

Can't you just make this so that it will allow connections to an ip number, without regard as to where the original http requested pointed to?

That way when I ask my browser to go to "artbatista.com", the router will sent to 192.168.1.109, and all I have to set in the config file is bind to 192.168.1.109

Art

PS. assuming you have the port forwarded in the router.

we need to fix the nancy configuration and guess then it's quite possible.

and yes for hashrate calculation: https://github.com/CoiniumServ/CoiniumServ/issues/332

It's worst than that. It seems to work randomly. Right now I can connect at both artbatista.com, or www.artbatista.com, but not at my ip 75.74.105.230.

Earlier tonight, it gave an error on artbatista.com, but allowed www.artbatista.com.

And, yes, I saw later that the hash rate issue was on github.

Cheers

Art

[bonesoul]

try setting a domain there instead - like; "bind": "eu.coinium.org",

Interesting. Set it with artbatista.com does not work, set it to www.artbatista.com it works.

Can't you just make this so that it will allow connections to an ip number, without regard as to where the original http requested pointed to?

That way when I ask my browser to go to "artbatista.com", the router will sent to 192.168.1.109, and all I have to set in the config file is bind to 192.168.1.109

Art

PS. assuming you have the port forwarded in the router.

we need to fix the nancy configuration and guess then it's quite possible.

and yes for hashrate calculation: https://github.com/CoiniumServ/CoiniumServ/issues/332

It's worst than that. It seems to work randomly. Right now I can connect at both artbatista.com, or www.artbatista.com, but not at my ip 75.74.105.230.

Earlier tonight, it gave an error on artbatista.com, but allowed www.artbatista.com.

And, yes, I saw later that the hash rate issue was on github.

Cheers

Art

okay i created an issue entry for it and will be checking nancy resources for a work-around; https://github.com/CoiniumServ/CoiniumServ/issues/430

update: artbatista, can you please try this fix: https://github.com/raistlinthewiz/CoiniumServ/tree/feature/web-bindings , you should be setting "bind": "" in web-server config.

Please let me if it works for you so I can merge it in the development tree.

[artbatista]

okay i created an issue entry for it and will be checking nancy resources for a work-around; https://github.com/CoiniumServ/CoiniumServ/issues/430

update: artbatista, can you please try this fix: https://github.com/raistlinthewiz/CoiniumServ/tree/feature/web-bindings , you should be setting "bind": "" in web-server config.

Please let me if it works for you so I can merge it in the development tree.

Crap, I am not familiar with Github, I can't seem to find a way to get the Github desktop app to pull that branch. All I can pull is DEVELOP and MASTER.

Can you give me quick pointer on how to get that branch?

Art

[bonesoul]

the zip file: https://github.com/raistlinthewiz/CoiniumServ/archive/feature/web-bindings.zip

[artbatista]

the zip file: https://github.com/raistlinthewiz/CoiniumServ/archive/feature/web-bindings.zip

Thank you.

Art

OK, seems good.

Anyway, I can access the web server using localhost, 127.0.0.1, the local ip of the machine, from outside the network with a redirected port, etc.

Good job.


Art

[artbatista]

this just came up:

14:56:32 [Error] [Pool] [Bitcoin] Error initializing pool; Unable to resolve type:
CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager

This may be related to the fact that Bitcoin daemon is still not synced, but just in case, I am reporting it. It will be at least 12 hours before bitcoin is fully synced, ill check then and let you know.

Art

[bonesoul]

okay thank you, a full debug log file may help better.

[artbatista]

okay thank you, a full debug log file may help better.

The BTC daemon is still not synced, but the alpha 5 version enabled the BTC pool, while occasionally complaining of time-outs from the daemon.

The web-bindings version, does not enable the BTC pool at all. Here are my config file and the logs:

bitcoin.json

Code:

{
    # detailed sample config file for pool which explicility sets all settings.

	"enabled": true,	

    # -------------------------------
    # Coin configuration
    # -------------------------------

    # coin: name of the coin configuration file that should exist in config/coins/.

	"coin": "bitcoin.json",    

    # -------------------------------
    # Coin Daemon RPC Connection
    # -------------------------------

	# host: ip/hostname of coin-daemon.
    # port: the port coin daemon is listening on.
    # username: username for rpc connection.
    # password: password for rpc connection.

	"daemon": {
		"host": "127.0.0.1",
		"port": 8388,
		"username": "removed",
		"password": "removed"
	},

    # -------------------------------
    # Meta Configuration
    # -------------------------------

    # motd: message of the day.
    # txMessage: message to be included used within generation transactions.

    "meta": {
        "motd": "Welcome to CoiniumServ pool, enjoy your stay! - http://www.coiniumserv.com",
        "txMessage": "http://www.coiniumserv.com/"
     },

    # -------------------------------
    # Wallet & Rewards Configuration
    # -------------------------------
    
    # address: generated coins will arrive here.

    "wallet" : {
        "address":  "1QGWCNk7oDYTJKYkCgBB4tuJCyav1LS7Kg"
    },

    # rewards: list of addresses that gets a percentage from each mined block (ie, pool fee.)

    "rewards":  [
        {"1QGWCNk7oDYTJKYkCgBB4tuJCyav1LS7Kg": 1} 
    ],

    # -------------------------------
    # Payment Processing Configuration
    # -------------------------------

	# enabled: set this true to let CoiniumServ handle the payments, false if you would like some other software like mpos to handle them.
    # interval: interval in seconds that payment-processor will be running.
    # minimum:  minimum amount of coins before a miner is eligable for getting a payment.

	"payments": {
		"enabled": true,
        "interval": 60,
		"minimum": 0.002
	},

    # -------------------------------
    # Miner Configuration
    # -------------------------------

    # validateUsername: set true to validate miner usernames as an addresses against the coin daemon.
    # timeout: timeout in seconds to disconnect miners that did not submit any shares for the period.

    "miner":  {
        "validateUsername": true,
        "timeout": 300
    },

    # -------------------------------
    # Job Manager Configuration
    # -------------------------------

    # blockRefresh: timeout in miliseconds to poll coin daemon for a new block.
    # rebroadcast: if now new blocks are found in this many seconds, a new job will be created and broadcasted.


    "job":  {
        "blockRefreshInterval": 1000,
        "rebroadcastTimeout": 55        
    },

    # -------------------------------
    # Stratum Server Configuration
    # -------------------------------

    # stratum:
    # enabled: set this true to enable stratum server.
    # bind: interface to bind stratum server.
    # port: port to listen for stratum connections.
    # diff: default difficulty assigned to newly connected miners.

    # vardiff:
    # enabled: set this true to enable variable-difficulty support.
    # minDiff: minimum difficulty that can be assigned to miners.
    # maxDiff: maximum difficulty that can be assigned to miners.
    # targetTime: try to get a single share per this many seconds from miner.
    # retargetTime: retarget a miners difficulty ever this many seconds.
    # variancePercent: allow difficulty for a miner to vary this percent without retargeting.

	"stratum": {
		"enabled": true,
		"bind": "0.0.0.0",
		"port": 3333,
		"diff": 16,
        "vardiff": {
            "enabled": true,
            "minDiff": 8,
            "maxDiff": 512,
            "targetTime": 15,
            "retargetTime": 90,
            "variancePercent": 30
        }
	},
    			
    # -------------------------------
    # Ban Configuration
    # -------------------------------

    # you can ban miners which submits invalid work / data to reduce system/network load.
    # enabled: set this true to enable banning support.
    # duration: duration of ban when a miner gets flagged for so.
    # invalidPercent: percentage of invalid shares to trigger a ban.
    # checkThreshold: number of shares required before a miner's shares are considered for a ban.
    # purgeInterval: purge interval in seconds that bans are checked to see if they are expired.

    "banning": {
        "enabled": true,
        "duration": 600,
        "invalidPercent": 50,
        "checkThreshold": 100,
        "purgeInterval": 300
    },

    # -------------------------------
    # Per-pool Storage Configuration
    # -------------------------------

    # hybrid storage layer
    # enabled: set this true to enable hybrid storage mode where redis and mysql is used together.

    # mpos layer
    # enabled: set this true to enable mpos compatibility mode - make sure to internal disable payment-processor!

    # redis
    # host: redis host.
    # port: redis port.
    # password: set the password if your redis installation requires one.
    # databaseId: redis database instance id (optional)

    # mysql
    # host: database host.
    # port: database port.
    # username: username for connecting the database.
    # password: password for connecting the database.
    # database: database name.

	"storage": {
        "hybrid": {
            "enabled": true,
		    "redis": {
			    "host": "127.0.0.1",
			    "port": 6379,
                "password": "removed",
                "databaseId": 0
		    },
		    "mysql": {
			    "host": "127.0.0.1",
			    "port": 3306,
			    "user": "removed",
			    "password": "removed",
                "database": "bitcoin"
		    }
        },
        "mpos": {
            "enabled": false,
		    "mysql": {
			    "host": "127.0.0.1",
			    "port": 3306,
			    "user": "username",
			    "password": "password",
                "database": "db-name"
		    }
        }
	},  

    # -------------------------------
    # Getwork Server Configuration
    # -------------------------------

    # EXPERIMENTAL!; This feature is still in development and not complete yet.
    # enabled: Set this true to enable getwork server.
    # bind: interface to bind getwork server.
    # port: port to listen for getwork connections.

	"vanilla": {
		"enabled": false,
		"bind": "localhost",
		"port": 2223
    }
}

config.json

Code:

{
    # -------------------------------
    # Stack Configuration
    # -------------------------------

    # name:  name of the pool stack.

    "stack": {
        "name": "ArtBatista.com"
    },

    # -------------------------------
    # Statistics Configuration
    # -------------------------------
    
    # updateInterval: interval for recaching statistics.
    # hashrateWindow: how many seconds worth of shares should be gathered to generate hashrate.

    "statistics": {
        "updateInterval": 60,
        "hashrateWindow": 120
    },

    # -------------------------------
    # Website Configuration
    # -------------------------------

    # enabled: set this true to enable frontend.
    # bind: interface to bind webserver.
    # port: port to listen for http connections.
    # backend: 
    # enabled: set this true to enable admin backend.
    # password: password for enabling administrator 

	"website": {
		"enabled": true,
		"bind": "",
		"port": 80,
        "backend" : {
            "metrics": {
                "enabled": false
            }
        }
	},

    # -------------------------------
    # Logging Configuration
    # -------------------------------

    # root: relative path of logs.
    # targets: log targets.
    
    # target: 
    # enabled: is the log target enabled?
    # type: console, file or packet.
    # filename: filename of the log file.
    # rolling: set this true to get a seperate log file for every day.
    # level: minimum log level.

    # logging configuration
	"logging": {
		"root": "logs",
		"targets": [
			{
				"enabled": true,
				"type": "console",
				"level": "debug"
			},
			{
				"enabled": true,
				"type": "file",
				"filename": "server.log",
				"rolling": false,
				"level": "information"
			},
			{
				"enabled": true,
				"type": "file",
				"filename": "debug.log",
				"rolling": false,
				"level": "verbose"
			},
			{
				"enabled": true,
				"type": "packet",
				"filename": "packet.log",
				"rolling": false,
				"level": "verbose"
			}			
        ]	
	}
}

debug.log, I waited a while on this one, but there was not BTC pool activity

Code:

09/08/2014 22:35:55 -04:00 [Information] [Program] [global] CoiniumServ Piri Reis 0.1.5.24989 warming-up..
09/08/2014 22:35:55 -04:00 [Information] [PlatformManager] [global] Running over .Net, framework: 4.5 (v4.0.30319.34014).
09/08/2014 22:35:55 -04:00 [Debug] [ConfigManager] [global] Discovering enabled pool configs..
09/08/2014 22:35:56 -04:00 [Information] [ConfigManager] [global] Discovered a total of 1 enabled pool configurations: [Bitcoin]
09/08/2014 22:35:56 -04:00 [Debug] [Pool] [Bitcoin] Generated cryptographically random instance Id: 731018519
09/08/2014 22:35:57 -04:00 [Information] [NetworkInfo] [Bitcoin] symbol: BTC algorithm: sha256 version: 90201 protocol: 70002 wallet: 60000 network difficulty: 3815723798.81463000 block difficulty: 3815723798.81 network hashrate: 31.78 PH/s network: mainnet peers: 20 blocks: 289829 errors: none 
09/08/2014 22:35:57 -04:00 [Information] [MySqlProvider] [Bitcoin] Mysql storage initialized: 127.0.0.1:3306, database: bitcoin.
09/08/2014 22:35:57 -04:00 [Information] [RedisProvider] [Bitcoin] Redis storage initialized: 127.0.0.1:6379, v2.8.14.


09/08/2014 22:35:57 -04:00 [Error] [Pool] [Bitcoin] Error initializing pool; Unable to resolve type: CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager


09/08/2014 22:35:58 -04:00 [Debug] [StatisticsManager] [global] Recached statistics - took 0.100 seconds
09/08/2014 22:35:58 -04:00 [Information] [HttpServer] [global] Web-server listening on: http://localhost/

packet.log

Code:

09/08/2014 22:35:56 -04:00 [Verbose] [DaemonClient] [Bitcoin] tx: "{
    'method' : 'getinfo',
    'params' : [
        
    ],
    'id' : 0
}"
09/08/2014 22:35:56 -04:00 [Verbose] [DaemonClient] [Bitcoin] rx: "{
    'result' : {
        'version' : 90201,
        'protocolversion' : 70002,
        'walletversion' : 60000,
        'balance' : 0.00000000,
        'blocks' : 289829,
        'timeoffset' : -1,
        'connections' : 20,
        'proxy' : '',
        'difficulty' : 3815723798.81463000,
        'testnet' : false,
        'keypoololdest' : 1410119942,
        'keypoolsize' : 101,
        'paytxfee' : 0.00010000,
        'relayfee' : 0.00001000,
        'errors' : ''
    },
    'error' : null,
    'id' : 0
}"
09/08/2014 22:35:57 -04:00 [Verbose] [DaemonClient] [Bitcoin] tx: "{
    'method' : 'getmininginfo',
    'params' : [
        
    ],
    'id' : 1
}"
09/08/2014 22:35:57 -04:00 [Verbose] [DaemonClient] [Bitcoin] rx: "{
    'result' : {
        'blocks' : 289829,
        'currentblocksize' : 81761,
        'currentblocktx' : 69,
        'difficulty' : 3815723798.81463000,
        'errors' : '',
        'genproclimit' : -1,
        'networkhashps' : 31780470568310748,
        'pooledtx' : 160,
        'testnet' : false,
        'generate' : false,
        'hashespersec' : 0
    },
    'error' : null,
    'id' : 1
}"
09/08/2014 22:35:57 -04:00 [Verbose] [DaemonClient] [Bitcoin] tx: "{
    'method' : 'getdifficulty',
    'params' : [
        
    ],
    'id' : 2
}"
09/08/2014 22:35:57 -04:00 [Verbose] [DaemonClient] [Bitcoin] rx: "{
    'result' : 3815723798.81463000,
    'error' : null,
    'id' : 2
}"

server.log

Code:

09/08/2014 22:35:55 -04:00 [Information] [Program] [global] CoiniumServ Piri Reis 0.1.5.24989 warming-up..
09/08/2014 22:35:55 -04:00 [Information] [PlatformManager] [global] Running over .Net, framework: 4.5 (v4.0.30319.34014).
09/08/2014 22:35:56 -04:00 [Information] [ConfigManager] [global] Discovered a total of 1 enabled pool configurations: [Bitcoin]
09/08/2014 22:35:57 -04:00 [Information] [NetworkInfo] [Bitcoin] symbol: BTC algorithm: sha256 version: 90201 protocol: 70002 wallet: 60000 network difficulty: 3815723798.81463000 block difficulty: 3815723798.81 network hashrate: 31.78 PH/s network: mainnet peers: 20 blocks: 289829 errors: none 
09/08/2014 22:35:57 -04:00 [Information] [MySqlProvider] [Bitcoin] Mysql storage initialized: 127.0.0.1:3306, database: bitcoin.
09/08/2014 22:35:57 -04:00 [Information] [RedisProvider] [Bitcoin] Redis storage initialized: 127.0.0.1:6379, v2.8.14.

09/08/2014 22:35:57 -04:00 [Error] [Pool] [Bitcoin] Error initializing pool; Unable to resolve type: CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager

09/08/2014 22:35:58 -04:00 [Information] [HttpServer] [global] Web-server listening on: http://localhost/

The "CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager" error does not occur in the alpha 5 version.

Something else of note, this version would not build because the csredis dependencies directory was empty. I had to copy that from the alpha 5 version. I guess GitHUb does not package them with the zip file, just a blank directory in place of csredis directory.

Finally, the web site works flawlessly in this version, I have tried to find a scenario where I can't connect via browser, but so far I have not seen a problem.

Let me know if I can do more.

Art

[artbatista]

I am intending to start setting up MPOS to try with coinium.

Are the hybrid storage setting incompatible with MPOS?

If I turn on MPOS mode, do I turn off the MySQL/redis storage option?

In standalone mode, what form of compensation is used to pay clients. PPS, PPLNS, ETC

Art

[bonesoul]

debug.log, I waited a while on this one, but there was not BTC pool activity

Code:

09/08/2014 22:35:55 -04:00 [Information] [Program] [global] CoiniumServ Piri Reis 0.1.5.24989 warming-up..
09/08/2014 22:35:55 -04:00 [Information] [PlatformManager] [global] Running over .Net, framework: 4.5 (v4.0.30319.34014).
09/08/2014 22:35:55 -04:00 [Debug] [ConfigManager] [global] Discovering enabled pool configs..
09/08/2014 22:35:56 -04:00 [Information] [ConfigManager] [global] Discovered a total of 1 enabled pool configurations: [Bitcoin]
09/08/2014 22:35:56 -04:00 [Debug] [Pool] [Bitcoin] Generated cryptographically random instance Id: 731018519
09/08/2014 22:35:57 -04:00 [Information] [NetworkInfo] [Bitcoin] symbol: BTC algorithm: sha256 version: 90201 protocol: 70002 wallet: 60000 network difficulty: 3815723798.81463000 block difficulty: 3815723798.81 network hashrate: 31.78 PH/s network: mainnet peers: 20 blocks: 289829 errors: none 
09/08/2014 22:35:57 -04:00 [Information] [MySqlProvider] [Bitcoin] Mysql storage initialized: 127.0.0.1:3306, database: bitcoin.
09/08/2014 22:35:57 -04:00 [Information] [RedisProvider] [Bitcoin] Redis storage initialized: 127.0.0.1:6379, v2.8.14.


09/08/2014 22:35:57 -04:00 [Error] [Pool] [Bitcoin] Error initializing pool; Unable to resolve type: CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager


09/08/2014 22:35:58 -04:00 [Debug] [StatisticsManager] [global] Recached statistics - took 0.100 seconds
09/08/2014 22:35:58 -04:00 [Information] [HttpServer] [global] Web-server listening on: http://localhost/

Code:

> Error initializing pool; Unable to resolve type: CoiniumServ.Persistance.Layers.Hybrid.IMigrationManager

This error prevents the pool from initializing. Can you please change this line

Code:

https://github.com/CoiniumServ/CoiniumServ/blob/develop/src/CoiniumServ/Pools/Pool.cs#L129

to

Code:

_logger.Error("Error initializing pool; {0:l}", e);

and paste the updated error log? It'll be helping me to find out the bug & fix.

I am intending to start setting up MPOS to try with coinium.

Are the hybrid storage setting incompatible with MPOS?

If I turn on MPOS mode, do I turn off the MySQL/redis storage option?

In standalone mode, what form of compensation is used to pay clients. PPS, PPLNS, ETC

Art

for mpos mode, you have to use MPOS-storage-layer which does only use MySQL.

you have to enable mpos section: https://github.com/CoiniumServ/CoiniumServ/blob/develop/src/CoiniumServ/config/pools/advanced-example.json#L190

In standalone mode, it does you Pay-Per-Share right now but I'd like to also note that I'm re-writing the payment-processor for standalone mode which will be eventually far better then anything that exists.