understanding spammy error log entries.

[agowa]

Hi, is there something I can do about these recurring and spammy error log entries? If this is not just some configuration issue on my part I'd like to suggest downgrading these to either debug or info.

I see countless occurrences of these in the logs:

1. 02:00:02@297/error - NTCP2: Host mismatch between published address 220.240.226.XXX and actual endpoint 193.138.218.XXX and 02:00:47@297/error - NTCP2: Host mismatch between published address 2001:XXX:1:XXX and actual endpoint 2001:XXX:0:XXX
2. 02:00:09@297/error - NTCP2: Wrong static key in SessionConfirmed
3. 02:00:45@297/error - NTCP2: RouterInfo is from future for 2930 seconds
4. 02:03:24@297/error - NTCP2: RouterInfo is too old in SessionConfirmed for 10243 seconds
5. 02:00:03@807/error - Tunnel: Tunnel with id XXX already exists
6. 02:02:30@889/error - RouterInfo: Can't open file /var/lib/i2pd/netDb/XXX/routerInfo-XXX.dat (with two different paths so far)
7. 02:00:32@889/error - SSU2: RouterInfo in SessionConfirmed is from future for 56491 seconds
8. 02:03:05@889/error - SSU2: RouterInfo in SessionConfirmed is too old for 7817 seconds
9. 02:02:41@375/error - Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message

OS: Alpine Linux Arch: x86_64 i2pd package version: 2.50.2-r0 openssl package version: 3.1.4-r5

Date and time are correctly synced and set to UTC.

The web interface shows everything as normal but with a low tunnel creation success rate:

Network status: OK
Network status v6: OK
Tunnel creation success rate: 10%

[Vort]

Hi, is there something I can do about these recurring and spammy error log entries?

Hello. You can set loglevel = critical.

[agowa]

Ok, but could you also please explain the above errors? I still don't know if they're errors that I can do something about or not. My goal is to only log errors that are (somewhat) "actionable" for me. Is loglevel = critical exactly that?

Assuming yes, what's with e.g. this one. It's not "critical" but only "error", so is it not something going wrong on my side???

02:02:30@889/error - RouterInfo: Can't open file /var/lib/i2pd/netDb/XXX/routerInfo-XXX.dat

In general i2pd should be able to write into that directory and create that file (as it did for all of the others in there). But somehow it didn't for these??? When I filter for unique files it couldn't open there I now get not only 2 but 300 unique ones.

[Vort]

Assuming yes, what's with e.g. this one. It's not "critical" but only "error", so is it not something going wrong on my side???

This message appears because of bug in i2pd. Developers know about it.

[agowa]

Ok, then I assume so is this one Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message too and all the other ones I listed above are "i2p network errors" (invalid data received from other nodes), right?

[Vort]

Ok, then I assume so is this one Garlic: Can't handle ECIES-X25519-AEAD-Ratchet message too

Latest version, 2.50.2-107-ga1dce017, have this problem mostly fixed by the way.

and all the other ones I listed above are "i2p network errors" (invalid data received from other nodes), right?

These "errors" are data, which i2pd not expects to see. Either because someone sent something wrong or because of bugs in i2pd.

[agowa]

Thanks. Then the only thing remaining is a wish to have these (and ideally all possible) log entries documented somewhere so that one can easily look them up. If there is already a work item for it then this ticket can be closed now.

Either because someone sent something wrong or because of bugs in i2pd.

Is this all that the "error" level is? I'd have expected such things to be at debug (at most info) tbh. But as long as anything else that is "an actual error" on my side is in critical I'd also leave it with a wish for a small note in the docs about what information each level is for.

[datawizard93]

I have the same log errors as well as low tunnel creation success, nice to know it's a bug.