APAR status
Closed as program error.
Error description
For 21.0.3 IF009 and earlier releases, after activating the monitoring in Custom Ressource you'll experience continuing problems with CPE pods. The reason is a log created in the /tmp folder of the CPE-pods, which grows in size until the /filesystem runs out of space, you may see something like below: sh-4.4$ ls -lah /tmp total 9.6G drwxrwxrwt. 1 dba-user root 4.0K Mar 11 08:51 . dr-xr-xr-x. 1 root root 112 Mar 10 08:48 .. drwxrwxrwt. 1 dba-user root 81 Mar 10 08:48 .com_ibm_tools_attach drwxrwxrwx. 2 dba-user root 4.0K Mar 10 08:49 .instana -rwxrwxrwx. 1 root root 2.9M Mar 10 08:48 attach-tools-1.10.3.jar -rw-------. 1 dba-user root 0 Mar 11 12:44 filebeat-cpe-stderr---supervisor-jz_r9o91.log -rw-------. 1 dba-user root 0 Mar 10 08:48 filebeat-cpe-stdout---supervisor-uqy00pp5.log -rw-------. 1 dba-user root 0 Mar 11 12:44 filebeat-syslog-stderr---supervisor-nb_hc56v.log -rw-------. 1 dba-user root 0 Mar 10 08:48 filebeat-syslog-stdout---supervisor-c63529kc.log -rw-------. 1 dba-user root 0 Mar 11 12:44 filebeat-was-stderr---supervisor-0erfz0m1.log -rw-------. 1 dba-user root 0 Mar 10 08:48 filebeat-was-stdout---supervisor-fefvehey.log -rwxrwxrwx. 1 root root 221K Mar 10 08:48 javaagent-loader-1.3.38.jar -rw-------. 1 dba-user root 9.4G Mar 11 12:44 monitoring-stdout---supervisor-21zm7mhw.log -rw-r-----. 1 dba-user root 4.7M Mar 11 12:44 pch1054743961696643202.history -rw-r-----. 1 dba-user root 141K Mar 10 23:39 pch1054743961696643202.history.gz -rw-r-----. 1 dba-user root 22M Mar 10 20:50 pch2478810992635227001.history.gz -rw-r-----. 1 dba-user root 143M Mar 11 12:44 pch5756868004504818183.history -rw-r-----. 1 dba-user root 16M Mar 10 23:47 pch5756868004504818183.history.gz -rw-r-----. 1 dba-user root 197K Mar 10 20:50 pch9118937568089439927.history.gz srwx------. 1 dba-user root 0 Mar 10 08:48 supervisor.sock -rw-r--r--. 1 dba-user root 3 Mar 10 08:48 supervisord.pid
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Collectd PCH monitoring generates too much log entries * **************************************************************** * PROBLEM DESCRIPTION: * * For 21.0.3 IF009 and earlier releases, after activating the * * monitoring in Custom Ressource you'll see collectd PCH * * monitoring generates too much log entries. In your * * container, you can see * * /tmp/monitoring-stdout---supervisor-21zm7mhw.log continually * * increasing untill your pod runs out of space. This happens * * to all CP4BA components. * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
Defect fixed, we set a log rotate size as 50 MB.
Temporary fix
Comments
APAR Information
APAR number
JR65029
Reported component name
CLOUD PAK FOR A
Reported component ID
5737I2300
Reported release
L00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-06-13
Closed date
2022-06-14
Last modified date
2022-06-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
CLOUD PAK FOR A
Fixed component ID
5737I2300
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"L00"}]
Document Information
Modified date:
15 June 2022