<p>First of all I thought that you were using a bitcoin pushpool as your primary software for a litecoin pool. But I guess you've checked that?
Otherwise, try this recomended pushpool fork instead, which worked for me: (For LTC) <a href="https://github.com/ArtForz/pushpool" rel="nofollow">https://github.com/ArtForz/pushpool</a></p>

<p>This one works for me, but ideally you would want to use the stratum software for mining purpose. (If you have clients connecting with LP/Getwork, you can add the stratum-proxy locally on your server)</p>

CC BY-SA 3.0
2013-06-11T20:43:24.523Z
I thought pushpool was the same regardless of whether it's serving BTC or LTC? If that's not the case, how would I check? The connected litecoin miners do get handed jobs to crunch so I've assumed that the pushpoold->litecoind set was correct. But can't hurt to double check. re Stratum: I am planning to add Stratum once I've got pushpool working, but haven't got that far yet. Thanks for the recommendation there though.
laumars
CC BY-SA 3.0
2013-06-11T20:57:02.103Z
Meant to add, I'll bare ArtForz fork in mind if this stackexchange question doesn't find the answer (to be honest, I'm starting to think it is just the fork I'm using - but I want to eliminate the other possibilities first). Thanks :)
laumars
CC BY-SA 3.0
2013-06-11T23:02:55.007Z
@laumars I think that is your reason really. I was starting out with a different pushpool build and my workers were never submitting shares. I suspected something to be very wrong, and decided to follow a small guide instead (they used the ArtForz fork) and poof it worked. :) Can't tell you how or why
Robin Jonsson
CC BY-SA 3.0
2013-06-12T14:19:56.110Z
update: that worked.
laumars
CC BY-SA 3.0
2013-06-12T18:55:24.170Z
Good :) Happy that it got resolved! Me myself is also running a pool: http://litepool.in
Robin Jonsson
CC BY-SA 3.0
2013-06-11T12:58:32.147Z
2013-06-11T12:58:32.147Z
Robin Jonsson
<p>Whenever I connect miners to pushpoold (connected to litecoind), it's not updating the shares table in MySQL (which in turn means the stats on mmcfe isn't updating). I'm pretty certain the database settings are correct as pushpool can read the users table to authenticate the miners and it's not an mmcfe config because I've inspected the shares table independently of mmcfe.</p>

<p>My pushpool server.json file is as follows:</p>

