Troubleshooting

Start a Bash session

Docker

1. Find the CONTAINER ID by command

docker container ls -a

E.g: the container ID = d1769cb64afe

2. Start a Bash session with the command docker exec -it <container id> bash

docker exec -it d1769cb64afe bash

Kubernetes

1. Find the MetaDefenteder ICAP Server pod with the command

kubectl get pods -A

→ pod name: md-icapsrv-77c4654f4b-bkclc

→ namespace: default

2. Start a Bash session

command:

kubectl exec -n <namespace> -it -c <container name> <pod name> bash

​

E.g:

kubectl exec -n default -it -c md-icapsrv md-icapsrv-77c4654f4b-bkclc bash

Execute the collect support packages script

To create a package you must start the script found under

${INSTALL_ROOT}/usr/bin/mdicapsrv-collect-support-data.sh

As the script processes the necessary information, the script generates the support package output.

The package file is a tar.gz archive with the following name:

mdicapsrv--support-<TIMESTAMP>.tar.gz

Where the timestamp was the date when the package was generated.

Example:

mdicapsrv--support-1660647413.tar.gz

The generated package will be placed in the same location as the script that was called.

Copy the support package from the container to outside

Docker

Use docker cp | Docker Documentation docker cp [OPTIONS] CONTAINER:SRC_PATH DEST_PATH|-

Example:

docker cp d1769cb64afe:/mdicapsrv--support-1660647413.tar.gz /home/icap

Kubernetes

Use kubectl cp Kubectl Reference Docs (kubernetes.io)

# Copy /tmp/foo from a remote pod to /tmp/bar locally

​

  kubectl cp <some-namespace>/<some-pod>:/tmp/foo /tmp/bar

Example:

kubectl cp default/md-icapsrv-77c4654f4b-bkclc:/mdicapsrv--support-1660648209.tar.gz /home/icap/mdicapsrv--support-1660648209.tar.gz