At first I only noticed that there was a long delay at shutdown, IIRC having appeared after the upgrade to "vivid". After much painful investigation, I could trace it to swapoff.
After boot, the swap usage always kept growing, maxing out at approx. 2 GiB -- despite there was no memory pressure (1.6 of 4 GiB RAM used, default swappiness of 60). Then I read somewhere that RAM filesystems like tmpfs filesystems tend to be swapped out quickly. df showed the culprit:
~$ df -h /dev
Filesystem Size Used Avail Use% Mounted on
udev 2,0G 2,0G 0 100% /dev
~$ du -sh /dev/.bootchart/log
2,0G /dev/.bootchart/log
~$
Wondering what bootchart was doing, I found the last successful logs in /var/log/bootchart with PNGs of "trusty". From "utopic" there were only TGZs; nothing of "vivid" there.
So it seems to me too that bootchart is failing silently in vivid. It seems the collector process is not terminated properly and the logs aren't saved in the right place afterwards.
Wouldn't it make sense to deprecate the package and at least put a note in the README or package description? Especially since systemd, which is used in "vivid" by default, can do bootcharting on its own.
Also note that a few days after upgrading to "vivid", I manually switched back from systemd to upstart; bootchart fails nonetheless.
bootchart seems faulty to me in 15.04.
At first I only noticed that there was a long delay at shutdown, IIRC having appeared after the upgrade to "vivid". After much painful investigation, I could trace it to swapoff.
After boot, the swap usage always kept growing, maxing out at approx. 2 GiB -- despite there was no memory pressure (1.6 of 4 GiB RAM used, default swappiness of 60). Then I read somewhere that RAM filesystems like tmpfs filesystems tend to be swapped out quickly. df showed the culprit:
~$ df -h /dev
Filesystem Size Used Avail Use% Mounted on
udev 2,0G 2,0G 0 100% /dev
~$ du -sh /dev/.bootchart/log
2,0G /dev/.bootchart/log
~$
Wondering what bootchart was doing, I found the last successful logs in /var/log/bootchart with PNGs of "trusty". From "utopic" there were only TGZs; nothing of "vivid" there.
So it seems to me too that bootchart is failing silently in vivid. It seems the collector process is not terminated properly and the logs aren't saved in the right place afterwards.
Wouldn't it make sense to deprecate the package and at least put a note in the README or package description? Especially since systemd, which is used in "vivid" by default, can do bootcharting on its own.
Also note that a few days after upgrading to "vivid", I manually switched back from systemd to upstart; bootchart fails nonetheless.