00:01:14 <DataHoarder> shouldn't take more than 5-10 minutes or so even if clean
00:01:35 <DataHoarder> maybe it hits the limit of how long you can be desync'd and get dropped from peers
00:02:03 <DataHoarder> backup the peer list and fully remove it, let it rebuild it
00:02:11 <hyc> dunno. it's been doing add_block: xxx" the whole time
00:02:15 <DataHoarder> cache is also only saved up after a full resync
00:02:30 <DataHoarder> what are you up to?
00:02:56 <hyc> working down to mainchain 3030856
00:03:06 <hyc> 3031154
00:03:25 <hyc> side height 6279370
00:03:32 <DataHoarder> that's about 9 hours ago
00:03:36 <DataHoarder> 3h more to go :D
00:03:41 <hyc> ugh
00:04:24 <DataHoarder> 10h 30m https://mini.p2pool.observer/share/6279370
00:04:56 <hyc> how far back is it going to go? 12 hours?
00:05:47 <DataHoarder> about so, two PPLNS windows + slightly extra
00:06:23 <DataHoarder> I should maybe make a "download compressed cache" feature on observer :D
00:06:31 <hyc> heh
00:06:33 <DataHoarder> client will still verify blocks there
00:06:49 <hyc> well, 12 hours back should overlap with when it was last online
00:07:12 <DataHoarder> there is this tool but it just uses the API https://git.gammaspectra.live/P2Pool/p2pool-observer/src/branch/master/cmd/apitocache/apitocache.go
00:07:24 <DataHoarder> also it's mini, which has larger blocks
00:07:36 <DataHoarder> many miner outputs, specially in first download
00:10:29 <hyc> ah, done.
00:10:38 <hyc> sheesh
00:11:07 <hyc> just over an hour
00:14:49 <m-relay> <o​frnxmr:monero.social> how is it if using --nocache ?
00:15:10 <m-relay> <o​frnxmr:monero.social> (im probably misremembering the flag)
00:16:02 <DataHoarder> probably about the same time as they had to download all the new blocks
00:16:20 <DataHoarder> it just doesn't lookup the cache at all (or saves them
00:17:05 <m-relay> <o​frnxmr:monero.social> Maybe just bad peers / slow download? 45mins sounds long
00:18:19 <m-relay> <o​frnxmr:monero.social> Sounds like 40mins longer than id think sounded normal (acceptable?)
00:18:20 <DataHoarder> 5Mbits and will get bad peers probably that way
00:18:41 <DataHoarder> it's somewhat latency sensitive for roundtrips too
00:18:55 <DataHoarder> afaik latest changes should have improved that
00:18:57 <m-relay> <o​frnxmr:monero.social> Ah, 5mbit not mb
00:19:04 <sech1> hyc maybe you caught some very slow peer who also didn't tell you about other peers... You need to check who you're connected to using "peers" command
00:19:39 <sech1> or are you syncing it on a potato SBC?
00:20:47 <sech1> immediate restart should sync fast because it will just load everything from the cache
00:21:47 <hyc> syncing it on an rk3588 with 32GB RAM, it's a fairly decent mini pc
00:22:25 <sech1> if restart with cache enabled is still very slow, I'd like to see log level 6 log of that
00:22:47 <hyc> ok I'll try restarting it now
00:24:03 <sech1> rk3588 has aes, right?
00:24:36 <hyc> yep
00:25:08 <hyc> seems to be going a lot faster now. it's with no-randomx, so keeping monerod 100% busy
00:26:49 <hyc> and I see a lot of "using cached block" msgs flying by
00:28:58 <hyc> done
00:29:14 <hyc> about 5 minutes, yeah
00:29:30 <sech1> so it was probably a slow peer. P2Pool tries to choose a peer with the lowest ping, but if this peer turns out to be slow, it's just a bad luck
00:30:27 <hyc> ok. never happened before
00:31:26 <sech1> I actually run p2pool without the cache, and it always restarts quickly
00:31:38 <sech1> so never happened to me too
00:36:00 <hyc> as a matter of fact, I remember seeing a message about too slow ping time on that startup
00:36:47 <hyc> I assumed it was complaining just because the 4G connection has generally slow pings\
02:13:52 <QuickBASIC> 5Mbit on 4G? You live in the boonies hyc?
03:44:41 <hyc> yep
04:07:20 <QuickBASIC> I lived in bumfuck Bavaria for a year and had miserable speeds on mobile and cable and swore to never live in rural Europe ever again lol.
04:08:05 <hyc> the gigabit fiber has been working fine for like 2 years.
04:08:21 <hyc> only died on me once before, when someone ran their digger thru the line
04:10:20 <QuickBASIC> I wish. Fiber is so sparse in America. Cable isn't bad though I get 250 down 50 up.
04:10:56 <QuickBASIC> "Business class" b/c wifey and I work remote.
07:42:11 <sech1> hyc running with --no-randomx also adds your node ping time to each block's sync time. So if it complained about "too slow ping", it could've been your node
10:01:24 <m-relay> <c​hch3003:monero.social> Hello! Trying to mine on my Macbook M1 Max with P2pool Mini from official GUI but it crashes directly with "Timed out, local node is not responding after 120 seconds. Please check your wallet and daemon log for errors. You can also try to start monerod manually. Exiting p2pool. Please check that port 18083 is available." Any idea what I can do?
10:05:33 <sech1> It's something with your Monero node. It's better to ask in #monero-gui