Troubleshooting a Siebel Cloud Manager Instance

The SCM instance might not run in any of the following cases:

When the OCI configuration is not set up properly, the SCM instance is blocked and a response like this is received:
```
    {
        "data": {},
        "message": "Configuration File not Found. Please refer this link to check how you can configure OCI configuration in your instance. https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdkconfig.htm Check Cloud Manager Logs for more information about the error.",
        "status": "failed"
    }
```
The message contains information about the reason for the failure. In this case, the message says Configuration File not Found. Check if the OCI configuration file is set up properly.
Any kind of exception raised by OCI might be caught and you can troubleshoot accordingly. All these logs are captured in the SCM application. View the log file to see detailed info about the error that occurred. After making the necessary changes in the configuration file, restart the application to check whether the error is still present.
When the SCM container fails to start. You can check the status of the SCM container and restart it as follows:
1. SSH in to the SCM instance.
2. Check the status of the SCM container:
```
sudo podman ps
```
  If this command does not return any output, it implies that the container hasn't started. In this case, check the cloud- init-output.log file:
```
vi /var/log/cloud-init-output.log
```
  If the log indicates that the container has failed or is not running, run the following command to confirm the status of the SCM container:
```
sudo systemctl status cloudmanager
```
  If the command output displays the container status as FAILED, restart the SCM container and check its status again as follows:
```
sudo systemctl restart cloudmanager
sudo systemctl status cloudmanager
```