XTdb

[James Sentman]

Those messages were logged during the nightly database checkup. There is still something in the saving of data that can cause the index to get out of sync evidently. It’s not something that is a problem with the graphs that only show the last 24 hours. I discovered it while working on the longer term graphs that I haven’t released yet. I’ll keep looking into that, but after logging that message the index is rebuilt and so is fine again, until something adds a new index node incorrectly somewhere. It might be part of the reaping of old database records that also happens during the night.

For now ignore it, if you notice something amiss in one of your graphs you can rebuild the index manually for just that unit in the units detail page in XTdb or just scan the entire database again with the scan and repair menu item. I don’t think you’ll ever see a problem in the current data though and there is no danger of data loss, it’s still there just not indexed properly for a reason i don’t fully have a handle on yet.



> On Oct 18, 2017, at 8:54 AM, Hendrik van Eeden <hvaneeden at comcast.net> wrote:
> 
> Updated XTension and XTdb to the latest version yesterday.  found this is the log this morning.  When I first launched XTdb, I got the “invalid index” notice for each and every unit.  Last night I got these in the log.  Should I ignore?  I am running El Capitan yet.
> 

Thanks,
 James


James Sentman                       http://www.PlanetaryGear.org		http://MacHomeAutomation.com




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.machomeautomation.com/pipermail/xtensionlist/attachments/20171018/9b1136a9/attachment.html>