00:11:41 <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
00:12:15 <gingeropolous> unnecessary double grep but whatevs
00:16:14 <lza_menace> i wont tell anyone
00:17:16 <plowsof> im going to tell chatgpt brb 
00:59:57 <selsta> I still think banning nodes permantly without first figuring out what causes this error state is a bad idea.
01:00:13 <selsta> (assuming you ban them permanently, I didn't check the repo)
01:00:35 <selsta> it's possible that this is a bug in monerod and not necessarily a malicious node
01:05:44 <plowsof> ginger has a bantime of 3600 seconds set (i dont notice any spam / resource usage myself)
01:18:45 <lza_menace> i am going to try it to see if it cuts down on my bandwidth usage
01:18:56 <lza_menace> i get emails every month that im getting throttled by my provider
01:19:01 <lza_menace> (OVH)
01:21:00 <selsta> 3600 should be fine for nodes that cause a lot of errors, yes
02:57:46 <Mochi101> man
02:57:52 <Mochi101> @price zeph
02:57:57 <Mochi101> oops
02:57:59 <Mochi101> :D
03:00:17 <lza_menace> gingeropolous: which log level?
03:00:47 <gingeropolous> i run log-level=1
03:14:50 <gingeropolous> hrm, another contender. grep "Failed to send message" bitmonero.log* | cut -f 6 | cut -f 1 -d "]" | sort | uniq -c | sort -n
03:18:47 <gingeropolous> and the genesis mismatch one
03:18:48 <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
03:19:11 <gingeropolous> thats gonna be not as straightforward because the IP address is on a different log line than the error
03:19:27 <gingeropolous> but I got one that has 1041 instances of that
03:21:55 <gingeropolous> oh there's already a a built in block for that
03:22:17 <gingeropolous> though its apparently not effective
03:23:43 <gingeropolous> i guess we need a recidiv equivalent
03:26:35 <gingeropolous> all about lowering that CONOP baby
03:37:54 <lza_menace> im running it
03:37:57 <lza_menace> no blocks ye
03:37:59 <lza_menace> t
05:34:27 <m-relay> <c​rabwalk:matrix.org> Hello roomies. I have some issues with my wallet. Is this a good place to ask questions?
05:49:28 <m-relay> <c​rabwalk:matrix.org> Couldn't connect to daemon: 127.0.0.1:18081
05:49:28 <m-relay> <c​rabwalk: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?
06:42:12 <m-relay> <l​za_menace:monero.social> port forwarding not needed. do you have monerod running? you run monerod and the wallet at the same time
18:40:19 <m-relay> <c​rabwalk: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>
18:40:19 <m-relay> <c​rabwalk:matrix.org> and get the wallet working again. Thanks for the reply. I won't waste time in the router.
19:03:06 <selsta> crabwalk: do you have any other issues apart from the "Couldn't connect to daemon" message?
19:03:38 <selsta> this message can show up when the wallet tries to connect to the node before it was started
19:03:53 <selsta> usually in the next try a couple seconds later it connects successfully
19:04:02 <selsta> so it's harmless unless you have other issues
19:31:24 <m-relay> <p​irm:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/WYhwtLYhcJPbEkliHYHJUzSK
19:31:32 <m-relay> <p​irm:matrix.org> Feriado
19:33:40 <m-relay> <c​0w:matrix.org> nossa as salsichas foram assassinadas !
19:34:04 <m-relay> <c​0w:matrix.org> nossa as linguicas foram assassinadas !
20:42:56 <m-relay> <c​rabwalk: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
20:52:06 <m-relay> <c​rabwalk:matrix.org> [2023-11-15 12:44 PM] 2023-11-15 20:44:35.409 I Monero 'Fluorine Fermi' (v0.18.3.1-release)
20:52:06 <m-relay> <c​rabwalk:matrix.org> Error: Couldn't connect to daemon: 127.0.0.1:18081
20:52:07 <m-relay> <c​rabwalk:matrix.org> [2023-11-15 12:44 PM] 2023-11-15 20:44:49.326 I Monero 'Fluorine Fermi' (v0.18.3.1-release)
20:52:07 <m-relay> <c​rabwalk:matrix.org> Height: 3018800, target: 3018861 (99.998%)
20:52:08 <m-relay> <c​rabwalk:matrix.org> Downloading at 73 kB/s
20:52:08 <m-relay> <c​rabwalk:matrix.org> 2 peers
20:52:09 <m-relay> <c​rabwalk:matrix.org> Remote Host Peer_ID State Prune_Seed Height DL kB/s, Queued Blocks / MB
20:52:09 <m-relay> <c​rabwalk:matrix.org> 82.69.12.29:18080 0000000000000000 before_handshake 0 0 1 kB/s, 0 blocks / 0 MB queued
20:52:10 <m-relay> <c​rabwalk:matrix.org> 66.190.134.158:18080 2f918635b777d257 synchronizing 0 3018861 72 kB/s, 20 blocks / 0 MB queued
20:52:10 <m-relay> <c​rabwalk:matrix.org> 1 spans, 0 MB
20:52:11 <m-relay> <c​rabwalk:matrix.org> [.]
20:52:11 <m-relay> <c​rabwalk:matrix.org> 66.190.134.158:18080 20/181 (3018800 - 3018819) -
21:25:55 <selsta> are you fully synced up?
21:26:08 <selsta> your daemon says 99% and not 100%
21:26:28 <selsta> before that the wallet won't sync
23:39:58 <m-relay> <c​rabwalk:matrix.org> Ive let it sit for a couple days with no change. Reinstalled and same thing repeats. It looks like nothing is happening.
23:41:18 <m-relay> <c​rabwalk:matrix.org> I left it since I posted the log message earlier, and it looks the same now
23:43:38 <m-relay> <c​rabwalk:matrix.org> https://matrix.monero.social/_matrix/media/v1/download/matrix.org/RHbUdhFMjiXBAoJPhDkMUyOW