Daemon crashed last night with only a warning about monero HOT 18 CLOSED

How long did you wait after launch?

The warning message you shared is likely unrelated to whatever freezing issue you had.

from monero.

It's been almost 20 mins and the console has done nothing else other than warn me my blockchain is on an HDD (I know, bad practice), resource usage shows that it hasn't even tried to read the disk as far as I can really tell

from monero.

The disk still works, I have media on there I can still stream just fine, its not an IO issue either as this machine has nothing else running at the moment

from monero.

It's doing 400kb/s read but that's far slower than anything I've seen it do

from monero.

It verifies the whole txpool on launch, which can take a while in some cases. Is there CPU usage?

Can you launch monerod with --log-level 2 and share the last couple messages?

from monero.

OK it is verifying transactions. spamming the console with a lot of:

2024-05-02 16:36:42.734 I Transaction added to pool: txid <dd3fb300aa6ad4095319e1ce59b90b08c38a63ef4cd10cdefe9a2bc324e7fc3e> weight: 101187 fee/byte: 80000, count: 338
2024-05-02 16:36:42.773 D Removing tx <0f19390354b694ee7774356757f2b0f85f5af1ab838b07b141812290172a323f> from tx pool, but it was not found in the map of added txs
2024-05-02 16:36:42.773 D Transaction removed from pool: txid <0f19390354b694ee7774356757f2b0f85f5af1ab838b07b141812290172a323f>, total entries in removed list now 339
2024-05-02 16:36:42.773 D Using 0.000000019000/byte fee
2024-05-02 16:36:42.773 D Mixin: 15-15

from monero.

Its using 250% CPU according to top so it is actually doing stuff

from monero.

im gonna just let it do its thing for a few hours and see if it fixes itself, sorry to cause alarm. It appeared to be idle but that clearly is not the case. Patience it is :D thanks for your help

from monero.

So I also mistitled it, I checked the log and it did close the daemon, not freeze. I also have ZMQ enabled for p2pool mining, I saw it mentioned here #8897, could it be related?

from monero.

How much RAM does your machine have? Did it get killed for OOM or crash?

from monero.

16GB of RAM, wasn't anywhere close to full. My virtual memory was at 91% though since its only a gig, but it had been at 80%+ since I started mining so not sure

from monero.

OK it was able to resync properly. I guess ill wait to see if it crashes again and try to get you more info if I can

from monero.

It's still not clear to me if it ran out of memory, or if it crashed. I have seen RAM usage spikes on my node in some specific situations that caused my node to OOM.

from monero.

Just checked one of my nodes, around the same time one of my nodes also ran out of memory. What you are reporting is not a crash, though it would be nice if someone could investigate what casues this RAM spike.

from monero.

Just checked one of my nodes, around the same time one of my nodes also ran out of memory. What you are reporting is not a crash, though it would be nice if someone could investigate what casues this RAM spike.

That is very odd indeed. No other processes were affected. I was running p2pool and xmrig on the server as well, if that is relevant. None of those crashed but were upset about the daemon dying

from monero.

Let's continue here #9315

from monero.

The issue you linked is this one

from monero.

#9317

from monero.