Este contenido no está disponible en el idioma seleccionado.

2.3. Validation Scripts


OpenShift Enterprise includes validation scripts that detect and report potential problems with broker and node hosts. Red Hat recommends that these scripts are used for monitoring purposes when performing the initial installation. After initial installation, these scripts can help troubleshoot any OpenShift Enterprise problems. Validation scripts detect common user errors, as well as unexpected failures. See the OpenShift Enterprise Administration Guide at https://access.redhat.com/site/documentation for more information on validation scripts.

2.3.1. Broker Host Scripts

This section describes validation scripts you can use to troubleshoot issues with broker hosts.

2.3.1.1. Verifying Broker Host Configuration

Use the oo-accept-broker script without any options to report potential problems in the broker host configuration. The output from this script indicates how many problems are found.

2.3.1.2. Fixing Gear Discrepancies

Use the oo-admin-chk script without any options to compare gear records in the broker's Mongo datastore to the gears actually present on the node hosts. The script reports any discrepancies that are found.

Example 2.1. Diagnosing Problems Using oo-admin-chk

# oo-admin-chk
Check failed.
 FAIL - user user@domain.com has a mismatch in consumed gears (-1) and actual gears (0)!
Copy to Clipboard Toggle word wrap
This indicates a mismatch between the number of consumed gears and the number of actual gears, which can occur under certain race conditions.
This problem can be fixed using the oo-admin-ctl-user command:
# oo-admin-ctl-user -l user@domain.com --setconsumedgears 0
Copy to Clipboard Toggle word wrap

Example 2.2. Diagnosing Problems Using oo-admin-chk

# oo-admin-chk
Gear 9bb07b76dca44c3b939c9042ecf1e2fe exists on node [node1.example.com, uid:2828] but does not exist in mongo database
Copy to Clipboard Toggle word wrap
This output indicates that although a gear was destroyed from the broker host's MongoDB, it was not completely removed from the node host. This can be due to storage issues or other unexpected failures. You can fix this issue by deleting the gear from the /var/lib/openshift directory, and removing the user from the node host.
These are two examples of the issues that could occur when running the oo-admin-chk script. The script should be self-explanatory to resolve most problems.
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat