Is any one having problems with Sysmon? Both my machines have stopped monitoring HDD temperature etc, one since 16/1 and the other since 21/1.
It is possible that your monitor.db has become corrupted,
Try renaming or deleting /mod/monitor/monitor.db
Unfortunately you will lose your accumulated history - I don't know enough about the database to suggest how you could fix the data
HDRFOX4#cd /mod/monitor && mv monitor.db temp.db && sqlite3 temp.db ".clone monitor.db" && rm temp.db smart... done temp... done vmstat... done net... done state... done sqlite_autoindex_state_1... done HDRFOX4#
cd /mod/monitor && mv monitor.db temp.db && sqlite3 temp.db ".clone monitor.db" && rm temp.db
There is only a few hours' worth of data, but it graphs for me except on 2 hours, 6 months and 1 year scales.The original monitor.db (after processing as above) is small by comparison (76KB v. 437KB).
Is this a surprise???Deleting monitor.db seems to have fixed it, but the graphs show some weird results on the different timescales in as much as the data only starts at about 20:10!
Curious. It wouldn't present for me on any scale that I tried (I find it hard to believe I only tried 2h, 6m, 1y). In any case, why should it refuse to plot at those scales?There is only a few hours' worth of data, but it graphs for me except on 2 hours, 6 months and 1 year scales.
It is a surprise - the visualisation routines are not presenting it properly. When the available data does not go back as far as the requested timescale, the x axis is only labelled as far as the data goes... but the plot should then be the same for all timescales longer than that - and it isn't. This is most obvious for the CPU utilisation and network activity (which have nice spikey plots).Is this a surprise???