-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgraded to v3 on raspi and now no longer able to boot because of "out of memory" error #6947
Comments
You're hitting limits on the number of memory mappings per process, see urbit/vere#624. |
I had found that and tried it, @joemfb, but it didn't work. I'm wondering if the earlier error (boot: core limit: Invalid argument) is relevant? --joe
|
The core limit failure is from a But I just realized that you said "raspi", and this specific error is coming out the lmdb integration. We're trying to create a huge mapping for the lmdb event-log environment: 500 GB on linux-aarch64, 1 TB elsewhere. That limit is currently hardcoded. We should make it configurable from the command line, in the meantime, you could try lowering it (at the top of |
ah, ok, thanks! perhaps it's time to move my urbit elsewhere... |
I also tried your rlimit suggestion, but that didn't seem to resolve the other (unrelated) error message:
|
yep, this is exactly the same issue I am running into on a Raspi 5 (8GB). It has a 250GB disk on it, and the lmdb the lmdb version in liblmdb0/now 0.9.24-1 arm64 [installed,local]
and also
Would this imply, if I put a 1TB disk on it, it might boot? and thanks, ~mopfel-winrux, for your assistance. |
Any ideas about this problem? A next worked but then trying to run it ended with this "Out of memory" error on lmdb, as well as other errors, e.g., "boot: core limit: Invalid argument."
$ uname -a
Linux umbrel 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
$ sudo ./urbit tindus-milmus
~
urbit 3.0
boot: home is /mnt/data/urbit/tindus-milmus
disk: loaded epoch 0i65645879
boot: core limit: Invalid argument
loom: mapped 2048MB
boot: protected loom
live: mapped: MB/854.687.744
live: loaded: KB/16.384
loom: memoization migration running...
loom: memoization migration done
boot: installed 967 jets
boot: core limit: Invalid argument
loom: mapped 2048MB
lite: arvo formula 2a2274c9
lite: core 4bb376f0
lite: final state 4bb376f0
lmdb: failed to open event log: Out of memory
disk: failed to initialize lmdb
pier: stay: init fail
The text was updated successfully, but these errors were encountered: