Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Telemetry breaks when running with custom log levels #8093

Closed
bkchr opened this issue Feb 9, 2021 · 0 comments · Fixed by #8097
Closed

Telemetry breaks when running with custom log levels #8093

bkchr opened this issue Feb 9, 2021 · 0 comments · Fixed by #8097
Assignees
@cecton
Labels
I3-bug The node fails to follow expected behavior.

Comments

@bkchr
Copy link
Member

bkchr commented Feb 9, 2021

When running a node with -lwarn it prints the following at startup and looks like it is stuck:

2021-02-09 17:41:36  Could not initialize telemetry: the span could not be entered    
2021-02-09 17:41:36  Received connection notifier for unknown node (/dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F). This is a bug.
@bkchr bkchr added the I3-bug The node fails to follow expected behavior. label Feb 9, 2021
This was referenced Feb 10, 2021
Closed
Merged
@ghost ghost closed this as completed in #8097 Feb 10, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cecton cecton

Labels
I3-bug The node fails to follow expected behavior.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use log level error to report telemetry paritytech/substrate
2 participants
@cecton @bkchr