CoiniumServ - open source & high performance pooled mining server software

[HunterS]

it was working yesterday.but i could get other config working so i reinstalled everything now all stuff that wasnt working is and all the stuff that was working aint.

[artbatista]

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

I think you need to put the ip there after "bind".

In the develop version you can leave it blank, but I am not sure about the release version.

Try "bind":127.0.0.1, you should then be able to load from the local browser at 127.0.0.1

Art

[HunterS]

i should still be able to open web front end

[artbatista]

it was working yesterday.but i could get other config working so i reinstalled everything now all stuff that wasnt working is and all the stuff that was working aint.

I was running orbitcoin and it was working beautifully and finding blocks, but the blocks never got accepted by the daemon.

See here:

https://github.com/CoiniumServ/CoiniumServ/issues/388


Art

[HunterS]

i have it installed on digitalocean.i should put ip from there in

[artbatista]

i should still be able to open web front end

Which is why it's a bug, fixed in the develop branch.

https://github.com/CoiniumServ/CoiniumServ/issues/430


Art

[HunterS]

i just dont understand why front end worked yesterday and not today

[bonesoul]

@hunters, which commit are you using, so I may be able to help you out there.

[bonesoul]

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

I think you need to put the ip there after "bind".

In the develop version you can leave it blank, but I am not sure about the release version.

Try "bind":127.0.0.1, you should then be able to load from the local browser at 127.0.0.1

Art

he doesn't need to with latest commits from develop, with that he'll be able to run embedded web-server on all interfaces.

02:15:08 [Information] [HttpServer] [global] Web-server listening on: http://178.62.138.128/

Seems apache is running on that ip:80.

Please upload your latest config.json to pastie.org so we can look if any mis-configuration is the reason.

[HunterS]

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

I think you need to put the ip there after "bind".

In the develop version you can leave it blank, but I am not sure about the release version.

Try "bind":127.0.0.1, you should then be able to load from the local browser at 127.0.0.1

Art

he doesn't need to with latest commits from develop, with that he'll be able to run embedded web-server on all interfaces.

02:15:08 [Information] [HttpServer] [global] Web-server listening on: http://178.62.138.128/

Seems apache is running on that ip:80.

Please upload your latest config.json to pastie.org so we can look if any mis-configuration is the reason.

i pasted it in here a few replies back.top of this page

[bonesoul]

Exactly what error do you get on the browser when you try to load up the page?

[HunterS]

Exactly what error do you get on the browser when you try to load up the page?

ok guys.I done clean install and it running.But like old mate said PoS coins dont work but im happy i got it working.will setup another wallet thats not PoS and see how it goes.cheer for the help.

[HunterS]

might try NOMP.Does PoS coins work with them?

[bonesoul]

i'll be fixing pos coin support soon - https://github.com/CoiniumServ/CoiniumServ/issues/388

[bonesoul]

Grandcoin  appears not to have submitblock. Wouldn't it be better to have a switch in the coin config to tell Coinium to use an alternate method for a particular coin?

opened an issue entry for this https://github.com/CoiniumServ/CoiniumServ/issues/442

[artbatista]

I finally had a chance today to build the Develop branch, and the timeout setting is a godsend.  I have not seen any more json timeouts since changing the timing from 1 to 5 seconds.

On a separate issue....

I am seeing quite a few of these, around 1-3 per hour. Is this a problem or should I ignore this?

Code:

01:17:51 [Error] [BlockProcessor] [Bitcoin] Queried block does not exist e8f26d3549137f79f6b0db41bedd99b2413e64959d6442a5e158745dbe78bb1b - Block not found
                                                                                                  
01:17:52 [Error] [BlockProcessor] [Bitcoin] Queried block does not exist f9ac44f024f575207de14090161d5ec8462db1877bc21dce60734026a3935463 - Block not found

Let me know if I should open a ticket on Github.

Art

[bonesoul]

Code:

01:17:51 [Error] [BlockProcessor] [Bitcoin] Queried block does not exist e8f26d3549137f79f6b0db41bedd99b2413e64959d6442a5e158745dbe78bb1b - Block not found
                                                                                                  
01:17:52 [Error] [BlockProcessor] [Bitcoin] Queried block does not exist f9ac44f024f575207de14090161d5ec8462db1877bc21dce60734026a3935463 - Block not found

