To begin troubleshooting an error, you can check the main log file for the OpenText Cloud Bridge Agent. This file is located on the host server at <Agent_install_dir>/agent/conf/daas_remote.log. You can adjust the logging level in the Agent console so this log collects the appropriate amount of data for your environment.
If you have too many Docker® container loggers running or logging levels configured too high, you might encounter disk space issues. In addition, the Agent can exceed the log limits so quickly that the error conditions are lost when the logs roll over. You can prevent or address these issues by manually changing the appropriate settings for the Docker® container in the <Agent_install_dir>/agent/conf/bridge-agent.yml file.
You can also configure logging levels in the <Agent_install_dir>/agent/conf/daas-remote.yml file. In the second section of the file, appenders can control the format of the log, the number of files, the size, and its rotation behavior.
NOTE:Avoid changing the log level for the org.apache.kafka file because it is very verbose and does not provide useful information.
Data source credentials that appear in red on the Data Sources tab are credentials that the Agent has been unable to decrypt because they were encrypted using different keys. If you change the encryption IV and key for your Agent instances, all credentials will be displayed in red. This will also happen if you import the credentials from an Agent with different keys. Ensure that you use the same encryption IV and key values for all Agent instances in your high availability environment. For more information, see Understanding Encryption IV and Key Values.
To fix this issue and ensure that your container automatically runs on Red Hat® Enterprise Linux® 8.3 Podman after a server restart, complete the steps in the following procedure. For more information, see the podman generate systemd reference page on the Podman website.
Stop your container:
podman stop bridge-agent
Use the podman generate systemd command to create your system file:
podman generate systemd --restart-policy=always --files --name bridge-agent
Locate the file with the name container-bridge-agent.service, then copy the file to the system folder:
cp container-bridge-agent.service /etc/systemd/system/container-bridge-agent.service
Enable the service:
systemctl enable container-bridge-agent.service
Start the service:
systemctl start container-bridge-agent.service
Check the status:
systemctl status container-bridge-agent.service
Restart your server to test it. For more information, see Restarting the OpenText Cloud Bridge Agent.
After a server restart, run the command podman ps and you should find your bridge-agent container running.