-
Notifications
You must be signed in to change notification settings - Fork 497
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
use more log level than just trace #566
Comments
@sebas77 errors printed always into logger. Also breaking socket errors you will receive in |
thanks @RevenantX . If my current investigation will be successful, I will be clearer with my use case: |
@sebas77 you can add |
@sebas77 also such timeouts possibly can be because network jumps (wifi->lte). You need enable |
yes that's already done. Our current settings are: Client:
(note we are also using an UDPAuthKey) Server:
the client is on android mobile! I forgot to say: these timeouts happen ONLY at the connection time, it's like the server never replies back to the client, but the server acknowledged the new connection. |
this is an example of what happens with our logs:
|
I activated the DEBUG_MESSAGES, but apparently everything (or almost everything) is at trace level.
using more level would be nice, I was after only errors/breaking stuff
The text was updated successfully, but these errors were encountered: