-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Exception: boost::wrapexcept<boost::bad_weak_ptr> and std::runtime_error #6473
Comments
They're known, the former is normal randomx noisy init probing, the second is fixed on github. |
I've got the same issue where Is this something that needs to be fixed in the monero project or in the librandomx project and thus has to be reported there?
|
It looks like RandomX is trying to allocate using large pages and that's failing. Anyway, you can make librandomx stop trying to use large pages by setting the environment variable MONERO_RANDOMX_UMASK=1 when running monerod. I see, librandomx actually does throw exceptions on allocation errors. That's rude. |
Thanks for having a look. Unfortunately the MONERO_RANDOMX_UMASK environment variable did not help as a work-around. Besides it flooding the log it also appears to be linked to a drastic decrease in sync time. |
Most likely because that's where it starts verifying PoW. |
Same issue with https://github.com/XMRto/monero repo on kubernetes, MONERO_RANDOMX_UMASK did not help |
The crash related to sudo sysctl -w vm.nr_hugepages=1280 and the other error seems to be fixed as well. |
I have encountered this issue. I don't think this issue is fixed if it requires such a workaround as
|
It is not fixed even in 0.17.3.0, at least for FreeBSD. I have huge pages and mlock enabled for users, but still get a lot of
from monerod. |
Enabling 1.5GB of locked memory for process (which is, I believe, analogous to Linux's |
I keep getting these as well
package is https://build.opensuse.org/package/show/openSUSE%3AFactory/monero |
continuing in #8341 |
Same issue here. I am using monero in a docker container. It worked for years. I am now many blocks late, so my instance starts synching. But after a while it stops. Mostly when these statements kick in:
And sooner or later I always find:
|
@godfuture so does it not sync up at all anymore? or does it sync up and at some point fall behind again? |
@selsta It does not sync up at all anymore. Well, in the beginning it syncs, but stops over time. I have done mem tests, reduced CPU clocks, increased hugepages...I dont know what to do anymore. It worked for long time. Now I saw the first time: |
Did you try resyncing from scratch? |
Yes, which in fact increased the frustration :-( |
@godfuture I need more info. Where did it get stuck first and where did it get stuck after the complete resync from scratch with deleted blockchain? |
Has anyone seen the following error/s in logs again and again?
Not sure if they are related but I started to see these errors after my blockchain got corrupted, I did sync using the same machine/monero daemon version on a different SSD disk then copied the "data.mdb" and "lock.mdb" over to data dir.
Everything seems to work fine so far but I am worried about log pollution.
My system:
OS: Arch Linux x86_64 Host: 81LF Lenovo Legion Y7000P-1060 Kernel: 5.6.7-arch1-1 CPU: Intel i7-8750H (12) @ 4.100GHz Monero 'Carbon Chamaeleon' (v0.15.0.5-release)
The text was updated successfully, but these errors were encountered: