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

I'm using monero-wallet-gui

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...

Is there a log level that logs why a peer is getting banned?

Someone on Reddit has a problem where the node suddenly starts to ban all peers and then disconnects from the network.

net.cn:INFO will *probably* show most, net.p2p:INFO some others.

That might not be all of them, but I think the vast majority.

Should they delete p2pstate.bin before testing?

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.

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?

Yes, --log-level "0,net.cn:INFO;net.p2p:INFO

ty

@selsta i had the same issue, i got it solved by rising this "#define ABSTRACT_SERVER_SEND_QUE_MAX_COUNT 10000" in epee

originaly was 1000

moneromooo: this is the log of the person whose peers get all banned paste.debian.net/1152098

is what italocoin wrote related to this?

Block verification failed, dropping connection

Add verify:INFO

(or even justERROR)

so --log-level "0,verify:ERROR" ?

If it's a valid block and it gets found as invalid, it's likely a corrupt chain.

Yes.

Might as well log-level 1

ok

In case other interesting things.

here is the post btw but not sure if there is anything else useful in there