How to "reset" tags which seem to have become corrupted?

Graham Criddle
Graham Criddle MVP Posts: 33,188
edited November 2024 in English Forum

For context please see the discussion at http://community.logos.com/forums/t/79694.aspx

It appears that David's (he started the other thread) tagging information has become corrupt on the Logos servers which results in incorrect information being synced down to his iPad app.

Appreciate thoughts on:

  • Whether the conclusion in that thread is the most likely explanation or whether there is something else which could be causing this
  • If the tag information on Logos servers has become corrupted what would be the best way of rebuilding this? My concern is that deleting information from the local configuration may cause corrupted information to be synchronised down

Thoughts and insight appreciated

Thanks, Graham 

Comments

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    tagging information has become corrupt on the Logos servers

    The first step in trying to fix this would be to run the command sync repair from the PC where the tagging is correct.

    Whether the conclusion in that thread is the most likely explanation or whether there is something else which could be causing this

    The thread could indicate (a) something went wrong in uploading tag info from the desktop to the cloud; or (b) something went wrong in downloading tag info from the cloud to iOS. I don't think there's enough info yet to be sure either way.

    The only way to test this for certain would be to look at the tag info on a third, clean device. This could be done, for example, by installing Faithlife for iOS. But I'm not sure that's necessary at this stage.

    My concern is that deleting information from the local configuration may cause corrupted information to be synchronised down

    I would agree.

    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!

  • Graham Criddle
    Graham Criddle MVP Posts: 33,188

    Hi Mark

    tagging information has become corrupt on the Logos servers

    The first step in trying to fix this would be to run the command sync repair from the PC where the tagging is correct.

    I'm not familiar with that command - can you expand on what it does?

    Thanks, Graham 

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    I'm not familiar with that command - can you expand on what it does?

    Would you be surprised if I said that there's no documentation!? I only know about it because it's listed as a valid command in the help file. I assume (but don't know for certain) sync repair is to sync now what update resources is to update now (i.e. it checks all the data, rather than just the data after the last timestamp).

    There is also a sync check command, which is somewhat better documented: http://community.logos.com/forums/p/43996/327499.aspx#327499 

    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!

  • David
    David Member Posts: 234 ✭✭

    Mark & Graham,

    Thanks for all your help. I performed a "sync repair" and, after some time, I received a warning symbol as a sync icon. I restarted Logos several times and now the sync icon is normal. However, the tagging situation is still the same. The mytags are correct on Logos 5 but incorrect on my iOS devices. The only thing that seems to fix the problem is for me to add a new tag in Logos 5 and delete it. This forces a Library Catalog update and I see the correct tagging information on my iOS device.

    I have attached my log files from Logos 5. These logs are only from a fresh restart of Logos after I performed the sync repair. Any further help would be appreciated. Thanks.

    Dave

    6560.LogosLogs.davidschlup.20140103-101933.zip

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Hi Dave,

    I notice in the logs that there are a number of errors when Logos is attempting to send/receive data from it's servers. That's obviously not going to be helping.

    It's hard to know what's causing the errors. The three possibilities are (1) A bug, (2) A problem with Logos' servers, or (3) A problem with your Mac, such as an over-zealous firewall or web filter.

    If it's (1), there's a possibility that the latest beta may help, as another user had similar problems which are fixed in that beta. However, running the beta is not without risk, and there's no guarantee that your problem is the same as his.

    I doubt it's (2), as I'd expect more reports if so.

    You could check (3), by temporarily disabling any software you have the might be interfering.

    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!

  • David
    David Member Posts: 234 ✭✭

    Mark, 

    Thanks for your reply. I had a suspicion something wasn't right. I have a feeling that the contents of my Library Catalog.db are not doing well with the Logos servers. Is there a safe way of rebuilding the Library Catalog.db? I saw an existing thread that stated your Collections may be deleted. I definitely don't want that to happen. Also, do you think this might fix the syncing errors? Thanks.

    Dave

  • David
    David Member Posts: 234 ✭✭

    Mark,

    Another thing. I went ahead and re-tagged (selecting all and adding a group tag) all of my library resources. I also reinstalled my iOS apps. It appears to have solved the mytag problem on my iOS device. However, I was wondering if you still see the sync errors in my logs. These logs were take after my re-tagging and after a restart of Logos 5. Thanks.

    Dave

    3884.LogosLogs.davidschlup.20140103-171850.zip

  • Jack Caviness
    Jack Caviness MVP Posts: 13,599

    If it's (1), there's a possibility that the latest beta may help, as another user had similar problems which are fixed in that beta. However, running the beta is not without risk, and there's no guarantee that your problem is the same as his.

    5.2a Beta 1 Mac has some show-stopper bugs. If anyone wants to see if their problem is fixed in 5.2a, they need to wait for Beta 2.