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.

Sign up for GitHub

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

Jump to bottom

roachtest: backup/KMS/AWS/n3cpu4 failed #113975

Closed
cockroach-teamcity opened this issue Nov 7, 2023 · 1 comment
Closed

roachtest: backup/KMS/AWS/n3cpu4 failed #113975

cockroach-teamcity opened this issue Nov 7, 2023 · 1 comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery
Milestone
24.1

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Nov 7, 2023 •
edited by cockroach-jira-scripts
Loading

roachtest.backup/KMS/AWS/n3cpu4 failed with artifacts on master @ ab484139e39c570edcd3f9df5ac09c84cdf74fee:

(monitor.go:153).Wait: monitor failure: dial tcp 3.145.78.61:26257: connect: connection refused
test artifacts and logs in: /artifacts/backup/KMS/AWS/n3cpu4/run_1

Parameters: ROACHTEST_arch=amd64 , ROACHTEST_cloud=aws , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_fs=ext4 , ROACHTEST_localSSD=true , ROACHTEST_metamorphicBuild=true , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

Grafana is not yet available for aws clusters

/cc @cockroachdb/disaster-recovery

This test on roachdash | Improve this report!

Jira issue: CRDB-33280
@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery labels Nov 7, 2023
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Nov 7, 2023
@msbutler
Copy link
Collaborator

msbutler commented Nov 7, 2023 •
edited
Loading

Duplicate of #113816. The oomkiller got node 1 good:

❯ grep "kill" *.dmesg.txt
1.dmesg.txt:[Tue Nov  7 20:36:02 2023] cockroach invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
1.dmesg.txt:[Tue Nov  7 20:36:02 2023]  oom_kill_process+0x10c/0x1b0
1.dmesg.txt:[Tue Nov  7 20:36:02 2023] oom-kill:constraint=CONSTRAINT_MEMCG,nodemask=(null),cpuset=cockroach-system.service,mems_allowed=0,oom_memcg=/system.slice/cockroach-system.service,task_memcg=/system.slice/cockroach-system.service,task=cockroach,pid=3864,uid=1000
image

@msbutler msbutler closed this as completed Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-disaster-recovery
Projects
No open projects
Disaster Recovery Backlog
Archived in project
Milestone
24.1
Development

No branches or pull requests
2 participants
@cockroach-teamcity @msbutler