selsta: there wasn't any more freezes in the meantime but found this related to the last one - 'segfault at 59 ip 000055a6c4010aaa sp 00007fff58563340 error 4 in monerod[55a6c3885000+10d3000]' i know it probably doesn't help but at least it could sched some light on type of the problem, maybe?

this was the v0.17.3.0 binary downloaded from getmonero.org?

this was with compiled from monero-linux-x64-0.17.3.0.tar.bz2

s/with//

compiled from?

yes binary, excuse me

ok

its 5 am

im a bit lost

np :D

i will wait for the next freeze but until then i would like to start another monerod 0.17.2.0 to use the same lmdb, is this possible?

i would like to start it to act as failover, as the services running are critical

running another daemon should work on the same lmdb

great, will go give it a try :) thanks for your time

thanks. just if anyone is interested, managed to get another monerod up with same lmdb its really straightforward just use the same data-dir as main monerod with different bind ports - monerod --data-dir /path/.bitmonero/ --rpc-bind-port 18091 --rpc-bind-ip=127.0.0.1 --restricted-rpc --p2p-bind-port 18090

interestingly, it is not allowed to run secondary monerod that uses the same lmdb as first node with 'exec' inside a docker entrypoint otherwise it will error out with 'Failed to create a read transaction for the db: Resource temporarily unavailable'. but running the first monerod will work with 'exec'

Why would you want to run two monerod on the same machine

Also, of course it blocks you: if it didn't, you'd have two programs trying to write to your blockchain file, which would corrupt it almost immediately

merope: monerod / lmdb supports two daemons with one blockchain file

the "local synchronization" mobile apps from getmonero.org/downloads will donload the whole 120GB keychain?

do the typical used keep that 120GB keychain on their hd?

*user

*blockchain

It's optional, but it gives you the highest level of security. You can use somebody else's node ("remote node") to sync your wallet, but they could log some of your data or mess with you in some ways

Note that there's also the --pruned-node option to occupy less storage space (~50GB)

merope: oh nice, didnt know about that pruned ... but also considering giving teens/young adults monero for christmas (ppl who prob never used crypto) ...

i guess the light wallets would be the best option

Then using a remote node is the easiest option

eoc: There's a few light wallets listed on the website

mhmhm

they still get their seed right?

Yes

cool

oh btw, mining with monerod ... are you likely to make ANY monero with a very basic mini computer?

and is it quite secure to run 24/7 on a personal computer?

Will you be using the personal computer for something else?

eoc: Depends on how powerful your CPU is

dEBRUYNE: yes, its the computer i use, but mostly for light stuff like browsing .. maybe a movie..

no gaming etc..

eoc: github.com/monero-project/monero/#socket-based

Resource wise it should be okay, as monerod does not use many resources once it is fully synced

dEBRUYNE: damn, thats a nice feature..

<Normsi> EN текст

does the pruning take long?

Exceedingly.

Don't prnue a fully grown db, you're better off resyncing.

moneromooo: with monerod --sync-pruned-blocks ?

Your question is missing a part. I can't answer it yet.

ah this recommends not pruning getmonero.org/resources/moneropedia/pruning.html

eoc: regarding solo-mining, it's not really worth it. You're most likely to not find anything at all for months/years, so you're just gonna be wasting the electricity

If you really want to mine a little bit, then you're better off mining on a mining pool (using xmrig) - but don't expect more than a few bucks worth of xmr per month unless you have a powerful cpu (like ryzen 3600/5600 or better)

(Note that intel cpus are slower and less efficient than their amd counterparts)

merope: thanks! sounds like not for me tbh (i even have intel haha)