-
gingeropolous
lza_menace, this will grep all the logfiles for that string, and then identify and count the IPs :grep ERROR bitmonero.log* | grep "Error state" | cut -f 6 | cut -f 1 -d " " | cut -f 1 -d ":" | sort | uniq -c
-
gingeropolous
unnecessary double grep but whatevs
-
lza_menace
i wont tell anyone
-
plowsof
im going to tell chatgpt brb
-
selsta
I still think banning nodes permantly without first figuring out what causes this error state is a bad idea.
-
selsta
(assuming you ban them permanently, I didn't check the repo)
-
selsta
it's possible that this is a bug in monerod and not necessarily a malicious node
-
plowsof
ginger has a bantime of 3600 seconds set (i dont notice any spam / resource usage myself)
-
lza_menace
i am going to try it to see if it cuts down on my bandwidth usage
-
lza_menace
i get emails every month that im getting throttled by my provider
-
lza_menace
(OVH)
-
selsta
3600 should be fine for nodes that cause a lot of errors, yes
-
Mochi101
man
-
Mochi101
@price zeph
-
Mochi101
oops
-
Mochi101
:D
-
lza_menace
gingeropolous: which log level?
-
gingeropolous
i run log-level=1
-
gingeropolous
hrm, another contender. grep "Failed to send message" bitmonero.log* | cut -f 6 | cut -f 1 -d "]" | sort | uniq -c | sort -n
-
gingeropolous
and the genesis mismatch one
-
gingeropolous
grep -C 5 "Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block mismatch" bitmonero.log* | grep calling | cut -f 6 | cut -f 1 -d "]" | sort | uniq -c | sort -n
-
gingeropolous
thats gonna be not as straightforward because the IP address is on a different log line than the error
-
gingeropolous
but I got one that has 1041 instances of that
-
gingeropolous
oh there's already a a built in block for that
-
gingeropolous
though its apparently not effective
-
gingeropolous
i guess we need a recidiv equivalent
-
gingeropolous
all about lowering that CONOP baby
-
lza_menace
im running it
-
lza_menace
no blocks ye
-
lza_menace
t
-
m-relay
<crabwalk:matrix.org> Hello roomies. I have some issues with my wallet. Is this a good place to ask questions?
-
m-relay
<crabwalk:matrix.org> Couldn't connect to daemon: 127.0.0.1:18081
-
m-relay
<crabwalk:matrix.org> Do I need to set port forwarding rule to resolve this? If I open port with my internal IP having public port range 18081 should I set my private port range to 18080? If I do open those ports, will it put my computer or LAN at risk by doing so, or is is isolated to the monero program?
-
m-relay
<lza_menace:monero.social> port forwarding not needed. do you have monerod running? you run monerod and the wallet at the same time
-
m-relay
<crabwalk:matrix.org> I'm not sure. Mac OS (I know, I know). I'm using the monero wallet gui with local node chosen. It synced the blochchain, but not the wallet. I had a functioning version previously but deleted it, and trying to restart now with seedphrase. I was surprised to see that a key file was also needed, so hopefully creating a new key file with the seedphrase will work to restore the funds <clipped message>
-
m-relay
<crabwalk:matrix.org> and get the wallet working again. Thanks for the reply. I won't waste time in the router.
-
selsta
crabwalk: do you have any other issues apart from the "Couldn't connect to daemon" message?
-
selsta
this message can show up when the wallet tries to connect to the node before it was started
-
selsta
usually in the next try a couple seconds later it connects successfully
-
selsta
so it's harmless unless you have other issues
-
m-relay
-
m-relay
<pirm:matrix.org> Feriado
-
m-relay
<c0w:matrix.org> nossa as salsichas foram assassinadas !
-
m-relay
<c0w:matrix.org> nossa as linguicas foram assassinadas !
-
m-relay
<crabwalk:matrix.org> In the log it looks like the only issue. But no matter how long I wait, the wallet progress bar does not move and the wallet never loads
-
m-relay
<crabwalk:matrix.org> [2023-11-15 12:44 PM] 2023-11-15 20:44:35.409 I Monero 'Fluorine Fermi' (v0.18.3.1-release)
-
m-relay
<crabwalk:matrix.org> Error: Couldn't connect to daemon: 127.0.0.1:18081
-
m-relay
<crabwalk:matrix.org> [2023-11-15 12:44 PM] 2023-11-15 20:44:49.326 I Monero 'Fluorine Fermi' (v0.18.3.1-release)
-
m-relay
<crabwalk:matrix.org> Height: 3018800, target: 3018861 (99.998%)
-
m-relay
<crabwalk:matrix.org> Downloading at 73 kB/s
-
m-relay
<crabwalk:matrix.org> 2 peers
-
m-relay
<crabwalk:matrix.org> Remote Host Peer_ID State Prune_Seed Height DL kB/s, Queued Blocks / MB
-
m-relay
<crabwalk:matrix.org> 82.69.12.29:18080 0000000000000000 before_handshake 0 0 1 kB/s, 0 blocks / 0 MB queued
-
m-relay
<crabwalk:matrix.org> 66.190.134.158:18080 2f918635b777d257 synchronizing 0 3018861 72 kB/s, 20 blocks / 0 MB queued
-
m-relay
<crabwalk:matrix.org> 1 spans, 0 MB
-
m-relay
<crabwalk:matrix.org> [.]
-
m-relay
<crabwalk:matrix.org> 66.190.134.158:18080 20/181 (3018800 - 3018819) -
-
selsta
are you fully synced up?
-
selsta
your daemon says 99% and not 100%
-
selsta
before that the wallet won't sync
-
m-relay
<crabwalk:matrix.org> Ive let it sit for a couple days with no change. Reinstalled and same thing repeats. It looks like nothing is happening.
-
m-relay
<crabwalk:matrix.org> I left it since I posted the log message earlier, and it looks the same now
-
m-relay