Crash - attempting Basic Search

In opening a basic Search box and trying to select the item to search in, when I click on the drop down list (illustration) I get a crash. It is repeatable.

Here are the logs. They refer to a malformed database (sigh) but I have no idea which one nor what to do at this point. Has anyone else seen this and does anyone have a suggestion? No idea which database this is trying to access.

1207.Logos4Crash.zip

Find more posts tagged with

Comments

David Bailey

Hi Mark,

Is that a collection you had created, or a resource called "History, World"?

Edit: it is a collection...

Have you tried to delete the collection and recreate it? Does it still crash?

Mark Smith

https://community.logos.com/discussion/comment/172614#Comment_172614

Definitely is a collection. It actually will let me search that collection. It just happened to be the last collection I searched so that's where Search opened up. The problem occurs as it is trying to open the drop-down list of other collections and resources. The malformed database would seem to be whatever Logos uses as it opens that list.

Mark Smith

Continues to crash. I reindexed over night but that wasn't the problem database.

Mark Barnes

https://community.logos.com/discussion/comment/172770#Comment_172770

Yes, I'd be confident this is an SQLite data corruption issue (Bradley will want to know about it, I'm sure, so it might be worth re-wording the title to include "SQLite data corruption"). The good news is that I'm pretty sure that the problem is with catalog.db which means you won't suffer data loss. You can just delete the file, and Logos will re-create it next time you load the application. (The file is in Logos4/Data/random/LibraryCatalog). The bad news is that it will take 15-30 minutes to re-create the file.

NetworkGeek

https://community.logos.com/discussion/comment/172772#Comment_172772

Does it populate the list of Collections from Tools/Collections/Open? If not sounds definitely like corruption; if it does let you open the list, try bringing up each collection and see if any particular one is causing a problem, if so you could delete it and then re-create it.

Mark Barnes

https://community.logos.com/discussion/comment/172774#Comment_172774

Does it populate the list of Collections from Tools/Collections/Open? If not sounds definitely like corruption; if it does let you open the list, try bringing up each collection and see if any particular one is causing a problem, if so you could delete it and then re-create it.

I'm 99% sure the problem is Mark's library, not with his collections.

Mark Smith

https://community.logos.com/discussion/comment/172772#Comment_172772

The good news is that I'm pretty sure that the problem is with catalog.db which means you won't suffer data loss

Actually I tried renaming that file and causing a rebuilding of that file but it loses all my collection data (which is extensive). Unfortunately I should have renamed the whole folder and rebuilt the folder since naming the file back again doesn't work. Some of the other files in that folder apparently now conflict. Thus I now have none of my collections.

I'm not totally wiped out (yet). I do have Logos 4 on another computer so may be able to restore all the files from there. I'll have to see.

Of course, we may have both guessed the wrong approach, but if not, this highlights the need for a way to locally backup critical data. It ain't in the cloud.

Mark Barnes

https://community.logos.com/discussion/comment/172780#Comment_172780

Actually I tried renaming that file and causing a rebuilding of that file but it loses all my collection data (which is extensive).

catalog.db does not hold your collections. It only holds a list of the books in your library. Collections are stored in the Documents folder (ResourceCollectionManager.db), not the data folder. Generally speaking (there are exceptions) it's safe to delete configuration files in the Data folder without personal data loss.

I'm still 99% sure that it's catalog.db causing the problem. Could you backup, then delete the file, re-load Logos, let it rebuild the library, and make it crash, then upload the logs for the whole of that operation?

Mark Smith

https://community.logos.com/discussion/comment/172798#Comment_172798

catalog.db does not hold your collections. It only holds a list of the books in your library.

Well all I did was rename catalog.db to catalog.dbo and let it rebuild catalog.db. It also built some other files as you see in the screen shot. The end result is all my collections are gone. So in the process of the rebuilding of catalog.db it lost my collections.

Now, of course, Search no longer crashes, but I don't have my collections which were created primarily for searching.

Here is what is in my LibraryCatalog folder (including the original catalog.db named catalog.dbo). These are the files with the today's date stamp so they were all created by forcing a rebuild of the catalog.db file.

BTW: Here is are the contents of my ResourceCollectionManager folder. As you can see Logos rebuilt those even though I did not touch that file. I will see if I can transfer over my files from this folder in my Beta install and see if they will work.

Mark Smith

https://community.logos.com/discussion/comment/172809#Comment_172809

I will see if I can transfer over my files from this folder in my Beta install and see if they will work.

That doesn't work. For some reason Logos updates those files when it opens and replaces them with an essentially empty file.

So, Logos guys, it would be nice to get this issue solved. I have a collections file in my Beta install and on another computer. Can I get Logos on this computer to recognize it?? If so, how?

Mark Barnes

https://community.logos.com/discussion/comment/172809#Comment_172809

