Skip to content

server, log: Malformed log entries make /_status/logs return 500 #151493

@alyshanjahani-crl

Description

@alyshanjahani-crl

Describe the problem

When a node has logs that contain a panic, the logs API on the status server fails as the panic causes log.FetchEntriesFromFiles to return an ErrMalformedLogEntry.

To Reproduce

This occurs quite often during the db-console/mixed-version-endpoints roachtest. See #149866 (comment)

Expected behavior
A panic in a log file shouldn't cause the status server to fail to serve the logs.

Jira issue: CRDB-53311

Metadata

Metadata

Assignees

Labels

C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.T-observabilitybranch-masterFailures and bugs on the master branch.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions