Skip to content
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

Captive core logs are missing information and have the wrong log level #3692

Closed
MonsieurNicolas opened this issue Jun 15, 2021 · 0 comments · Fixed by #3746
Closed

Captive core logs are missing information and have the wrong log level #3692

MonsieurNicolas opened this issue Jun 15, 2021 · 0 comments · Fixed by #3746

Comments

@MonsieurNicolas
Copy link
Contributor

What version are you using?

Horizon 2.5

What did you do?

Start captive core in debug level.

What did you expect to see?

Log lines with information on subsystem and log level.

What did you see instead?

Log lines all claim to be INFO level and core's subsystem is missing (truncated).

compare one of the DEBUG Overlay log lines for example (raw core logs first, captive-core logs per Horizon):

2021-06-15T07:49:03.625 GA2QO [Overlay DEBUG] TCPPeer::startRead 800 from 3.83.213.217:11625
-------------------------
INFO[2021-06-15T16:06:20.901+02:00] TCPPeer::startRead 728 from 54.211.227.163:11625  pid=63159 service=ingest subservice=stellar-core

note the missing DEBUG and Overlay anywhere - this makes debugging very hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants