The only real problem i see here is that your operator table for some weird reason misses the "API_KEY" column, that we can fix easily if we get your settings.rds.
Concerning the record manager log entries, lets dissect them one by one:
- Failed to load realtime cache, file corrupt, empty or not found.
Loosing the realtime cache is no disaster, the historical records contains all the samples needed for reports. The realtime records are merely a cache for producing graphs in the monitor info page and dashboard fast, see here for more info: http://community.kaseya.com/xsp/f/159/t/18096.aspx
- Failed to flush statistics to disk: Failed to send realtime records to record manager, return code 3 exception code 0.
Operation failed, ie it could contact the record manager, but it could not store the records, have you seen this more than once ?
- Failed to flush statistics to disk: Failed to send records to record manager, return code 1 exception code 1727.
Record manager is down (1727 = Windows error, RPC server unreachable), here KNM just say it cant send the records to record manager, but they are keept in a local cache until the record manager comes back up again.
Might have started with this:
- Record manager was not properly shutdown, maker file found. Will clear realtime cache, might be corrupt.
When the record manager starts it will go trough the realtime cache and validate all blocks in it, since its a to large extent a memory mapped block based storage, where write operation may occur in any part, it happens that it gets corrupted when the computer loses power or the process is unexpectedly shutdown. Loosing there cache is not a big deal, its rebuilt again.
Our user account issues persist. Good to have the charts back though, thank you for the info on Record Manager.