Mustgather: Collecting data to diagnose issues with FileNet Content Manager containers

Troubleshooting

Problem

This document describes the general information and diagnostic data needed to start troubleshooting issues related to IBM FileNet Content Manager containers. Include the diagnostics retrieved from using this document when opening a case for problems related to FileNet Content Manager containers running standalone or in Cloud Pak for Automation.

Resolving The Problem

Overview of FileNet Content Manager diagnostic information

As needed diagnostic information

Operator logs

Detailed diagnostic collection steps

These are the detailed steps to gather different types of data for FileNet Content Manager. When running diagnostic commands, run them from an empty collection directory to make it easy to package the files. Run the commands from the project or namespace containing FileNet or use the -n <namespace> flag with all kubectl commands.

1: Provide a detailed description of the problem and your environment

Provided a detailed description of your issue. Include screen captures and re-create steps if possible.
Is it an intermittent or re-creatable issue? Has this always been an issue or an issue that started only after a change occurred?
What is the business impact? Should we be aware of any deadlines impacted by the issue?
Provide a reference to the documentation being followed for the failing operation.
Which platform are you using (OpenShift, managed OpenShift, other Kubernetes platform)?
Provide version (and vendor as needed) for the following products:

    FileNet Content Manager
    Database vendor and version
    LDAP vendor and version
    If this is a IBM Cloud Pak for Automation deployment, what version?
For deployment issues, were images downloaded from Entitled Registry or Passport Advantage?

2: Gather the following configuration information

If using OpenShift, provide the output of this command:
```
oc version > version.txt
```
Provide the output of this command:
```
kubectl version >> version.txt
```
Provide the Custom Resource(CR) .yaml file used by the operator to set up the environment
```
kubectl get icp4acluster -o yaml > config.yaml
```
Collection information about the nodes.
```
kubectl get nodes -o wide > nodes.txt
```
Collect information about the pod statuses
```
kubectl get pods > pods.txt
```

Collect information about the pod containers

kubectl get pods -o jsonpath="{..image}" > containerInfo.txt

On OpenShift gather route configuration
```
oc get route > routes.txt
```
Note: If needed, more detailed route config info can be gotten with -o yaml option
Collect the defined secrets
```
kubectl get secrets > secrets.txt
```
Collect the defined persistent volume claims
```
kubectl get pvc > pvcs.txt
```

Collect the description and log of any pod you are having issues with:

kubectl describe pod <pod-name> > describe-<podname>.txt
kubectl logs <podname> > log-<podname>.log

3: Log data

Gather the logs from the persistent volume.

Review the get pods output to determine the running FileNet Content Manager pod names
Review the get pvc output to determine the location of the cpefnlogstore persistent volume.
Provide a copy of these files from each running FileNet pod found in this directory.
<cpefnlogstore volume>/FileNet/<FileNet Content Manager Pod name>
- messages.log
- p8_server_error.log
- pesvr_system.log

4: Collect Operator logs

If you are having issues during the deployment by the operator then collect the operator logs described in the installation troubleshooting page.

What to do next

Review the log files and traces at the time of the problem to try to determine the source of the problem.
Check these locations for known issues:
- Search in the Cloud Pak for Automation Support Page.
- Review the FileNet Content Manager documentation.
Once you completed gathering all the needed info and diagnostics, you can add them to your case. Alternatively, you can upload files to ECURep. For more information, see Enhanced Customer Data Repository (ECuRep) - Overview.

Related Information

Mustgather: Collecting data to diagnose issues with IBM Cloud Pak for Automation

Document Location

Worldwide

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"ARM Category":[{"code":"a8m0z0000001h6UAAQ","label":"Container"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"5.5.4;and future releases","Line of Business":{"code":"LOB45","label":"Automation"}},{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS2JQC","label":"IBM Cloud Pak for Automation"},"ARM Category":[{"code":"a8m0z0000001evoAAA","label":"FileNet Content Manager"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)","Line of Business":{"code":"LOB45","label":"Automation"}}]

Tips