minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-07-31 18:04:52 +03:00
Code Activity

Replace mc admin console references with mc admin logs (#1198)

Browse Source 
mc admin console command is depreciated, users should start using mc
admin logs instead.
This commit is contained in:
Furkan Sahin
2024-05-06 20:31:40 +02:00
committed by GitHub
parent 7be620fd13
commit 24d445c35a
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
source/operations/data-recovery/recover-after-drive-failure.rst
View File

@ -111,7 +111,7 @@ The command should result in remounting of all of the replaced drives.
5) Monitor MinIO for Drive Detection and Healing Status 5) Monitor MinIO for Drive Detection and Healing Status
------------------------------------------------------- -------------------------------------------------------
Use :mc:`mc admin console` command *or* ``journalctl -u minio`` for Use :mc:`mc admin logs` command *or* ``journalctl -u minio`` for
``systemd``-managed installations to monitor the server log output after ``systemd``-managed installations to monitor the server log output after
remounting drives. The output should include messages identifying each formatted remounting drives. The output should include messages identifying each formatted
and empty drive. and empty drive.

4
source/operations/data-recovery/recover-after-node-failure.rst
View File

@ -73,8 +73,8 @@ in the deployment.
------------------------------------ ------------------------------------
Start the MinIO server process on the node and monitor the process output Start the MinIO server process on the node and monitor the process output
using :mc:`mc admin console` or by monitoring the MinIO service logs using :mc:`mc admin logs` or by monitoring the MinIO service logs using
using ``journalctl -u minio`` for ``systemd`` managed installations. ``journalctl -u minio`` for ``systemd`` managed installations.
The server output should indicate that it has detected the other nodes The server output should indicate that it has detected the other nodes
in the deployment and begun :ref:`healing operations <minio-concepts-healing>`. in the deployment and begun :ref:`healing operations <minio-concepts-healing>`.

4
source/operations/install-deploy-manage/decommission-server-pool.rst
View File

@ -310,7 +310,7 @@ the next step once decommissioning is completed.
If :guilabel:`Status` reads as failed, you can re-run the If :guilabel:`Status` reads as failed, you can re-run the
:mc-cmd:`mc admin decommission start` command to resume the process. :mc-cmd:`mc admin decommission start` command to resume the process.
For persistent failures, use :mc:`mc admin console` or review For persistent failures, use :mc:`mc admin logs` or review
the ``systemd`` logs (e.g. ``journalctl -u minio``) to identify more specific the ``systemd`` logs (e.g. ``journalctl -u minio``) to identify more specific
errors. errors.
@ -505,7 +505,7 @@ The command returns output similar to the following:
You can move on to the next step once MinIO completes decommissioning for all pools. You can move on to the next step once MinIO completes decommissioning for all pools.
If :guilabel:`Status` reads as failed, you can re-run the :mc-cmd:`mc admin decommission start` command to resume the process. If :guilabel:`Status` reads as failed, you can re-run the :mc-cmd:`mc admin decommission start` command to resume the process.
For persistent failures, use :mc:`mc admin console` or review the ``systemd`` logs (e.g. ``journalctl -u minio``) to identify more specific errors. For persistent failures, use :mc:`mc admin logs` or review the ``systemd`` logs (e.g. ``journalctl -u minio``) to identify more specific errors.
4) Remove the Decommissioned Pools from the Deployment Configuration 4) Remove the Decommissioned Pools from the Deployment Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~