Documentation update


To provide a better user experience, we have now created a separate documentation space for BMC Helix Automation Console (previously called BMC Helix Vulnerability Management).
Users of BMC Helix Automation Console can find the latest documentation at BMC Helix Automation Console. .

Configure log file settings

You deploy TrueSight Automation Console using Docker containers. Docker uses the /var/lib/docker as the default image installation folder, which contains a json.log file for every container. Over a period of time, this json.log file becomes huge in size and occupies the entire /var file system.

 Even if TrueSight Automation Console does not use this json.log file, the /var folder may cause issues in the Automation Console environment. To avoid running into space problems, you must perform these steps:

  1. To verify the current file size of the json.log files in your environment, run the following command:

    du -h `find /var/lib/docker/containers -name *-json.log*`

  2. Stop the application and the database:

    /opt/bmc/stackmanager stop --deployment application
    /opt/bmc/stackmanager stop --deployment database
  3. Stop the Docker service.

    systemctl stop docker

  4. Go to the /etc/docker/daemon.json file and append the following entry:

        "log-driver": "json-file",
        { "max-size": "20m", "max-file": "3" }
  5. Rename the /var/lib/docker/containers folder to create a backup folder.
  6. Start the Docker service and verify whether all containers are displayed.

    systemctl start docker
    docker ps -a

    When you rename the folder, the registry container is removed. 

  7. Run the registry container again after pointing to the correct dockerrepo folder on your system.

    docker run -d \  -p 5000:5000 \  --restart=always \  --name registry \  -v /opt/tsac_<version>/dockerrepo:/var/lib/registry \  registry:2
  8. Verify whether the registry is set up correctly.

    curl http://localhost:5000/v2/_catalog

    Alternatively, you can use the browser to verify whether the registry is accessible by using the following URL: http://<TSAC-Docker-Host>:5000/v2/_catalog 

  9. Start the database and then the application.

    /opt/bmc/stackmanager start --deployment database
    /opt/bmc/stackmanager start --deployment application
  10. Log on to TrueSight Automation Console to continue using the product. 
    You can choose to remove the backup folder created in Step 5. 

For more details, see the knowledge article  000378742: TrueSight Automation Console (TSAC) /var is 100% full and application is not accessible

Was this page helpful? Yes No Submitting... Thank you