How to Troubleshoot the Bold Reports Application Deployment in Linux Environment

In this section, we cover common deployment challenges specific to Bold Reports on Linux and offering effective solutions.

• Permission for a specific user.
• Get a journal log if the service is in an inactive or expired state for Bold Reports.
• UMS site deployment is pending.
• Deployment failed due to an incorrect protocol.

Permission for a specific user

Confirm whether the specific user has full root privileges in the Linux environment before deploying the Bold Reports application. If not, follow the steps below to grant full privileges to the user. The usermod command can be used to change the user’s group membership, which will give them root privileges. To do this, run the following command:

usermod -aG root username

Example:

usermod -aG root boldreports

Get a journal log if the service is in an inactive or expired state for Bold Reports

1. Ensure the service is active in Linux by running the command below.

   sudo systemctl status bold-*
   

2. If the status shows exited or inactive, review the journalctl logs for the service using the command below.

   journalctl -u bold-reports-api.service --since "10 min ago"
   

List of services in Bold Reports application

• bold-reports-api.service
• bold-reports-jobs.service
• bold-id-api.service
• bold-ums-web.service
• bold-reports-service.service
• bold-reports-viewer.service
• bold-reports-web.service
• bold-id-web.service

UMS site deployment is pending

Check whether the user has read, write, or execute permission for the /var/www/bold-services/application/app_data/reporting directory.

1. Navigate to the location and list the permissions for all folders.

   cd /var/www/bold-services/application/app_data ls -l
   

   

2. Next, grant permissions to the reporting folder using the following command.

    sudo chmod -R 777 reporting
   

3. Refer to the document to create the site in ums/sites.

Deployment failed due to an incorrect protocol

1. Ensure the application is deployed using the correct protocol (http/https)
2. In case the application has been deployed with the HTTPS protocol but doesn’t have SSL, you will need to change the protocol in the product.json file from HTTPS to HTTP. The file can be found at the following location: /var/www/bold-services/application/app_data/configuration/product.json.
3. Restart the service using the below command.

   sudo systemctl restart bold-*