<pre><code>{
    "listen" : [
            { "host": "domain.com", "port" : 8336 },
            { "host": "domain.com", "port" : 8337, "protocol" : "http-json" },

            # HTTP JSON-RPC protocol, port 8339,
            # with trusted proxy appserver.example.com forwarding
            # requests to us
            #{ "port" : 8337, "protocol" : "http-json",
            #  "proxy" : "appserver.example.com" },

            # binary protocol, localhost-only port 8338
            { "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }

    ],

    "database" : {

            "engine" : "mysql",

            "host" : "localhost",

            "port" : 3306,

            "name" : "db",
            "username" : "user",
            "password" : "pass",

            "sharelog" : true,

            "stmt.pwdb" :
              "SELECT password FROM pool_worker WHERE username = ?",

            "stmt.sharelog" :
             "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

    },

    "memcached" : {
            "servers" : [
                    { "host" : "127.0.0.1", "port" : 11211 }
            ]
    },

    "pid" : "/opt/pushpool/tmp/pushpoold.pid",

    "forcehost" : "localhost",

    "log.requests" : "/opt/pushpool/tmp/request.log",
    "log.shares" : "/opt/pushpool/tmp/shares.log",

    "longpoll.disable" : false,

    "auth.cred_cache.expire" : 75,

    "rpc.url" : "http://127.0.0.1:8332/",
    "rpc.user" : "user",
    "rpc.pass" : "pass",

    "rpc.target.bits" : 21,

    "work.expire" : 120,

    "roll.ntime.disable" : false
}
</code></pre>

<p>I've already searched through stackexchange as well as the wider web, so I <em>think</em> I've picked up on all the basic mistakes (eg not including stmt.sharelog and the rpc.target.bits), but I suspect this is still a configuration problem and that I've overlooked something really stupid.</p>

<p>Overview specs:</p>

<ul>
<li>Debian Wheezy 64bit</li>
<li>pushpool (repo: <a href="https://github.com/jgarzik/pushpool" rel="nofollow">https://github.com/jgarzik/pushpool</a>)</li>
<li>litecoind</li>
<li>mysql  Ver 14.14 Distrib 5.5.31, for debian-linux-gnu (x86_64) using readline 6.2</li>
</ul>

CC BY-SA 3.0
2013-06-10T22:58:49.063Z
What happens when you run stmt.sharelog manually, putting in test values for the `?` marks?
Nick ODell
CC BY-SA 3.0
2013-06-11T20:57:48.870Z
Same thing. No data inserted into the db and no error outputted to the logs.
laumars
<litecoin><pushpool>
pushpool not updating mysql
laumars
# pushpool not updating mysql

(Asked by: username_0 on 2013-06-10)

Whenever I connect miners to pushpoold (connected to litecoind), it's not updating the shares table in MySQL (which in turn means the stats on mmcfe isn't updating). I'm pretty certain the database settings are correct as pushpool can read the users table to authenticate the miners and it's not an mmcfe config because I've inspected the shares table independently of mmcfe.

My pushpool server.json file is as follows:

```
{
    "listen" : [
            { "host": "domain.com", "port" : 8336 },
            { "host": "domain.com", "port" : 8337, "protocol" : "http-json" },

            # HTTP JSON-RPC protocol, port 8339,
            # with trusted proxy appserver.example.com forwarding
            # requests to us
            #{ "port" : 8337, "protocol" : "http-json",
            #  "proxy" : "appserver.example.com" },

            # binary protocol, localhost-only port 8338
            { "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }

    ],

    "database" : {

            "engine" : "mysql",

            "host" : "localhost",

            "port" : 3306,

            "name" : "db",
            "username" : "user",
            "password" : "pass",

            "sharelog" : true,

            "stmt.pwdb" :
              "SELECT password FROM pool_worker WHERE username = ?",

            "stmt.sharelog" :
             "INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, solution) VALUES (?, ?, ?, ?, ?, ?)"

    },

    "memcached" : {
            "servers" : [
                    { "host" : "127.0.0.1", "port" : 11211 }
            ]
    },

    "pid" : "/opt/pushpool/tmp/pushpoold.pid",

    "forcehost" : "localhost",

    "log.requests" : "/opt/pushpool/tmp/request.log",
    "log.shares" : "/opt/pushpool/tmp/shares.log",

    "longpoll.disable" : false,

    "auth.cred_cache.expire" : 75,

    "rpc.url" : "http://127.0.0.1:8332/",
    "rpc.user" : "user",
    "rpc.pass" : "pass",

    "rpc.target.bits" : 21,

    "work.expire" : 120,

    "roll.ntime.disable" : false
}

```

I've already searched through stackexchange as well as the wider web, so I *think* I've picked up on all the basic mistakes (eg not including stmt.sharelog and the rpc.target.bits), but I suspect this is still a configuration problem and that I've overlooked something really stupid.

Overview specs:

* Debian Wheezy 64bit
* pushpool (repo: <https://github.com/jgarzik/pushpool>)
* litecoind
* mysql Ver 14.14 Distrib 5.5.31, for debian-linux-gnu (x86\_64) using readline 6.2

**Tags:** litecoin, pushpool

> **Comments:**
> **username_1**: What happens when you run stmt.sharelog manually, putting in test values for the `?` marks?  
> **username_0**: Same thing. No data inserted into the db and no error outputted to the logs.  

---

## 1 answers

### Answer by username_2 on 2013-06-11. Score: 0 | Accepted answer

First of all I thought that you were using a bitcoin pushpool as your primary software for a litecoin pool. But I guess you've checked that?
Otherwise, try this recomended pushpool fork instead, which worked for me: (For LTC) <https://github.com/ArtForz/pushpool>

This one works for me, but ideally you would want to use the stratum software for mining purpose. (If you have clients connecting with LP/Getwork, you can add the stratum-proxy locally on your server)

> **Comments:**
> **username_0**: I thought pushpool was the same regardless of whether it's serving BTC or LTC? If that's not the case, how would I check? The connected litecoin miners do get handed jobs to crunch so I've assumed that the pushpoold->litecoind set was correct. But can't hurt to double check. re Stratum: I am planning to add Stratum once I've got pushpool working, but haven't got that far yet. Thanks for the recommendation there though.  
> **username_0**: Meant to add, I'll bare ArtForz fork in mind if this stackexchange question doesn't find the answer (to be honest, I'm starting to think it is just the fork I'm using - but I want to eliminate the other possibilities first). Thanks :)  
> **username_2**: @username_0 I think that is your reason really. I was starting out with a different pushpool build and my workers were never submitting shares. I suspected something to be very wrong, and decided to follow a small guide instead (they used the ArtForz fork) and poof it worked. :) Can't tell you how or why  
> **username_0**: update: that worked.  
> **username_2**: Good :) Happy that it got resolved! Me myself is also running a pool: http://litepool.in  

---

