| 2017-04-19 11:31:28 |
Simon Pasquier |
description |
In MOS 9.0 with Telemetry Plugin v 1.0.1, the following file grew up to ~40GB:
/tmp/heka-influxdb-points.log
Because of this, the root partition nearly filled up and could have possibly impacted the environment if manual proactive action wasn't taken.
Actual Results:
root@ic3-ctl01-scc:/tmp# ls -lh
total 40G
-rwxr-xr-x 1 root root 40G Apr 14 15:33 heka-influxdb-points.log
Expected Results:
To have the proper configuration in place out of the box (whether its defining logrotate configuration, or making configuration change to the service itself) to prevent this file from growing to such a large size. |
In MOS 9.0 with Telemetry Plugin v 1.0.1, the following file grew up to ~40GB:
/tmp/heka-influxdb-points.log
Because of this, the root partition nearly filled up and could have possibly impacted the environment if manual proactive action wasn't taken.
Actual Results:
root@ic3-ctl01-scc:/tmp# ls -lh
total 40G
-rwxr-xr-x 1 root root 40G Apr 14 15:33 heka-influxdb-points.log
Expected Results:
To have the proper configuration in place out of the box (whether its defining logrotate configuration, or making configuration change to the service itself) to prevent this file from growing to such a large size.
Workaround:
Add a cron job that deletes the file periodically. |
|
