Project

General

Profile

Actions

Idea #21424

open

Way to run a diagnostic container that captures all system logs, not just Crunch's

Added by Brett Smith 8 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
Start date:
Due date:
Story points:
-

Description

Use case: you have a compute node image that's misbehaving because it's misconfigured. It would help to be able to run a job that registers/passes through all the system logs for review.

This could be as simple as running journalctl --follow --boot=0 --lines=all and streaming the output somewhere. Maybe capture a few key log files under /var/log too for common system facilities that commonly don't log to syslog, like /var/log/dpkg.log.

Since this needs to run outside the container, I'm guessing it needs to be implemented in crunch-run directly?

Some problems are post-boot (like #20748), so it would help to be able to have the container run for an arbitrary time while in this mode. e.g., run the busybox image with sleep 15min or something.

Need to consider the security implications of this. Maybe only let admins run containers in this mode?


Related issues

Related to Arvados - Idea #21581: Crunch saves compute node journals to collections readable only by administratorsNewActions
Actions #1

Updated by Brett Smith 7 months ago

  • Related to Idea #21581: Crunch saves compute node journals to collections readable only by administrators added
Actions

Also available in: Atom PDF