Troublehsooting 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 pod diskjockey has the status crashLoopBackOff.

Solution: Check the correctness of the parameter ELMA365_HOST:

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 file /etc/resolv.conf, check line search, where the BRIX domain must be specified. For example, for the elma365.example.com domain name:

search example.com

• in file /etc/hosts, check the addresses and the aliases specified for them;
• add the A record to file /etc/hosts. 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 file resolv.conf after the command cat /etc/resolv.conf there is the line search, and also after the command docker exec elma365 kubectl -n kube-system logs -l k8s-app=kube-dns 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 configuration file values-elma365.yaml. Read more in Modify BRIX Enterprise parameters;
• On-Premises Standard: in the configuration file config-elma365.txt. Read more in Modify BRIX Standard parameters.

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 command lscpu, and check for free disk space using the command df -x overlay -x tmpfs. Compare the obtained data with the minimum system requirements:

• for On-Premises Enterprise see System requirements for BRIX On-Premises Enterprise;
• for On-Premises Standard see System requirements for BRIX On-Premises Standard.

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 can we improve the article?

YesNo

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