11:14:25 I can connect with .onion remote node and synchronize the wallet, but I cannot interact with this node. I always get the message: Error: Couldn't connect to daemon: 127.0.0.1:18081 11:14:49 I'm using monero-wallet-gui 12:04:05 Can I somehow limit the ram usage of monerod. I know that lmdb should free up space when other processes need it, but I m having a weird bug on my pool where im getting errors after few days of running it... 12:52:46 Is there a log level that logs why a peer is getting banned? 12:55:43 Someone on Reddit has a problem where the node suddenly starts to ban all peers and then disconnects from the network. 12:56:02 net.cn:INFO will *probably* show most, net.p2p:INFO some others. 12:56:15 That might not be all of them, but I think the vast majority. 12:56:54 Should they delete p2pstate.bin before testing? 12:58:05 I dunno. Depends what you want to test exactly. If it's just "why is it doing this now", then no. If you want to fix the problem, it might help. 12:58:50 ok, last question, if I do `--log-level "net.cn:INFO;net.p2p:INFO"` is there a way to also add the default log level? 12:59:26 Yes, --log-level "0,net.cn:INFO;net.p2p:INFO 13:01:10 ty 19:34:49 @selsta i had the same issue, i got it solved by rising this "#define ABSTRACT_SERVER_SEND_QUE_MAX_COUNT 10000" in epee 19:35:17 originaly was 1000 23:07:57 moneromooo: this is the log of the person whose peers get all banned https://paste.debian.net/1152098/ 23:08:08 is what italocoin wrote related to this? 23:14:08 Block verification failed, dropping connection 23:14:14 Add verify:INFO 23:14:20 (or even justERROR) 23:14:42 so --log-level "0,verify:ERROR" ? 23:14:48 If it's a valid block and it gets found as invalid, it's likely a corrupt chain. 23:14:51 Yes. 23:15:03 Might as well log-level 1 23:15:11 ok 23:15:11 In case other interesting things. 23:17:13 https://old.reddit.com/r/monerosupport/comments/h8pzfk/monerod_synchronization_stuck/ 23:17:24 here is the post btw but not sure if there is anything else useful in there