Payout module not paying

[ghost]

Hello,

I have problems regarding the payout module. No miner has been paid but I've got 100 WEB in the etherbase account mentioned in the webchaind config. So I think it's an error with the payout module. The console says every minute:

No payees that have reached payout threshold

Every module is separated on different servers (they all work fine), here is the payout config:

{
"threads": 2,
        "coin": "web",
        "name": "payout",

        "upstreamCheckInterval": "5s",
        "upstream": [
                {
                        "name": "main",
                        "url": "http://192.168.1.225:39573",
                        "timeout": "10s"
                }
        ],

        "redis": {
                "endpoint": "192.168.1.226:6379",
                "poolSize": 10,
                "database": 0,
                "password": ""
        },

        "payouts": {
                "enabled": true,
                "requirePeers": 2,
                "interval": "1m",
                "daemon": "http://192.168.1.225:39573",
                "timeout": "10s",
                "address": "0xd9be691b73bc601390052363fff11e5d57e1ad2a",
                "gas": "21000",
                "gasPrice": "1000000000",
                "autoGas": true,
                "threshold": 1000000000,
                "bgsave": false
        },
}

Kind regards, Djitn

[lukaszmatczak]

Hello Payout module config looks OK. It can be also problem with unlocker module. Could you paste here its config and logs? And please tell if any miner have balance over 1 WEB? Or balances are just 0?

[ghost]

Thanks for your quick response.

This is the unlocker module's configuration:

{
        "threads": 2,
        "coin": "web",
        "name": "unlocker",

        "upstreamCheckInterval": "5s",
        "upstream": [
                {
                        "name": "main",
                        "url": "http://192.168.1.225:39573",
                        "timeout": "10s"
                }
        ],

        "redis": {
                "endpoint": "192.168.1.226:6379",
                "poolSize": 10,
                "database": 0,
                "password": ""
        },

        "unlocker": {
                "enabled": true,
                "poolFee": 1.0,
                "poolFeeAddress": "0x3aa63e102d3c731998cacfb6e85035026b9bdb30",
                "devDonate": 1.0,
                "depth": 32,
                "immatureDepth": 16,
                "keepTxFees": false,
                "interval": "1m",
                "daemon": "http://192.168.1.225:39573",
                "timeout": "10s"
        },
}

and as error log, I get this every minute: (the first time I checked this... This is the problem I guess)

Unlocking suspended due to last critical error: dial tcp 192.168.1.226:6379: connect: no route to host

All the balances of every miner stays on 0 WEB.

This is a short log of the redis server that is reachable by every module running on every server:

okt 11 20:56:50 ubuntu7 redis-server[588]: 588:M 11 Oct 20:56:50.074 * 10 changes in 300 seconds. Saving...
okt 11 20:56:50 ubuntu7 redis-server[588]: 588:M 11 Oct 20:56:50.074 * Background saving started by pid 1711
okt 11 20:56:50 ubuntu7 redis-server[588]: 1711:C 11 Oct 20:56:50.117 * DB saved on disk
okt 11 20:56:50 ubuntu7 redis-server[588]: 1711:C 11 Oct 20:56:50.118 * RDB: 0 MB of memory used by copy-on-write
okt 11 20:56:50 ubuntu7 redis-server[588]: 588:M 11 Oct 20:56:50.175 * Background saving terminated with success
okt 11 21:01:51 ubuntu7 redis-server[588]: 588:M 11 Oct 21:01:51.025 * 10 changes in 300 seconds. Saving...
okt 11 21:01:51 ubuntu7 redis-server[588]: 588:M 11 Oct 21:01:51.025 * Background saving started by pid 1713
okt 11 21:01:51 ubuntu7 redis-server[588]: 1713:C 11 Oct 21:01:51.065 * DB saved on disk
okt 11 21:01:51 ubuntu7 redis-server[588]: 1713:C 11 Oct 21:01:51.066 * RDB: 0 MB of memory used by copy-on-write
okt 11 21:01:51 ubuntu7 redis-server[588]: 588:M 11 Oct 21:01:51.126 * Background saving terminated with success

The redis server is accessable by the server that is running the unlocker module.

[lukaszmatczak]

You can try to restart unlocker module. If error will happen after restart it means that you have connection problem between unlocker and redis server.

[ghost]

That resolved the issue... Never thought of doing that. Now I have another issue, the payout module knows who to pay to but it says:

“Account is locked”

[lukaszmatczak]

How did you execute webchaind? Command must contain: --unlock <pool_address> --password /path/to/file_with_password

[ghost]

Is the password file automatically created or do I need to create it myself?

[lukaszmatczak]

Need to create manually. It should contain only password without any additional characters.

[ghost]

I have succesfully unlocked the pool account, thanks! Now I got this error:

Unable to start payouts, number of peers on a node is less than required 20

[lukaszmatczak]

Seems like requirePeers in config of your payout module is set to 20. You can set it to lower values, for example 2.

[ghost]

If I set this to 2 it also says:

Unable to start payouts, number of peers on a node is less than required 2

And after some time it says again:

Account is locked

[lukaszmatczak]

It can be problem with firewall. Do you have both TCP and UDP port 31440 opened?