Return more info in connection init errores #10
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zmstone
force-pushed
the
return-more-info-in-connection-init-errores
branch
from
99f829a to
3b22690
Compare
id
approved these changes
Oct 7, 2024
zmstone
force-pushed
the
return-more-info-in-connection-init-errores
branch
8 times, most recently
from
10af525 to
ecc2908
Compare
when in a system there are more than one set of MySQL database connections, looking at a e.g. 'timeout' log is not quite helpful to tell which exact config set went wrong
zmstone
force-pushed
the
return-more-info-in-connection-init-errores
branch
from
ecc2908 to
0953d99
Compare
zmstone
force-pushed
the
return-more-info-in-connection-init-errores
branch
from
6bf3b41 to
e204ec5
Compare
zmstone
force-pushed
the
return-more-info-in-connection-init-errores
branch
from
e204ec5 to
1ee4047
Compare
id
approved these changes
Oct 7, 2024
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When there are more than one set of MySQL configs, it's quite hard to tell which one is for which.
before:
timeoutafter:
#{cause => timeout,port => 3306,user => <<"root">>,host => "1.1.1.1",database => <<"test">>}e.g.
2024-10-07T07:12:52.857393+00:00 [error] crasher: initial call: mysql_conn:init/1, pid: <0.6494.0>, registered_name: [], exit: {#{cause => timeout,port => 3306,user => <<"root">>,host => "1.1.1.1",database => <<"test">>},[{gen_server,init_it,6,[{file,"gen_server.erl"},{line,961}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,241}]}]}, ancestors: [<0.6493.0>,<0.6492.0>,<0.6490.0>,ecpool_sup,<0.4205.0>], message_queue_len: 0, messages: [], links: [<0.6493.0>], dictionary: [], trap_exit: false, status: running, heap_size: 376, stack_size: 28, reductions: 286; neighbours: