CA XCOM xcom.log file filling up due to repeated "XCOMU0047I Local transfer restarted" messages

Products

• XCOM Data Transport
• XCOM Data Transport - Linux PC
• XCOM Data Transport - Windows

Issue/Introduction

The xcom log (xcom.log) is filling up server space with the following entries repeated many times. The log file is growing at a rate of ~ 1 GB an hour.

+++
2021/02/03 14:13:00 TID=000210 []
    XCOMU0047I Local transfer restarted .

2021/02/03 14:13:00 TID=000210 []
    XCOMU0047I Local transfer restarted .
+++

There are files also piling up in the queue folder $XCOM_HOME/Q.
The last few lines of xcomqm -L is as below
+++
000305 - DONE       LOCAL   RESTARTABLE  #XCOMN0602E unable to open queue data file.

000306 - DONE       LOCAL   RESTARTABLE  #XCOMN0602E unable to open queue data file.

000307 - DONE       LOCAL   SUCCESSFUL   XCOMU0011I Transfer ended; 160 blocks (3159 bytes) transmitted in 31 seconds (101 bytes/second)
000308 - DONE       LOCAL   SUCCESSFUL   XCOMU0011I Transfer ended; 48 blocks (933 bytes) transmitted in 14 seconds (66 bytes/second)
+++

What is the root cause and how to recover from this issue?

Environment

Release : 11.6
Component : CA XCOM Data Transport for Linux PC

Cause

This type of looping problem is normally caused by an XCOM Queue corruption when trying to restart a transfer i.e. in directory $XCOM_HOME/Q there are one or more bad .MBR file or .IDX entries.
It was also revealed that "-cy" was being used to stop the xcomd. 
Using "-cy" is not advised because it brings down the daemon/scheduler immediately irrespective of whether there are running or scheduled transfers and should only really be used as a last resort. That option is also known to cause XCOM Queue corruptions.

Using "-s" is the recommended option to stop the xcomd. It sends a request to the scheduler and does not stop the daemon immediately if there is an active transfer going on.

Here is the relevant documentation page covering the xcomd options: CA XCOM Data Transport for UNIX/Linux 11.6.1 > Reference > Operating Environment > The xcomd Command

Resolution

To resolve the problem:
a. Stop the xcomd daemon using "xcomd -s"
b. Check no rogue xcom processes are running (ps -ef | grep -v grep | grep -i xcom)
c. Move out ALL files from directory $XCOM_HOME/Q to some backup directory (for reference only)
d. Start the xcomd daemon