IT40491: LARGE LOG.TXT FILE OF SEVERAL GB IN /ROOT/.TARGETCLI ON VSNAP

APAR status

• Closed as program error.

Error description

• On the IBM Spectrum Protect Plus vSnap host, the log.txt file
  in directory /root/.targetcli can grow very large to several GB
  potentially filling up the root '/' filespace.
  The size of the log.txt file depends on the iSCSI
  mount/dismount activity.
  If there are many mounts and dismounts, the file will grow
  large because the logging level for the ?vsnap-target? service
  is set to ?debug? and there is no option to prune that log.
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.x
  
  Additional Keywords: SPP, SPPLUS, TS008879886, logs
  

Local fix

• On the vSnap host,
  1. Delete file /root/.targetcli/log.txt
  2. Set the log level to info:
       sudo vsnap_targetcli set global loglevel_file=info
  3. Define a log rotation by creating a file named :
       /etc/logrotate.d/targetcli
  4. Add the following definition in that file :
       /root/.targetcli/log.txt {
              size 10M
              rotate 10
              missingok
              notifempty
              nocompress
              sharedscripts
       }
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.9 and 10.1.10          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Recommendation: Apply fixing level when available. This      *
  * problem is currently projected to be fixed in IBM Spectrum   *
  * Protect Plus level 10.1.10.2 and 10.1.11. Note that this is  *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• The log file previously located in /root/.targetcli has been
  moved to /opt/vsnap/log, and rotation has been implemented to
  the new file to ensure it does not grow unnecessarily large.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• vSnap    iSCSI
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels