Skip to content
cPFenceDocs

Restore missing Owl chart data

  1. Open System Dashboard and check the SERVER, METRIC, RANGE and observation time.
  2. Choose Update now for the chart or Refresh now for the Dashboard.
  3. On the intended server, check Owl monitoring and Owl history in System Settings.
  4. For missing secondary-server data, inspect its connection and follow secondary server connection troubleshooting.
  5. Check current status and module output before using the reviewed Owl restart control.

Dashboard performance chart with Local server selection, metric, range and NOW, AVG and MAX measurements.

Check chart scope and freshness before treating missing data as a collection problem. Select the image to enlarge it; use your browser's Back command to return.

Owl monitoring and Owl history switches in General Settings on Local server scope.

Check both Owl monitoring and Owl history on the server whose data is missing. Select the image to enlarge it; use your browser's Back command to return.

After correcting the connection or collection setting, refresh and allow a few minutes for new observations. If the WebUI itself still needs a restart, a root administrator can run cpfence --restart-webui on the main control panel server, then reopen the page.

Missing data is not zero usage. Turning history off stops new collection while retaining old history. Current telemetry uses the verified cPFence server connection; adding passwordless SSH is not a chart-connectivity repair.

Manage Owl History Logging with Enable Owl History Logging, Disable Owl History Logging and Back controls.

Advanced Settings offers separate history-collection controls. Check the server targets above the menu before changing collection. Select the image to enlarge it; use your browser's Back command to return.