Project

General

Profile

Feature #771

Logs need to persist across reboots

Added by Anonymous over 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
No priority
Assignee:
-
Category:
Middleware
Target version:
-
Estimated time:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:

Description

Today there's no visibility if a user goes and reboots the box where we can trace back what happened to get the user into a potentially failed state.

/var/log should be a file backed memory disk (not a ram disk like it is today) that's synced periodically to a persistent store to ensure that we have traceability to determine cause of failure in user issues across reboots.

History

#1 Updated by Xin Li over 7 years ago

/var/log is persist if user choose to configure it as such. The problem - it's not supported to have /var on a ZFS so the user has to use a dedicated disk for that.

By the way I think periodically flushing logs is not likely to catch much useful errors because the most useful logs are most likely be generated when the system is in extreme condition where flush scripts is not likely to be even ran.

#2 Updated by Jordan Hubbard about 5 years ago

  • Status changed from Unscreened to Closed

Now resolved by .system dataset.

Also available in: Atom PDF