Troubleshooting of possible BRIX On-Premises issues

The article covers the most common issues and errors encountered during the installation, configuration, and operation of the BRIX On-Premises system.

Issues during installation of BRIX On-Premises Standard

1. Issue: BRIX Standard system installation takes a long time. After running the docker exec elma365 kubectl get all -A command, a list of pods with the following statuses is displayed:

• Running.
• Completed.
• The diskjockey pod has the crashLoopBackOff status.

Solution: Check the correctness of the ELMA365_HOST parameter:

1. If an IP address of the virtual machine was specified during the system installation, verify its accuracy.
2. If a domain name is used during the system installation:

• Check the DNS server for an A record matching "DNS" <-> "IP address of the machine with BRIX". For example:

elma365.example.com. A 192.168.1.1

• In the /etc/resolv.conf file, check line search, where the BRIX domain must be specified. For example, for the elma365.example.com domain name:

search example.com

• In the /etc/hosts file, check the addresses and the aliases specified for them;
• Ddd the A record to the/etc/hosts file. For example:

192.168.1.1 elma365.example.com elma365

To apply changes, restart maybe required. Use the following command:

systemctl restart networking

To learn more about setting the ELMA365_HOST parameter, see Modify BRIX Standard parameters.

2. Issue: BRIX Standard is unresponsive or slow.

Solution: If in the resolv.conf file after the cat /etc/resolv.conf command, there is the line search, and also after the docker exec elma365 kubectl -n kube-system logs -l k8s-app=kube-dns command, there are synchronization errors, remove search.

How to remove it depends on the service used to generate the configuration file.

Common issues with BRIX On-Premises Enterprise and Standard

1. Issue: Invitations to the BRIX platform and password recovery emails are not being sent.

Solution: in BRIX, additional configuration of the SMTP server connection parameters is required:

• On-Premises Enterprise: in the values-elma365.yaml configuration file. Read more in the Modify BRIX Enterprise parameters article.
• On-Premises Standard: in the config-elma365.txt configuration file. Read more in the Modify BRIX Standard parameters article.

2. Issue: BRIX is only accessible within the corporate network.

Solution: Install a reverse proxy and configure the connection to BRIX using:

• HAProxy.
• Nginx.

3. Issue: BRIX does not install or operates slowly.

Solution: On the server, check the number of cores and the presence of AVX instructions using the lscpu command, and check for free disk space using the df -x overlay -x tmpfs command. Compare the obtained data with the minimum system requirements.

Was this helpful?

Thanks for your feedback!

Please specify why:

Recommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

How we can improve it?

YesNo

Please specify whyRecommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

Found a typo? Select it and press Ctrl+Enter to send us feedback