# Swift Ops Runbook

This document contains operational procedures that Hewlett Packard Enterprise (HPE) uses to operate and monitor the Swift system within the HPE Helion Public Cloud. This document is an excerpt of a larger product-specific handbook. As such, the material may appear incomplete. The suggestions and recommendations made in this document are for our particular environment, and may not be suitable for your environment or situation. We make no representations concerning the accuracy, adequacy, completeness or suitability of the information, suggestions or recommendations. This document are provided for reference only. We are not responsible for your use of any information, suggestions or recommendations contained herein.

- Identifying issues and resolutions
  - Is the system up?
  - Functional tests usage
  - External monitoring
  - Diagnose: General approach
  - Diagnose: Swift-dispersion-report
  - Diagnose: Is system responding to `/healthcheck`?
  - Diagnose: Interpreting messages in `/var/log/swift/` files
  - Diagnose: Parted reports the backup GPT table is corrupt
  - Diagnose: Drives diagnostic reports a FS label is not acceptable
  - Diagnose: Failed LUNs
  - Diagnose: Slow disk devices
  - Diagnose: Slow network link - Measuring network performance
  - Diagnose: Remapping sectors experiencing UREs
  - Diagnose: High system latency
  - Diagnose: Interface reports errors
  - Diagnose: Hung swift object replicator
  - Diagnose: High CPU load
  - Further issues and resolutions
- Software configuration procedures
  - Fix broken GPT table (broken disk partition)
  - Procedure: Fix broken XFS filesystem
  - Procedure: Checking if an account is okay
  - Procedure: Getting swift account stats
  - Procedure: Revive a deleted account
  - Procedure: Temporarily stop load balancers from directing traffic to a proxy server
  - Procedure: Ad-Hoc disk performance test
- Server maintenance
  - General assumptions
  - Assessing the health of swift
  - Recon examples
  - Assessing the availability risk when multiple storage servers are down
  - Swift startup/shutdown
- Troubleshooting tips
  - Diagnose: Customer complains they receive a HTTP status 500 when trying to browse containers
  - Procedure: Deleting objects
  - Procedure: Decommissioning swift nodes

this page last updated: 2025-11-03 12:55:44

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.

found an error? report a bug