9 Troubleshooting

• Troubleshooting for OBMA Patch Installation
  
• Troubleshooting for plato-apigateway-router
  

9.1 Troubleshooting for OBMA Patch Installation

If the OBMA services are not up after patch installation, please check the plato-config-server logs at the below location for further analysis.

/scratch/obma/domain/PlatoInfra/servers/Config_Server1/logs

If you see an error like “args list too long”, please navigate to the below file setUserOverrides.sh at location /scratch/obma/domain/PlatoInfra/bin and remove the unwanted properties. Then, please restart Config_Server1 on weblogic followed by the other managed servers. Once done, make OBMA services are up and running.

9.2 Troubleshooting for plato-apigateway-router

If you observe any SSL related issues in the plato-apigateway-router logs, then follow the below steps.

1. Stop the router by killing the router process.
2. Import the crt files into the java trust store on the VM on which the router is installed (the foundation machine ideally).
3. One crt file will be of the same foundation machine, while the other crt file(s) will be of the machine(s), the foundation machine has performed a sync with. Replace the password placeholder with the actual one.

   cd /scratch/ssl/cacerts
   
   keytool -importcert -file ofss-mum-2672.crt -keystore /scratch/obma/jdk-11.0.16/lib/security/cacerts -storepass <password> -noprompt
    
   keytool -importcert -alias domainCertForRouter -file ofss-mum-2550.crt -keystore /scratch/obma/jdk-11.0.16/lib/security/cacerts -storepass <password> -noprompt
   

4. Restart the router using through the OBMA installer using the below runlist.

   run_list ['recipe[obma_weblogic::deployapigateway_router]']