Here is are the contents of my ResourceCollectionManager folder. As you can see Logos rebuilt those even though I did not touch that file.

There's no logical reason why your Collections should be deleted by deleting catalog.db - I've deleted that file in the past without this happening. Nevertheless, a sync ought to restore those collections, shouldn't it?

Mark Barnes

https://community.logos.com/discussion/comment/172821#Comment_172821

So, Logos guys, it would be nice to get this issue solved. I have a collections file in my Beta install and on another computer. Can I get Logos on this computer to recognize it?? If so, how?

I wonder if the beta has changed the format of this database, which is perhaps why it is created blank? If you restored a beta version of this file before you deleted catalog.db, that could explain why you have no collections now.

Mark Smith

https://community.logos.com/discussion/comment/172842#Comment_172842

I wonder if the beta has changed the format of this database, which is perhaps why it is created blank? If you restored a beta version of this file before you deleted catalog.db, that could explain why you have no collections now.

Yes, I wonder that, too. But no, I didn't try restoring it until after my collections disappeared.

Syncing does not restore one's collections. Therefore the need to be able to back them up and restore them locally.

Mark Smith

https://community.logos.com/discussion/comment/172862#Comment_172862

Still would like to hear from Logos on how this happened and if there is a fix using another collections database I have.

Mark Barnes

https://community.logos.com/discussion/comment/172863#Comment_172863

Do you want to upload your two collections databases (beta and broken) and we could compare them?

Mark Smith

https://community.logos.com/discussion/comment/172866#Comment_172866

Do you want to upload your two collections databases (beta and broken) and we could compare them?

Not much to compare. The smaller file is the new one in my SR-2 version (the empty one), the larger one is that of my beta installation.

5126.ResourceCollectionManager.zip

Mark Barnes

https://community.logos.com/discussion/comment/172891#Comment_172891

No idea whether this will work, but do you want to try using this file with your SR-2 installation?

6545.ResourceCollectionManager2.zip

Basically it's the beta file, but with the info table updated to the details that were in the SR-2 file. Worth a shot perhaps?

Mark Smith

https://community.logos.com/discussion/comment/172937#Comment_172937

Mark,

That did the trick. You are a smart guy. Thank you!

Where did you find info to change? I look at this file and see nothing that betrays a date or anything much I can interpret that makes the file unique.

Mark Barnes

https://community.logos.com/discussion/comment/172954#Comment_172954

Glad it worked! It looked like you'd done a lot of work on your collections.

The.db files contain multiple tables. One of the tables is called info, and it seemed to contain a unique identifier. I just copied it over.

Mark Smith

https://community.logos.com/discussion/comment/172967#Comment_172967

Yes I had done a bit of work on them. If I had to rebuild them all, I probably would do many fewer or build them as I need them.

I am curious about the cloud and collections, as there was a time I got a bunch of duplicated collections and was told this was due to some issue with syncing. I assumed my collections were on the Logos server. Maybe they are and got wiped out with whatever caused my problem. Maybe they aren't. I'd like to know.

Thanks for the explanation and for fixing my problem.

Dave Hooton

https://community.logos.com/discussion/comment/172842#Comment_172842

So, Logos guys, it would be nice to get this issue solved. I have a collections file in my Beta install and on another computer. Can I get Logos on this computer to recognize it?? If so, how?

I wonder if the beta has changed the format of this database, which is perhaps why it is created blank? If you restored a beta version of this file before you deleted catalog.db, that could explain why you have no collections now.

It's never advisable to use databases from a beta (newer version) in a non-beta (older) installation due to updated format/schema changes.

Dave Hooton

https://community.logos.com/discussion/comment/172973#Comment_172973

I am curious about the cloud and collections, as there was a time I got a bunch of duplicated collections and was told this was due to some issue with syncing.

That was a combination of syncing and L4 incorrectly marking collections as edited when there had been no changes

However, syncing of collections remains a problem for a fresh installation. It often has to be "encouraged" by building & editing a collection, as well as restarting L4.

Dave Hooton

https://community.logos.com/discussion/comment/172780#Comment_172780

Actually I tried renaming that file and causing a rebuilding of that file but it loses all my collection data (which is extensive). Unfortunately I should have renamed the whole folder and rebuilt the folder since naming the file back again doesn't work. Some of the other files in that folder apparently now conflict. Thus I now have none of my collections.

I'm not totally wiped out (yet). I do have Logos 4 on another computer so may be able to restore all the files from there. I'll have to see.

Whilst deleting & renaming databases can be fruitful a corrupted/malformed database is far better left to Logos Tech Support when it is this disruptive. The safer alternative was to use your beta installation and Quick
Installation onto multiple computers (although it would have to be an installation to the same or a newer Beta); I have never had issues with collections/documents nor database schemas.