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.

do you have 4gb of ram? try using -j1 instead of the -j$(nproc) or whatever

I had the same issue

abberant[m]: Nope just 1Gb. I will try to recompile ...

post the error message

<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 libera.ems.host/_matrix/media/r0/do…cd6c36a3f7affd0f0b9b700320390b93603)

It happens after 43% of the code compiled.

need full log, please post to paste.debian.net

and this is with -j1?

abberant[m]: yes.

I will recompile again with the -j$(nproc) flag.

that won't fix it

it will (possible) make it worse lol

your log doesn't contain the error, post a full log

where the log file is saved?

there is no file, just copy it

from screen

Sent to paste.debian.net.

shadowfax-87[m]: monero-project/monero #7953/files

add this release-rpi target to Makefile and then try `make release-rpi`

I could if sworn reading a swap file was needed to compile on low ram pi's

Now the compiler is stucked at around 29% ...

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?

I'm just going to assume those are references to the base one to compare versions...

I am actually think whether the low memory could be an issue to compile. I will try another approach tomorrow. I am UTC-3.

yes, low memory will definitely give you issues with compiling moneord, you need at least 3gb IMO and only run one job

4gb is ideal

nonono... 4gb is minimal requirement. 64gb is ideal ;)

abberant[m]: you need the modified p2pool, and its pr was merged on a monero branch. it is still not released

oh at least it got merged, sweet

thanks as usual for info 👍

github.com/monero-project/monero/commits/release-v0.17 has it

wait what is the hashrate raffle and how to join it?

mightysnowman[m]: provided by XvB xmrvsbeast.com/p2pool

ye but how to join it

see that page

Register/Update at the bottom

dang it I need to have open ports?

I need to give my p2pool node access in the registration?

they redirect miners to your instance

you can have *another* p2pool instance elsewhere

with same wallet address

can I update the ip and port of the node every day?

there's one service that can make a port on my pc open but ip and the public port randomizes everyday

use dyn-dns

noip.com and similar sites

public port changes too? Not sure then

yeah noip doesnt allow to update the port

but yes, you can update it every day

save the "pin" you are given

okay then I should be fine

wait for how long the winned hashrate stays?

whatever amount XvB gives you

20m, 6h, 2h :)

check history

we have had up to 5 MH/s of raffle

peer list: 518

Real peer list is probably 150 or so

dynamic IPs mess it up

can someone test if my p2pool node is reachable from outside? 35.157.111.131:17828

seems to work, even through VPN

cool

the thing with the port forwarding service thing is that it has no udp, only tcp

do any of the monero related stuff use udp?

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.

Everything is using tcp (both monerod and p2pool)

^

hmm.. xvb node gives me 1 more outputs then my own node, is this normal? also the weight is different. Do these matter?

what weight? That node might see different set of transactions in mempool

1 more output - it can mine to a wallet that's not in PPLNS window, for example

ah right

ah yes, as soon as I start mining on p2pool again monero rng god decides to hit with the 400% block

hyc is it really safe to run two monerod instances with the same data dir? SChernykh/p2pool #49

^ interested on that

"added support for multiple daemons using the same LMDB database" from that reddit link

sounds sketchy

Also what is the fail count on the raffle? how often the fail count gets increased when connection fails?

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

okay I have new developments

looks like shares that should be accepted are being rejected

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...

I have plenty of connections and am getting new blocks live

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

It verifies all blocks you have, saved and new abberant[m]

that sync is normal as there is no file to read from

ok

There is the block cache it fetches blocks from

but it treats it like a local network source

well yes that but normally its all in memory right?

could shares getting rejected be cause of the daemon or only p2pool?

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

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

how would it accept every share but ones with enough diff to be submitted to the network :(

sech1 in general yes it's safe, but I don't think there's any use case any more

originally it was to allow multiple monerods on different networks to use the same DB

but now one monerod can talk on tor/i2p/clearnet simultaneously

so I can't see why anyone would need that feature now

abberant do you get any shares on p2pool side? What's in p2pool status?

like low diff shares?

also half the time I get this... (full message at libera.ems.host/_matrix/media/r0/do…26bfcdd9777ff312ee82f1fef22ab920341)

> <@abberant:matrix.org> ```... (full message at libera.ems.host/_matrix/media/r0/do…893f42553c7d12ea7476ade73dfc6b4e2a0)

> <@abberant:matrix.org> also half the time I get this... (full message at libera.ems.host/_matrix/media/r0/do…61f4b9ce058d785cf4eff83c005840fcdfb)

@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

works.

can also run clusters for load balancing without using tons of storage

Try to run with loglevel 5, you can see which peers your p2pool tries to connect to and what happens

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