Excessively large engine-$$.out file in the /tmp directory

The Issue: 

Data Collector has created a file in the /tmp directory that is growing to an excessive size and is taking up space. 

The purpose of this file is to serve as a location for stdout from a running Data Collector. Under normal circumstances, this file does not receive much data and should not grow to a large size. Specifically, the rotatelogs is used to limit the size of this file to ~10mb. 

However, there are a few instances where this file will receive more data than usual, or grow to an excessively large size. 

• Adding certain Java parameters to your $SDC_HOME/libexec/sdc-env.sh file can result in extra output being sent to this /tmp file. This output is often useful for debugging, but can fill the file up quickly. An example of this might be the -Djavax.net.debug=ssl,handshake parameter used to debug SSL connections. 
• If the rotatelogs utility is not currently available on your machine, the /tmp/engine-$$.out file may continue to grow past the limited size of ~10mb. 

The Solution: 

There are a number of ways in which this issue might be remedied:

1. Check to see if you have any Java parameters included in your sdc-env.sh file that produce verbose output. If any of these options are no longer needed, they may be disabled/removed to reduce output. 
2. Check to see if the rotatelogs utility is available on your machine. This can be done by running the following command: command -v rotatelogs If this produces no output, you can attempt to install the utility using the following steps: 
   1. Install the httpd package using yum, apt, etc. depending on your distribution
   2. Run command -v rotatelogs once again to verify that it has now been installed. 
   3. Shutdown and restart the Data Collector
   4. Run ps aux | grep rotatelogs to verify that the rotatelogs utility is now working on the /tmp/engine-$$.out file.