-
food4lyfe
Hey I need help with initializing a remote node on raspberry pi. I posted this on the #monero channel as well but I think this channel is more appropriate
-
food4lyfe
I tried running monerod using the Armv7 but it doesn't seem to work. It keeps crashing saying "Bus error". Anyone knows why?
-
m-relay
<k4r4b3y:karapara.net> Armv7 is currently unofficially not supported.
-
m-relay
<k4r4b3y:karapara.net> I remember trying monerod on my armv7 CPU smartphone and single board computer
-
m-relay
<k4r4b3y:karapara.net> on both platforms, monerod has crashed, with the same error as your, "Bus error."
-
m-relay
<k4r4b3y:karapara.net> I opened some github issues last year on this topic. We worked on the issue comments with luigi and hyc, but the result lead us nowhere.
-
food4lyfe
Ahh ic ic, all good then. I'll try to find another way around it. My raspi actually has ARMv8 but idk why it couldn't run it. Everytime I run it, it keeps saying "No files such file or directory" which then lead me to ARMv7. Anyways thanks m-relay!
-
m-relay
<k4r4b3y:karapara.net> what is the model of your raspi? 3B?
-
food4lyfe
Nope raspberry pi 4 model b
-
m-relay
<k4r4b3y:karapara.net> why don't you try the armv8?
-
food4lyfe
I did, couldn't run it. It keeps on saying "No such files or directory"
-
selsta
food4lyfe: what's the output of "file monerod"
-
food4lyfe
monerod: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=b29c5e0b2e68458d0b5ba3504c65c8bee4270d2d, with debug_info, not stripped
-
selsta
do you have at /lib/ld-linux-aarch64.so.1 ?
-
selsta
a file at
-
food4lyfe
No
-
moneromooo
Bus error means unaligned access or access to unmapped virtual memory. Probably the latter, as it tends to happen to LMDB in the face of corrupted database.
-
selsta
you need it to run the program
-
m-relay
<tobtoht:monero.social> food4lyfe: install the 64-bit version of the OS
-
selsta
-
selsta
I think that's your problem
-
food4lyfe
m-relay: I think I installed the 64-bit version. when using uname -a, it printed out aarch64
-
selsta
seems you have a 64bit kernel but 32bit OS according to that link, you need a 64bit OS
-
m-relay
<tobtoht:monero.social>
raspberrypi.com/software/operating-systems scroll down to 64-bit
-
food4lyfe
selsta: Yeah it seems like thats the problem. I'll reinstall the OS, I'll follow up after if there's anymore issues. Thanks selsta!
-
food4lyfe
m-relay: Yup, thanks for the link. I'll try that one. I'll let you know after I reinstalled it. Thanks for helping out m-relay
-
m-relay
<0xfffc:matrix.org> if you have objdump in that machine, "arm-none-linux-gnueabi-objdump -x monerod | grep NEEDED"
-
m-relay
<0xfffc:matrix.org> then investigate .so files with readelf --headers *.so
-
m-relay
<0xfffc:matrix.org> SIGBUS is really a different/deeper version of SIGSEGV.
-
food4lyfe
m-relay: I'm not familiar with objdump. I do have objdump but not the one you are referring to. Do you know which package has that binary?
-
xFFFC0000
yeah, samething. "objdump -x monerod | grep NEEDED"
-
food4lyfe
objdump gives out "objdump: monerod: file format not recognized"
-
xFFFC0000
now do readelf --headers monerod
-
xFFFC0000
as selsta mentioned, I expect something seriously wrong with that installation.
-
xFFFC0000
appears that you don't have a correct monerod file. elf headers are messed up. objdump should've worked. Anyway, readelf will tell more about the issue.
-
selsta
it's not the file
-
selsta
oh I misread, ignore me
-
food4lyfe
Yeah, readelf shows that in the program headers section it requires /lib/ld-linux-aarch64.so.1. Currently reinstalling it to the 64-bit OS version
-
xFFFC0000
anyway, the root is the one selsta mentioned, 64bit 32bit mismatch
-
xFFFC0000
s/root/root issue/
-
food4lyfe
I have to go. But thanks xFFFC0000, m-relay, selsta for the help
-
food4lyfe
If there are more issues with it, I'll ask it here :D
-
hyc
unmapped memory gets a SIGSEGV. SIGBUS almost always means unaligned access.
-
moneromooo
Pretty sure LMDB hits SIGBUS when reading data from "the LMDB database" but off the file extents, which happens on corrupt data.