00:18:05 <hyc> I had 142 accepted shares and 3 rejected
00:18:12 <hyc> never noticed rejected shares before
06:16:07 <sech1> hyc what was the reject reason? xmrig should show it
08:26:29 <hyc> [2021-08-27 23:27:26.372]  cpu      rejected (81/1) diff 383076 "Invalid job id" (15539 ms)
08:26:30 <hyc> [2021-08-27 23:27:26.372]  net      no active pools, stop mining
08:26:31 <hyc> [2021-08-27 23:27:31.497]  net      use pool 192.168.1.214:3333  192.16
08:29:21 <hyc> https://paste.debian.net/1209386/
08:29:31 <hyc> looks like it was just stale
08:29:50 <hyc> diff 383076 was on line 4
09:47:19 <sech1> share was rejected at 23:27:26.372 and was sent to p2pool at 23:27:10.833. p2pool sent 4 new jobs between these two points and it only remembers last 4 job IDs. Which means that this share reached p2pool and was verified sometime between 24.218 and 26.372, 14 seconds after it was sent. It's something with your network again
09:48:04 <sech1> or something with your p2pool build...
12:05:46 <garth> Have we crossed 3GHZ on mainnet yet? Seems like we are getting awfully close
12:53:29 <nioc> 2.95 now, it has been between 2.64 and 2.84 for the past week 
13:31:02 <hyc> yeah I see a few connection timed out messages here, so something is still flaky with the mac
13:32:04 <hyc> xmrig says ping time 89ms which is ridiculously slow for this LAN
13:35:13 <hyc> and once again p2pool was reporting a lower height than monerod actually had
13:35:26 <hyc> so maybe zmq-pub is sending out of date info
13:39:15 <hyc> heh. even the xmrig miner on the mac reports a ping time of 34ms, that's localhost
13:40:54 <hyc> seems like macos is just a pig
13:42:31 <hyc> or libuv sucks
13:42:59 <hyc> either or both could be true
13:52:45 <sech1> or libuv on macos sucks
13:58:07 <hyc> why does p2pool need to execute randomx itself? why doesn't it just trust the hashes its miners submit?
14:00:09 <hyc> \i suppose if p2pool sent bad hashes to monerod it would eventually get banned
14:03:27 <hyc> never mind... still it would be nice not to need up to 3 instances of randomx on a machine. if we isolate randomx hasing to its own process
14:03:49 <hyc> and let monerod and p2pool send data to it over a socket for verification
14:04:02 <hyc> would reduce footprint
14:04:37 <hyc> xmrig itself could serve that purpose
14:04:57 <hyc> meanwhile configure a trusted client mode in monerod and p2pool for a local xmrig
14:45:27 <sech1> why would p2pool trust other nodes without checking PoW on blocks they send?
14:45:43 <hyc> right, it can't.
21:11:31 <sech1> New hashrate ATH at block https://xmrchain.net/block/2437045 - 3012.8 MH/s