Complete metadata update ?
Why did ALL of my resources get a metadata update? Every resource shows Last Updated Yestrday.
Comments
-
Randy W. Sims said:
Why did ALL of my resources get a metadata update? Every resource shows Last Updated Yestrday.
The log doesn't say (other than the fact the metadata was 'missing'). The most obvious cause of this would have been the deletion of updates.db in the UpdateManager folder. If you didn't delete that file manually, it might have been corrupt and deleted by Logos the last time you ran the software, and has now been re-created. (That's a guess. But I can't think of another explanation.)
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks, Mark. You jogged it loose. I shouldn't have posted last night; I had a gut feeling this was me. I tried to trace it back but didn't put it together until this morning when I read your post. TL;DR I had "Use Internet" to No after forcing a rebuild of Library Catalog several days ago and didn't realize until last night.
The day the CPU flaw was leaked I had started to take some initial baseline benchmarks to compare later after the patch. I closed most running apps, flushed the idle process tasks, and inside Logos, I set "use internet" to no. Then I got as far as running two tests: 1) rebuild bible index; 2) delete library catalog. I was going to run more tests the next day so left it. But the CPU patch was pushed out early and I forgot about benchmarking.
Next day I ran in to the Use Internet crash with search everything. I flipped it on, off, on, off, on, off while testing that crash, but again, I left it off.
Last night I went to do something and realised "Use internet" was off, turned it on, got what I was after and walked away. I came back just a little while later right before bed to look at something and noticed the yellow bar in the library and it wasn't going away....
I couldn't track it back back, but I had a feeling I was the most likely cause--I usually am. I had never left it online long enough after the catalog rebuild from days previous to update the metadata. Sorry for wasting anyone's time.
0 -
Mark Barnes said:
The most obvious cause of this would have been the deletion of updates.db in the UpdateManager folder.
FYI, metadata is stored in the LibraryCatalog, not the UpdateManager.
Andrew Batishko | Logos software developer
0 -
Mark Barnes said:
The most obvious cause of this would have been the deletion of updates.db in the UpdateManager folder.
FYI, metadata is stored in the LibraryCatalog, not the UpdateManager.
Apologies. I meant metadata.db in the Updates folder. (I'm sure it used to be in updates.db and some point in the distant past.)
I know metadata is stored in LibraryCatalog, but it appears that metadata.db stores the download status and version timestamp of the metadata. If that's wiped, LibraryCatalog wouldn't know that it's version of the metadata was current, and it would all be re-downloaded, wouldn't it?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0
