Ce contenu n'est pas disponible dans la langue sélectionnée.
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 Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
					This section describes validation scripts you can use to troubleshoot issues with broker hosts.
				
2.3.1.1. Verifying Broker Host Configuration Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
		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 Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
		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
# oo-admin-chk
Check failed.
 FAIL - user user@domain.com has a mismatch in consumed gears (-1) and actual gears (0)!
			This problem can be fixed using the 
 
Copy to Clipboard
Copied!
 
 
Toggle word wrap
Toggle overflow
 
 
		
oo-admin-ctl-user command: 
oo-admin-ctl-user -l user@domain.com --setconsumedgears 0
# oo-admin-ctl-user -l user@domain.com --setconsumedgears 0
Example 2.2. Diagnosing Problems Using oo-admin-chk
oo-admin-chk
# oo-admin-chk
Gear 9bb07b76dca44c3b939c9042ecf1e2fe exists on node [node1.example.com, uid:2828] but does not exist in mongo database
/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.