Administering BRIX Standard

Update certificates for Kubernetes cluster

During the update of BRIX Standard, automatic updating of Kubernetes cluster certificates is performed. You can also manually initiate the update by executing the installation command with the --renew-certs-k8s key.

sudo ./elma365-docker.sh --renew-certs-k8s

Reinstall BRIX Standard

To reinstall BRIX, run the installation script with the --reset key.

For online installation:

sudo ./elma365-docker.sh --reset

For offline installation without internet access:

sudo ./elma365-docker.sh --offline --reset

начало внимание

When running the script, all data stored in BRIX Standard (KinD) will be deleted.

конец внимание

Clean the node for subsequent installation of BRIX Standard

To clean the host node for subsequent installation of BRIX Standard (KinD), run the installation script with the --delete key:

sudo ./elma365-docker.sh --delete

Diagnostics and troubleshooting

1. Collect diagnostic information.

начало внимание

For accurate collection of network status diagnostic information, the script requires the net-tools utility.

конец внимание

To collect diagnostic information about the system status, run the installation script elma365-installer-docker.sh with the --diag key:

sudo ./elma365-docker.sh --diag

After starting, the installation script will determine the version of the installed BRIX Standard (KinD) and offer a method to save diagnostics.

To continue with the diagnostics collection, enter one of the options:

[S]. Collect and upload diagnostic information to the BRIX server.

The installation script will return a link to download the diagnostic information. Example link: https://nc.elma365.tech/iuq1fg.txt.

[F]. Collect and save to a file on a local disk.

The installation script will provide a path to the file with diagnostic information, for example, /root/elma365-2023.2.15/elma365-diagnostic-20230410-142556.

The installation script will then collect the diagnostic information.

2. Generate logs and check service status.

To get logs from application services, run the command:

docker exec elma365 kubectl logs -l tier=elma365 --all-containers > logs.txt

To view logs from a specific service, replace [name] with the desired service:

начало примера

Example:

docker exec elma365 kubectl logs -l app=main

конец примера

To view logs in real-time, add the -f option.

начало примера

Example:

docker exec elma365 kubectl logs -l app=main -f

конец примера

To check the status of services, run the command:

docker exec elma365 kubectl get pod

The result will be displayed in a table format with a list of services. Services should be in the Running status, and tasks should be in the Completed status.

List of available commands for elma365-installer-docker.sh

To view the list of all available commands, run the installation script with the key --help:

sudo ./elma365-docker.sh --help

Доступные команды:

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