Indexing problems

I downloaded an upgrade yesterday and waited during night for Logos to do the first-time indexing. When I came to office this morning the indexing icon was not visible in the right corner. After exploring the program for a while, Logos crashed. When I relaunched the program, the indexing process started once again. I waited most of the day to discover that the indexing icon disappeared again, and I was wondering if the indexing had stopped. When I closed Logos and reopened it, the first-time indexing process started again with twelve more hours remaining. Can someone help me?

Find more posts tagged with

Comments

Dave Hooton

We will need some logs to help sort this issue - http://wiki.logos.com/Diagnostic_Logging (it helps to zip the files before uploading, we need Logos4Indexer.log)

Raymond Urne

https://community.logos.com/discussion/comment/57086#Comment_57086

I don't know if this is what you ask for:

2210.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2210.Logos4Indexer.log:550:0]

6406.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/6406.Logos4.log:550:0]

I tried to index once again after enabling logs. Same problem occurred. After waiting 10 hours (when still 1 h 30 min was remaining) I was asked to restart Logos because new resources was available. When I did, the first time indexing started again. 1o more hours to wait....

Damian McGrath

https://community.logos.com/discussion/comment/57452#Comment_57452

Raymond. You will need to provide logs in which you haven't paused the indexing after 11 minutes.

Raymond Urne

https://community.logos.com/discussion/comment/57508#Comment_57508

We try again. Hopefully these logs are what you are looking for:

2068.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2068.Logos4Indexer.log:550:0]

Dave Hooton

https://community.logos.com/discussion/comment/57810#Comment_57810

We try again. Hopefully these logs are what you are looking for:

Yes, there are quite a lot of errors. Hopefully Logos Tech will now investigate.

Raymond Urne

https://community.logos.com/discussion/comment/57823#Comment_57823

Do I have to contact Logos Tech? Or will they investigate based on this post?

Dave Hooton

https://community.logos.com/discussion/comment/57826#Comment_57826

Do I have to contact Logos Tech? Or will they investigate based on this post?

Yes they will - so let's give them a day before discussing further options.

George Allakhverdyan

https://community.logos.com/discussion/comment/57810#Comment_57810

We try again. Hopefully these logs are what you are looking for:

2068.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/2068.Logos4Indexer.log:550:0]

Hi thanks for the log, it seems this is a known issue and hasn't been fixed yet, probably an older or corrupted resource file is causing this problem. Please read http://wiki.logos.com/Diagnostic_Logging and attach a log file to this thread to help us narrow down which resource it is.

Edit: I must be somewhere else! I received your log file and passed it to the devs for review, I will let you know as soon as we figure this out.

Raymond Urne

https://community.logos.com/discussion/comment/58252#Comment_58252

Do you want another log file? I thought it was what I had posted. Where can I find that log file?

Edit: My reply was written before I saw your edit.[:)]

George Allakhverdyan

https://community.logos.com/discussion/comment/58260#Comment_58260

Do you want another log file? I thought it was what I had posted. Where can I find that log file?

Edit: My reply was written before I saw your edit.

It looks like you have about 43 corrupted resources... I don't know how this could have happened, but it will probably be pain to go through and erase them all to re-download them from the server. If you really would like to then close Logos 4 and follow these steps:

Open the Logos4Indexer.log file you provided in Notepad and using Ctrl+F type in "Couldn't clone" - each line you find will display the name of the resource. Example:

2009-12-17 01:28:39.2058 6 Error LogosResource Couldn't clone CTitle for 'LLS:1.0.71'; resource will not be indexed.

The location of these resources is

C:\Users\Raymond.SENTERMENIGHET2\AppData\Local\Logos4\Data\njzvac1z.cjt\ResourceManager\

Most of the LLS resources are named LLS_52_0_2_.... instead of LLS:52.0.2 and are located inside \ResourceManager\logos

The rest of them may be scattered throughout the ResourceManager folder. After erasing them run Logos 4 and it should download them.

Edit: Your only other choice would be to get rid of the resource manager folder and have it redownload all of your resources..

Raymond Urne

https://community.logos.com/discussion/comment/58420#Comment_58420

I did what you said. When I ran Logos after deleting the corrupted files Logos crashes at start-up. The first-time indexing starts up again, but I can't see that any files are downloaded.

George Allakhverdyan

https://community.logos.com/discussion/comment/58667#Comment_58667

I did what you said. When I ran Logos after deleting the corrupted files Logos crashes at start-up. The first-time indexing starts up again, but I can't see that any files are downloaded.

Can you post the new log?

Raymond Urne

https://community.logos.com/discussion/comment/58669#Comment_58669

3817.Logos4Indexer.log

George Allakhverdyan

https://community.logos.com/discussion/comment/58674#Comment_58674

3817.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/3817.Logos4Indexer.log:550:0]

Sorry I should have mentioned the indexer and Logos 4 are separate processes, so if the indexer did not crash then I would just need the Logos4.log to see why it failed this time.

Raymond Urne

https://community.logos.com/discussion/comment/58703#Comment_58703

We try again. Is this what you mean?

3782.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/3782.Logos4.log:550:0]

Raymond Urne

https://community.logos.com/discussion/comment/58749#Comment_58749

Now I think that the problem is solved for a while (I still experience some unexpected crashes or shut-downs).

I did what George told me to: I deleted all the files that seemed to be corrupted according to the LogosIndexer log. When I lauched logos after that, it failed during start-up. But the first-time indexing started and finished without problems. Then I restored the deleted files from the trashcan (maybe they where not corrupted?), and Logos started successfully and the library was indexed.

Thanks!

George Allakhverdyan

https://community.logos.com/discussion/comment/58749#Comment_58749

We try again. Is this what you mean?

3782.Logos4.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/3782.Logos4.log:550:0]

It seems the log file isn't showing enough information. Please save this file http://downloads.logos.com/LBS4/LDLS4Installer/EnableLogging.js and run it and it should say logging enabled. Then reproduce the issue and then attach the new logs (both Logos4.log and the Logos4Indexer.log). Just to clarify, the indexer didn't crash correct?

Edit: Hmm that is good news though I'm glad it's working, and maybe they weren't corrupt after all. Please though if you do experience another crash, do the diagnostic logging again and save the log after reproducing the crash, and attach it to a new thread, it would greatly help us wrinkle out all the bugs. Thanks.