Skip to content

This is the multi-page printable view of this section. .

Return to the regular view of this page.

Troubleshooting

Overview

MinIO users have two options for support.

  1. Community support from the public Slack channel.

    Community support is best-effort only and has no SLA or SLO.

  2. Paid subscribers have access to the MinIO Subscription Network, SUBNET, which provides access to health checks, direct-to-engineering support, and license management.

    For current licensing levels and pricing, refer to the MinIO SUBNET page.

Tools

The MinIO Client provides several functions to display information about your MinIO deployment or monitor its activity.

  • For basic information about your MinIO deployment, use mc admin info.
  • For deeper investigation of S3 calls and responses, use mc admin trace.
  • Use mc admin logs to display logs from the command line. The command supports type and quantity filters for further limiting logs output.

Upgrades and version support

MinIO regularly releases updates to introduce features, improve performance, address security concerns, or fix bugs. These releases can occur very frequently, and vary by product.

Always test software releases in a development environment before upgrading on a production deployment.

Recommended upgrade schedule

MinIO recommends always installing the most recent release to obtain security enhancements and improvements. We recognize that such a frequent release schedule may make this impractical for some organizations. In such cases, we recommend using MinIO and our related product releases that are no older than six months.

Version Alignment

As the various MinIO products release separately on their own schedules, we recommend the following version alignment practices:

MinIO

Update to the latest release or a release no older than six months.

MinIO Client

Update to the mc release that occurs immediately after the MinIO release, within one or two weeks.

MinIO Operator

Use a MinIO version no earlier than the latest at the time of the Operator release. The MinIO version latest at time of release can be found in the quay.io link in the example tenant kustomization yaml file for the Operator release.

  • 4.5.5: MinIO RELEASE.2022-12-07T00-56-37Z or later
  • 4.5.6: MinIO RELEASE.2023-01-02T09-40-09Z or later
  • 4.5.7: MinIO RELEASE.2023-01-12T02-06-16Z or later
  • 4.5.8: MinIO RELEASE.2023-01-12T02-06-16Z or later

When creating a new tenant, the Operator uses either the latest available MinIO release image or the image you specify when creating the tenant.

Upgrading the Operator does not automatically upgrade existing tenants. Upgrade existing tenant MinIO versions separately.

1 - Encrypting Files

Description

You can encrypt the output of the mc support inspect command for enhanced security when transmitting the files to MinIO SUBNET.

Encryption

You can choose to encrypt the output zip file for enhanced security with the --encrypt flag. MinIO provides a binary to decrypt the file.

When the encryption flag, the output provides a decryption key. The output resembles the following:

$ mc support inspect --encrypt play/test123/test*/*/part.*
mc: Encrypted file data successfully downloaded as inspect.ad2b43d8.enc
mc: Decryption key: ad2b43d847fdb14e54c5836200177f7158b3f745433525f5d23c0e0208e50c9948540b54

mc: The decryption key will ONLY be shown here. It cannot be recovered.
mc: The encrypted file can safely be shared without the decryption key.
mc: Even with the decryption key, data stored with encryption cannot be accessed.

As the output says, MinIO only displays the encryption key this one time, and it cannot be displayed or recovered later.

Decryption

MinIO provides a decryption tool to use on the files generated by mc support inspect.

To install the decryption tool, install Go, then run

go install github.com/minio/minio/docs/debugging/inspect@latest

After installing the inspect decryption binary, decrypt the file with the following command:

inspect -key=<decryptionKeyFromOutput> <file.enc>

Replace <decryptionKeyFromOutput> with the decryption key provided when generating the diagnosit file. Replace <file.enc> with the downloaded file name, including a relative or absolute path.

-key flag is optional. If not provided, an interactive prompt asks for the key. The file name includes a portion of the decryption key. This helps verify which key to use for the file.

The decryption process outputs an unencrypted .zip file.