00:50:54 <shadowfax-87[m]> Does anyone have experience compiling the souce code on Raspberry Pi 3? The P2Pool is compiling ok, but I am getting error messages compiling the monero binaries. I am using a RPi3 with Ubuntu Server 21.0 64-bit.
00:52:00 <abberant[m]> do you have 4gb of ram? try using -j1 instead of the -j$(nproc) or whatever
00:52:04 <abberant[m]> I had the same issue 
00:55:01 <shadowfax-87[m]> abberant[m]: Nope just 1Gb. I will try to recompile ... 
00:55:30 <selsta> post the error message
01:02:08 <shadowfax-87[m]> <selsta> "post the error message" <- make[3]: *** [contrib/epee/src/CMakeFiles/epee.dir/build.make:82: contrib/epee/src/CMakeFiles/epee.dir/byte_slice.cpp.o] Error 1... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/4ea3bcd6c36a3f7affd0f0b9b700320390b93603)
01:02:42 <shadowfax-87[m]> It happens after 43% of the code compiled.
01:02:51 <selsta> need full log, please post to paste.debian.net
01:05:07 <abberant[m]> and this is with -j1?
01:05:28 <shadowfax-87[m]> abberant[m]: yes.
01:06:28 <shadowfax-87[m]> I will recompile again with the -j$(nproc) flag.
01:06:44 <selsta> that won't fix it
01:06:54 <selsta> it will (possible) make it worse lol
01:07:07 <selsta> your log doesn't contain the error, post a full log
01:07:38 <shadowfax-87[m]> where the log file is saved?
01:10:32 <selsta> there is no file, just copy it
01:10:36 <selsta> from screen
01:14:48 <shadowfax-87[m]> Sent to paste.debian.net.
01:16:59 <selsta> shadowfax-87[m]: https://github.com/monero-project/monero/pull/7953/files
01:17:24 <selsta> add this release-rpi target to Makefile and then try `make release-rpi`
01:30:02 <EDad> I could if sworn reading a swap file was needed to compile on low ram pi's
01:46:08 <shadowfax-87[m]> Now the compiler is stucked at around 29% ...
03:16:34 <abberant[m]> Do you still need the modified monerod to use p2pool? I'm looking at seth's docker guide to see if it can save me time and it looks like the sources are from the vanilla monerod?
03:27:58 <abberant[m]> I'm just going to assume those are references to the base one to compare versions...
03:34:53 <shadowfax-87[m]> I am actually think whether the low memory could be an issue to compile. I will try another approach  tomorrow. I am UTC-3.
05:30:20 <xmrvsbeast[m]> yes, low memory will definitely give you issues with compiling moneord, you need at least 3gb IMO and only run one job
05:33:19 <xmrvsbeast[m]> 4gb is ideal
06:17:45 <jaska087> nonono... 4gb is minimal requirement. 64gb is ideal ;)
08:19:33 <DataHoarder> abberant[m]: you need the modified p2pool, and its pr was merged on a monero branch. it is still not released
08:20:24 <abberant[m]> oh at least it got merged, sweet
08:20:36 <abberant[m]> thanks as usual for info 👍
08:21:37 <DataHoarder> https://github.com/monero-project/monero/commits/release-v0.17 has it
09:44:20 <mightysnowman[m]> wait what is the hashrate raffle and how to join it?
09:44:54 <DataHoarder> mightysnowman[m]: provided by XvB https://xmrvsbeast.com/p2pool/
09:45:23 <mightysnowman[m]> ye but how to join it
09:45:28 <DataHoarder> see that page
09:46:00 <DataHoarder> Register/Update at the bottom
09:46:28 <mightysnowman[m]> dang it I need to have open ports?
09:46:47 <mightysnowman[m]> I need to give my p2pool node access in the registration?
09:46:49 <DataHoarder> they redirect miners to your instance
09:46:57 <DataHoarder> you can have *another* p2pool instance elsewhere
09:47:02 <DataHoarder> with same wallet address
09:48:37 <mightysnowman[m]> can I update the ip and port of the node every day?
09:49:12 <mightysnowman[m]> there's one service that can make a port on my pc open but ip and the public port randomizes everyday
09:49:21 <sech1> use dyn-dns
09:49:50 <sech1> noip.com and similar sites
09:50:28 <sech1> public port changes too? Not sure then
09:50:41 <mightysnowman[m]> yeah noip doesnt allow to update the port
09:52:35 <DataHoarder> but yes, you can update it every day
09:53:09 <DataHoarder> save the "pin" you are given
09:54:08 <mightysnowman[m]> okay then I should be fine
10:03:40 <mightysnowman[m]> wait for how long the winned hashrate stays?
10:06:05 <DataHoarder> whatever amount XvB gives you
10:06:12 <DataHoarder> 20m, 6h, 2h :)
10:06:15 <DataHoarder> check history
10:06:40 <DataHoarder> we have had up to 5 MH/s of raffle
10:10:13 <Inge> peer list: 518
10:12:54 <sech1> Real peer list is probably 150 or so
10:13:00 <sech1> dynamic IPs mess it up
10:35:51 <mightysnowman[m]> can someone test if my p2pool node is reachable from outside? 35.157.111.131:17828
10:48:46 <DataHoarder> seems to work, even through VPN
10:53:07 <mightysnowman[m]> cool
10:53:54 <mightysnowman[m]> the thing with the port forwarding service thing is that it has no udp, only tcp
10:54:08 <mightysnowman[m]> do any of the monero related stuff use udp?
11:17:14 <EDad> mightysnowman[m]: I am using noip as it's one of the options included with my router. The downside is my router only checks once a hour so there "could" be some downtime. I've hit the raffle twice so far with the setup. So it does work.
11:22:23 <sech1> Everything is using tcp (both monerod and p2pool)
12:17:53 <mfoolb> ^
12:27:18 <jaska087> hmm.. xvb node gives me 1 more outputs then my own node, is this normal? also the weight is different. Do these matter?
12:31:22 <sech1> what weight? That node might see different set of transactions in mempool
12:31:38 <sech1> 1 more output - it can mine to a wallet that's not in PPLNS window, for example
12:32:30 <jaska087> ah right
13:30:52 <mightysnowman[m]> ah yes, as soon as I start mining on p2pool again monero rng god decides to hit with the 400% block
13:35:10 <sech1> hyc is it really safe to run two monerod instances with the same data dir? https://github.com/SChernykh/p2pool/issues/49
13:36:00 <DataHoarder> ^ interested on that
13:36:51 <sech1> "added support for multiple daemons using the same LMDB database" from that reddit link
13:37:32 <jaska087> sounds sketchy
16:26:09 <mightysnowman[m]> Also what is the fail count on the raffle? how often the fail count gets increased when connection fails?
16:36:12 <pauliouk> fail count is how many times you've won the raffle, but haven't had a share in the X days it looks at. Also increases if the system can't connect to you
16:55:01 <abberant[m]> okay I have new developments
16:55:06 * abberant[m] sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/f8ee205aa1157694af9701dc3be9124ef30ca26c
16:55:21 <abberant[m]> looks like shares that should be accepted are being rejected
16:56:30 <abberant[m]> I'm not the only one on my monero node that I think is facing similar problems, any idea why this is? what could be making them get rejected...
16:58:35 <abberant[m]> I have plenty of connections and am getting new blocks live
17:05:14 <abberant[m]> also p2pool has to sync a ton of blocks everytime I restart, even if its only been like 10 seconds, idk if this is normal
17:10:02 <DataHoarder> It verifies all blocks you have, saved and new abberant[m] 
17:10:10 <jaska087> that sync is normal as there is no file to read from
17:10:23 <abberant[m]> ok
17:10:26 <DataHoarder> There is the block cache it fetches blocks from
17:10:39 <DataHoarder> but it treats it like a local network source
17:10:49 <jaska087> well yes that but normally its all in memory right?
17:13:11 <abberant[m]> could shares getting rejected be cause of the daemon or only p2pool?
17:13:50 <abberant[m]> the only thing different about my setup compared to everyone else is that I have zmq on 0.0.0.0 to bind to my public ip so that friends can connect
17:14:47 <abberant[m]> otherwise I've reinstalled everything and tried different versions and everything else I can think of and have been getting shares rejected for over a week now, I'm starting to think its not worth my effort
17:17:03 <abberant[m]> how would it accept every share but ones with enough diff to be submitted to the network :(
17:17:49 <hyc> sech1 in general yes it's safe, but I don't think there's any use case any more
17:18:10 <hyc> originally it was to allow multiple monerods on different networks to use the same DB
17:18:24 <hyc> but now one monerod can talk on tor/i2p/clearnet simultaneously
17:18:39 <hyc> so I can't see why anyone would need that feature now
17:18:56 <sech1> abberant do you get any shares on p2pool side? What's in p2pool status?
17:20:00 <abberant[m]> like low diff shares?
17:20:38 <abberant[m]> also half the time I get this... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/286b926bfcdd9777ff312ee82f1fef22ab920341)
17:21:05 <abberant[m]> > <@abberant:matrix.org> ```... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/70e90893f42553c7d12ea7476ade73dfc6b4e2a0)
17:21:19 <abberant[m]> > <@abberant:matrix.org> also half the time I get this... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/7711961f4b9ce058d785cf4eff83c005840fcdfb)
17:40:12 <QuickBASIC> @hyc> so I can't see why anyone would need that feature now. <--- someone will find a use case even if you can't think of it. Port forwards in and out of WSL suck so I sometimes I run monerod inside of WSL and point data-dir at /mnt/c/ProgramData/bitmonero (where Windows monerod.exe puts it) even though the daemon is running on Windows too it
17:40:12 <QuickBASIC> works.
17:41:26 <abberant[m]> can also run clusters for load balancing without using tons of storage
17:48:42 <sech1> Try to run with loglevel 5, you can see which peers your p2pool tries to connect to and what happens
17:49:30 <abberant[m]> going to try next, I cleared p2pool cache which I havent tried yet in recent memory so I'm going to see if it makes a difference