Files
nexus/knowledgebase/csd-wiki/ICSD/Troubleshooting-guide-for-CMS-UI-report-scheduler-issue_688996426.md

3.0 KiB

Troubleshooting-guide-for-CMS-UI-report-scheduler-issue_688996426

Problem What didn't work? Add a short description of the problem and symptom in this Text Data macro.

We received many incidents from DN in EU8 farm about CMS UI report scheduler function is not stable, while with existing CMS UI logs, we can't find the root cause because of limited information in the log, so we need Ops team to help get the thread dump and heap dump of CMS UI pod when the issue happens again.

Issue 1992037 - Scheduled Reports logs lack helpful messages for better troubleshooting purpose

Issue 2003256 - Scheduled Reports status always shows "pending"

Issue 2113063 - EU8 Report scheduled at CMS UI are often getting stopped or not working

Environment

Which enviroment and customer tenant that are affected? Add a short description in this Text Data macro EU8 DN prod tenant

Cause

*Why did this happen? Describe the root cause of the problem in this Text Data macro.*The root cause is not found yet, need to get thread dump and heap dump of CMS UI pod to get more information.

Solution

How do we fix it? Describe how someone would solve the problem in a concise, step-by-step guide in this Text Data macro.

Follow the steps when the CMS UI report scheduler is hanging or not working again:

  1. Collect all CMS browser logs
  2. Get CMS UI thread dump and heap dump:
    1. run kubectl command to enter CMS browser pod: kubectl exec -it -n <pod_name> -c <pod_container_name> bash 2. go to one folder which have write permission e.g. /tmp. 3. run `jstack ` to get thread dump, then wait for 10 seconds to get a 2nd thread dump for comparation purpose 4. run 'jmap -dump:file=headdump ' to get heap dump 5. share the heapdump and thread dump to CMS R&D

Conveniently search and link related articles through List Data macro.

Related pages