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

Out of space no longer logged when a node runs out of space #67187

Open
RichardoC opened this issue Jul 2, 2021 · 8 comments
Open

Out of space no longer logged when a node runs out of space #67187

RichardoC opened this issue Jul 2, 2021 · 8 comments
Labels
A-logging In and around the logging infrastructure. A-observability-inf C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-community Originated from the community P-3 Issues/test failures with no fix SLA T-observability

Comments

@RichardoC
Copy link
Contributor

RichardoC commented Jul 2, 2021

Describe the problem

Since upgrading to docker image cockroachdb/cockroach:v21.1.3 from cockroachdb/cockroach:v20.2.1 cockroach will not log to stderr that it had run out of space before exiting upon a restart.

To Reproduce

Run cockroachdb/cockroach:v21.1.3 with entrypoint
cockroach start-single-node --store /storage/ --insecure --log="sinks: {stderr: {no-color: true, channels: [ALL]}, file-groups: {default: {channels: [All]}}}"
Where /storage/ points to a volume with no space left

See that nothing is logged to stderr

Expected behavior
Run cockroachdb/cockroach:v20.2.1 with entrypoint
cockroach start-single-node --store /storage/ --insecure
Where /storage/ points to a volume with no space left

Logs from cockroachdb/cockroach:v20.2.1

E210702 15:35:36.915758 1 util/log/exit_override.go:59 ⋮ logging error: write ‹/storage/logs/cockroach.database-service-559d8ccd44-9xsz7.unknownuser.2021-07-02T15_34_39Z.000001.log›: no space left on device

Environment:

  • CockroachDB version
    docker image cockroachdb/cockroach:v21.1.3
  • Server OS:
    Ubuntu 18.04
  • Client app [e.g. cockroach sql, JDBC, ...]
    N/A

Additional context
What was the impact?
Makes it more difficult to work out why a cockroach node won't start.

Jira issue: CRDB-8417

@RichardoC RichardoC added the C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. label Jul 2, 2021
@blathers-crl
Copy link

blathers-crl bot commented Jul 2, 2021

Hello, I am Blathers. I am here to help you get the issue triaged.

Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here.

I was unable to automatically find someone to ping.

If we have not gotten back to your issue within a few business days, you can try the following:

  • Join our community slack channel and ask on #cockroachdb.
  • Try find someone from here if you know they worked closely on the area and CC them.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@blathers-crl blathers-crl bot added O-community Originated from the community X-blathers-untriaged blathers was unable to find an owner labels Jul 2, 2021
@rafiss rafiss added this to To do in DB Server & Security via automation Jul 6, 2021
@blathers-crl blathers-crl bot added the T-server-and-security DB Server & Security label Jul 6, 2021
@rafiss rafiss added A-logging In and around the logging infrastructure. and removed X-blathers-untriaged blathers was unable to find an owner labels Jul 6, 2021
@rafiss
Copy link
Collaborator

rafiss commented Jul 9, 2021

Thanks for reporting this @RichardoC !

cc @knz for triaging

@knz knz moved this from To do to Linked issues (from the roadmap columns on the right) in DB Server & Security Jul 29, 2021
@RichardoC
Copy link
Contributor Author

Hi there, any updates?

@knz
Copy link
Contributor

knz commented Nov 29, 2021

Not yet, but thanks for the reminder.

@knz
Copy link
Contributor

knz commented Nov 29, 2021

cc @piyush-singh @jtsiros for prioritization

@jtsiros
Copy link

jtsiros commented Dec 8, 2021

Right now, we are targeting this for after the new year given the December milestone priorities. Please ping @mwang1026 if this becomes urgent.

@github-actions
Copy link

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

@knz knz removed this from Linked issues (from the roadmap columns on the right) in DB Server & Security Aug 28, 2023
@RichardoC
Copy link
Contributor Author

/remove-label stale

@exalate-issue-sync exalate-issue-sync bot added P-3 Issues/test failures with no fix SLA T-observability and removed T-observability-inf labels Mar 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-logging In and around the logging infrastructure. A-observability-inf C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-community Originated from the community P-3 Issues/test failures with no fix SLA T-observability
Projects
None yet
Development

No branches or pull requests

4 participants