happens when we sumbmit more then one block hash candidates to coin daemon, the daemon will accept one of them and reject the other - and we are checking to see which one was accepted. so basically not a problem.

[andr0x]

Hi bonesoul!

First ,let me congratulate you, your Stratum Server is very very nice in all sense!: configuration, stability, Performance , And really I want use it forever  ....

Currently I'm testing it with Digibyte Coin : https://bitcointalk.org/index.php?topic=408268.0 in Scrypt algo mode in a Unix box, after some hours of testing (10hrs), I didn't receive any coins to my wallet (server and personal wallet), I'll ask later to Digibyte Dev Team if Scrypt chain have issues (is possible, because Digibyte recently migrate it chain to a multi-algo mining) ...

Well, Digibyte coin have other algo option to mining : groestl ....

Some hours later of test (6hrs) in Groestl mode,   I didn't receive any coins in the wallets (server and personal wallet) ...

Reading Digibyte Groestl pool technical specification , I see  that Digibyte's Groestl implemetantion is the same  to Myriadcoin Groestl, currently I'm mining here : https://v2.cryptopoolmining.com/dgb-groestl/  without issues 

But I have some questions, :

a) Why in Scrypt mode I don't receive coins after 10 hrs ?
b) Is possible integrate Myriadcoin Groestl algo to you stratum server ? ...


About "a" question,  What configurations / logs files need from my server? I can help you in all test process  ...

Thanks for your time and effort to develop this nice stratum server 

Success!

[bonesoul]

Hi andr0x,

Thanks for your kind words.

First of all do you have enough hash-power to mine block alone? I personally prefer and suggest guys to first run with testnet daemon, so that you can make sure everything is working okay (in terms of mining & block submissions)

Other then that which version do you use? A release version or latest development tree?

Would be nice to see your debug.log file for Digibyte (https://github.com/CoiniumServ/CoiniumServ/wiki/How-to-ask-questions-and-report-bugs%3F) so I can check for any outstanding errors.

For the groestl part, does myriad-coin or digibyte-groestl use a specific groestl implementation? If not we already have the groestl implementation in https://github.com/CoiniumServ/CoiniumServ/blob/develop/src/CoiniumServ/Cryptology/Algorithms/Groestl.cs (which though is not tested).

You can give a try within a digibyte-groestl testnet for example.

[andr0x]

Hi bonesoul, thanks for fast response!

I'll respond you between quotes

Hi andr0x,

Thanks for your kind words.

First of all do you have enough hash-power to mine block alone? I personally prefer and suggest guys to first run with testnet daemon, so that you can make sure everything is working okay (in terms of mining & block submissions)

Currently in groestl I have 15 MH/s by now. You are right, Is a good idea test all in testnet daemon, I will run some test there  .

Other then that which version do you use? A release version or latest development tree?

I'm working directly with last development tree, I see few mins ago, that you commited some changes, I'll do a pull to update my copy  

Would be nice to see your debug.log file for Digibyte (https://github.com/CoiniumServ/CoiniumServ/wiki/How-to-ask-questions-and-report-bugs%3F) so I can check for any outstanding errors.

Sure, I'll run some test in daemon test mode before, and later I'll send to you all related logs files ( https://github.com/CoiniumServ/CoiniumServ/wiki/How-to-ask-questions-and-report-bugs%3F )

For the groestl part, does myriad-coin or digibyte-groestl use a specific groestl implementation? If not we already have the groestl implementation in https://github.com/CoiniumServ/CoiniumServ/blob/develop/src/CoiniumServ/Cryptology/Algorithms/Groestl.cs (which though is not tested).

You can give a try within a digibyte-groestl testnet for example.

I'm not 100% sure if digibyte use a specific groestl implementation, I'm based on this comment : https://bitcointalk.org/index.php?topic=408268.msg8888673#msg8888673  and in this pool Digibyte's Groestl information : https://v2.cryptopoolmining.com/dgb-groestl/index.php

But if I check digibyte network information directly from daemon it say  "difficulty_groestl" : 127.54058916 " and official thread, algo section it say clearly "Groestl" : https://bitcointalk.org/index.php?topic=408268.0 I'm bit confused  

I'll run some runs in testnetwork in groestl algo before , and later I'll send to you all logs files  

Thanks for all bonesoul and have a nice day!