Do you mean it is reported as zero? Bitcoin frontends usually display hash rates in MH/s, so that may be the cause.
No no I fixed it with nushor's help, I had share history with pushpool screwed up.
It was the Bitcointalk forum that inspired us to create Bitcointalksearch.org - Bitcointalk is an excellent site that should be the default page for anybody dealing in cryptocurrency, since it is a virtual gold-mine of data. However, our experience and user feedback led us create our site; Bitcointalk's search is slow, and difficult to get the results you need, because you need to log in first to find anything useful - furthermore, there are rate limiters for their search functionality.
The aim of our project is to create a faster website that yields more results and faster without having to create an account and eliminate the need to log in - your personal data, therefore, will never be in jeopardy since we are not asking for any of your data and you don't need to provide them to use our site with all of its capabilities.
We created this website with the sole purpose of users being able to search quickly and efficiently in the field of cryptocurrency so they will have access to the latest and most accurate information and thereby assisting the crypto-community at large.
"stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, so$
## server.json
{
# network ports
"listen" : [
# binary protocol (default), port 8342
{ "port" : 8123 },
# HTTP JSON-RPC protocol, port 8341
{ "port" : 8080, "protocol" : "http-json" },
# HTTP JSON-RPC protocol, port 8344,
#proxy is most likely your external ip address if your running a public pool
# requests to us | "proxy" should be set to your ip address that people will connect through
{ "port" : 8344, "protocol" : "http-json",
"proxy" : "192.-.-.-" },
# binary protocol, localhost-only port 8338
# host is most likely your localhost address
{ "host" : "127.0.0.1", "port" : 8338, "protocol" : "binary" }
],
# database settings
"database" : {
"engine" : "mysql",
"host" : "localhost",
"port" : 3306,
#database name
"name" : "mmcfe",
#database user
"username" : "-",
#database password
"password" : "-",
#enable sharelog | to insert share data or sometimes known as "work"
"sharelog" : true,
"stmt.pwdb":"SELECT password FROM pool_worker WHERE username = ?",
"stmt.sharelog":"INSERT INTO shares (rem_host, username, our_result, upstream_result, reason, so$
},
#uncoment this when you want to use memcached (Recommended for servers over 1.5gb of ram)
# cache settings
#"memcached" : {
# "servers" : [
# { "host" : "127.0.0.1", "port" : 11211 }
# ]
#},
"pid" : "/home/pushpool/pushpoold.pid",
# overrides local hostname detection
"forcehost" : "localhost.localdomain",
"log.requests" : "/home/pushpool/request.log",
"log.shares" : "/home/pushpool/shares.log",
# the server assumes longpolling (w/ SIGUSR1 called for each blk)
"longpoll.disable" : false,
# length of time to cache username/password credentials, in seconds
"auth.cred_cache.expire" : 75,
# RPC settings
#Bitcoind Protocal settings
#Host were bitcoind can be found on the network
"rpc.url" : "http://127.0.0.1:9332/",
#Username & password to connect to bitcoind
"rpc.user" : "-",
"rpc.pass" : "-",
# rewrite returned 'target' to difficulty-1?
"rpc.target.rewrite" : true
}