Hi Bert,
Thanks for the reply. I did check the source code and thats whats puzzled me you see. As far as I can see, there is only one section that will print the following (and thats the section you highlighted):
(remote_host, auth_user, "Y", NULL, NULL, hexstr)
But thats not what I saw in the log. There was no 'NULL' for upstream_result. it was 'N'
However, thats what I saw in the log:
[2011-06-15 11:51:3.691804] ::ffff:87.194.1.1 test Y N - 000000015d59759d9d64a30622943f5ad37efcad184935b5de6e84bf00000a81000000005508473 8be6f076686f2a3c98f61e19659a18908788fe79f7fa2fa0ed439d8144df89ca51a1d932ff3fde9 7400000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000
Ive checked in the mysql DB and upstream_result written in there with the 'N' too:
select * from shares where solution like '000000015d59759d9d64a30622943f5ad37efcad184935b5de6e84bf00000a81000000005508473%';
+------+------+---------------------+----------+------------+-----------------+--------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| id | time | rem_host | username | our_result | upstream_result | reason | solution |
+------+------+---------------------+----------+------------+-----------------+--------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------+
| 3228 | 2011-06-15 11:51:03 | ::ffff:87.194.1.1 | test | Y | N | NULL | 000000015d59759d9d64a30622943f5ad37efcad184935b5de6e84bf00000a81000000005508473 8be6f076686f2a3c98f61e19659a18908788fe79f7fa2fa0ed439d8144df89ca51a1d932ff3fde9 7400000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000
My guess would be this section that has caused it
sharelog(remote_host, auth_user,
srv.easy_target ? "Y" : *json_result ? "Y" : "N",
*json_result ? "Y" : "N", NULL, hexstr);
but then I dont fully understand the reasons why pushpool would think the share work is enough to submit to bitcoind, but then get an upstream result of 'N' ?
Sorry if im sounding a bit thick.