A difficulty 1 share.
That target is 2^(256-32)-1, the maximum possible target for most hardware (H=0).
That message is printed when a miner returns work that doesn't match the target it was sent, meaning that there's a bug or other problem.
EDIT: That returned work has a hash that isn't low at all. What mining hardware are you using?
Thank you very much for that info. That was my fear.
As for hardware, I'm using Antminer U2s. But, I don't think the hardware is sat fault. If I point my Ants (via Bfgminer) directly at p2pool, it works. I don't get those messages, and the p2pool stats page displays a local hash rate.
This problem arises when I first point my miners to a proxy I'm writing, and then the proxy talks to p2pool. The stratum communication looks identical to me:
Message to p2pool:
{"params":["12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF","226858380923200241282647501746235717849","08000000","534ddc22","b9609317"],"id":800,"method":"mining.submit"}
Response from p2pool:
{"id":800,"error":null,"result":true}
And then in p2pool's console output I see these:
2014-04-15 20:26:07.905276 Worker 12uCQa1rEBxQutWUkXE2AA6LnhfrAPJpgF submitted share with hash > target:
2014-04-15 20:26:07.905412 Hash: ef95748110ef4e9612d216da2cb08d1de41e28b872d7761aaff7db538d1f084b
2014-04-15 20:26:07.905520 Target: ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
I'm still trying to debug what I've done wrong, but I figured stopping in here and double checking my understanding of p2pool's message was a good start.
Still confused as to why I'm getting a "result: true", despite p2pool claiming the hash doesn't meet difficulty 1 though.