Comment 5 for bug 1472338

In the last couple of recreates I checked the wrong setting for memory usage. I should have been looking on the host for a container setting under /sys/fs/cgroup/memory/ rather then using memory stat commands like free. So I now have a process running to that checks memory usage every minute for the container and so the next time the refresh power state errors are re-created, we can get a better idea of memory usage patterns and what direct correlation if any exists.

This is what the data would look like:

Monitoring memory usage for maas container...
Recording memory usage in bytes at Sat Aug 22 00:42:30 UTC 2015
5802795008
Recording memory usage in bytes at Sat Aug 22 00:43:30 UTC 2015
5964120064
Recording memory usage in bytes at Sat Aug 22 00:44:30 UTC 2015
5921673216
Recording memory usage in bytes at Sat Aug 22 00:45:30 UTC 2015
5943955456
Recording memory usage in bytes at Sat Aug 22 00:46:30 UTC 2015
5792681984
Recording memory usage in bytes at Sat Aug 22 00:47:30 UTC 2015