-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
understanding spammy error log entries. #2023
Comments
Hello. You can set |
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 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???
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??? |
This message appears because of bug in i2pd. Developers know about it. |
Ok, then I assume so is this one |
Latest version, 2.50.2-107-ga1dce017, have this problem mostly fixed by the way.
These "errors" are data, which i2pd not expects to see. |
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.
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. |
I have the same log errors as well as low tunnel creation success, nice to know it's a bug. |
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:
02:00:02@297/error - NTCP2: Host mismatch between published address 220.240.226.XXX and actual endpoint 193.138.218.XXX
and02:00:47@297/error - NTCP2: Host mismatch between published address 2001:XXX:1:XXX and actual endpoint 2001:XXX:0:XXX
02:00:09@297/error - NTCP2: Wrong static key in SessionConfirmed
02:00:45@297/error - NTCP2: RouterInfo is from future for 2930 seconds
02:03:24@297/error - NTCP2: RouterInfo is too old in SessionConfirmed for 10243 seconds
02:00:03@807/error - Tunnel: Tunnel with id XXX already exists
02:02:30@889/error - RouterInfo: Can't open file /var/lib/i2pd/netDb/XXX/routerInfo-XXX.dat
(with two different paths so far)02:00:32@889/error - SSU2: RouterInfo in SessionConfirmed is from future for 56491 seconds
02:03:05@889/error - SSU2: RouterInfo in SessionConfirmed is too old for 7817 seconds
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:
The text was updated successfully, but these errors were encountered: