Resolving JMS Fleet Health Issues
Issue 1: The fleet does not have any managed instances.
Resolution Options:
The following outlined option(s) are available to resolve the issue:
Option 1: Use the OMA installer provided by JMS or installation script to install agents and deploy the JMS plug-in on hosts you want to monitor within the fleet:
Option 2: Register instances with installed agents and the deployed JMS plug-in that aren't currently registered to any JMS fleet. This can be done using the "Add Managed Instance(s)" action in the Managed Instances table.
Option 3: If the fleet is no longer needed, delete it.
Option 4: Review your policy to verify group definitions, resource type, or compartment in the policy statements. Ensure that your policy includes the following policy statement:
ALLOW DYNAMIC-GROUP JMS_DYNAMIC_GROUP TO MANAGE log-content IN COMPARTMENT $(compartmentName)$(compartmentName) is the compartment to which the fleet belongs.
Issue 2: The JMS plugins registered to the fleet encountered errors while trying to push inventory data to the fleet inventory or operational logs, probably due to missing policies.
Resolution Options:
The following outlined option(s) are available to resolve the issue:
Option 1: If an inventory log isn't configured to the fleet, use the Log Configuration Wizard in the JMS Fleets listing page to recreate the missing inventory log.
- Go to the Fleet Listing Page
Option 2: If an inventory log isn't configured to the fleet, associate a new or existing inventory log object with the fleet by using the
UpdateFleet API.
Option 3: If an inventory log is already configured for the fleet, review your policies to ensure they include the following policy statements:
ALLOW RESOURCE jms SERVER-COMPONENTS TO MANAGE log-groups IN COMPARTMENT $(compartmentName)
ALLOW RESOURCE jms SERVER-COMPONENTS TO MANAGE log-content IN COMPARTMENT $(compartmentName)$(compartmentName) is the compartment to which the fleet belongs.