03:45:48 Hi guys, I'm trying to understand a few things about monerod and maybe someone could clarify a few details. 03:49:36 Can "monerod --data-dir" default be changed permanently? 03:51:55 I'm also getting this warning "W The blockchain is on a rotating drive: this will be very slow, use an SSD if possible ..." when I am using an SSD though a usb one. 04:15:42 ok.. maybe this isn't the right forum for these questions? 05:37:39 Guest55: Yeah, this is the channel for programming questions. You might try in #monero. 05:37:49 About changing the data dir permanently: If you want your blockchain in another place, just make sure you always start your daemon that way. No other mechanism to achieve any "permanence" really. 05:37:59 That warning about the slow HD: That's harmless, for some problem in the logic or in the response of the OS the daemon thinks you are using a slow HD while you are not, and warns. Also happens within virtual machines, for example. 05:54:38 He left 06:38:23 Hey, I am facing a lot of 'W Failed to create a read transaction for the db: MDB_READERS_FULL: Environment maxreaders limit reached' lately. This makes monerod totally unresponsive. I already start monerod with ' --max-concurrency 60' to no avail really. Are there any other options? 07:24:37 re: documentation. That's an issue. A lot of stuff is not documented. I added the main features in the download page on getmonero and in other places. I also open issues when i think we should document something on the website, but what's missing is people actually doing it. I would totally support a CCS for that 07:25:41 Please open an issue on monero-site if you think something should be documented but it's not 07:26:40 there is already a list of stuff that need to be added/updated: https://github.com/monero-project/monero-site/issues?q=is%3Aissue+is%3Aopen+label%3A%22%E2%9B%91%EF%B8%8F+contributor+needed%22 09:03:25 normo: Try restarting your system. Also max-concurrency 60? Why? I would not change max concurrency at all. 10:46:01 Yes, that's just shooting your self in the foot and wondering why it hurts. 10:46:53 You can bump the max readers at runtime IIRC if you really want that. git grep maxreaders or max_readers in src/blockchain/db_lmdb.cpp 13:18:14 luigi1111w: can you merge 6612 when you can ? It fixes the build with older boost. 13:49:52 selsta: I don't remember where this recommendation came from. I removed max-concurrency again. Still the original error remains. There only is the Monero onion explorer running sharing the same lmdb. This one seems to eat up the readers. 13:53:25 yes, you have to do as moneromooo suggested and increase the number of LMDB readers if you want this to work 13:53:53 monerod by default only allocates enough readers for its own threads, it doesn't know about any other processes also using the DB 13:54:12 the explorer eats up more readers itself, so you have to bump up the max 13:55:46 also afaik there's still a bug in the onion explorer that leaves dangling readers, so it tends to run out of them 13:59:53 I even wrote a python tool that reads the readers, but now that it only shows 0, I assume it's bound to the environemnt created in the tool itself instead of the lmdb in general. 14:03:48 an environment only exists as long as any processes have it open 14:04:07 if the tool has its own environment then that means no other processes were still alive on it before 14:05:09 those guys really need to chase down that reader leak and fix it... 14:30:09 I will go and increase the value in the source code then. Seems to be the only option if I want to keep the explorer. Thanks everybody. 15:17:15 hyc: I just read your comment again. So if I open an (lmdb) environment using the mainnet lmdb drectory (in my python lmdb app), I should see the actual number of readers? 15:19:40 yes 15:20:36 also, if there are no processes active, whoever access the DB first initializes the environment. so you can start your tool and set the readers to a larger number, before starting monerod & explorer 15:55:06 Ok, then I have an error in how I access the db. It says '0' readers and a call to 'reader_check()' returns '0' as well. I check that whenever the error occurs. 15:55:49 Thanks again for hint with regard to the order of processes started. 16:04:16 the environment is only there while processes have it open. 16:06:59 I thought, I could simply, open the environment and check the number of readers to help debugging and actually confirm the high number of readers. 16:07:14 yeah 16:13:56 if the environment is active, yes, you should be able to see the current count 16:14:05 use the mdb_stat CLI tool instead 16:14:39 sounds like whatever LMDB your python is linked with is the wrong version or something 16:15:15 you pretty much have to link to the one that's in the monero build tree 16:16:26 I basically just do: 'env = lmdb.open("/mnt/Monero/lmdb", subdir=True, lock=False, readonly=True, max_dbs=10)' and 'env.info()'. That's it. 16:16:47 Yes, I will try mdb_stat.