ATTN: "Preparing your library" on next sign in

We just pushed out updated licenses to all beta testers; the next time you sign in, you will need to go through "Preparing your library" while the system scans for unlocked resources.

More information: http://community.logos.com/forums/p/1845/14257.aspx#14257

Find more posts tagged with

Performance

Comments

Simon’s Brother

This has now been running for 4 hours on the first stage of the indexing. Lookig at the log files it seems to be have runnin on three of those on the New Dictionary of Theology returning a multitude of errors similar to :

Error Sinai.TopicIndex Article 105 for topic �¢Қ�£ is out of scrolling range

I had major issues trying to get a copy of the log files. I don't know whether it was the constant writing to it by the indexer with all the errors or it had grown to large or a lock on the file, but it crashed windows explorer when I tried to open it just recently and same result when I tried to compress it. Result was I had to kill Logos4.exe - as there is no way to gracefully exit from the program - pausing indexing did not solve the problem. This however did not shut down the indexer it kept running So I then had to kill it.... and I could now open the log and compress it. Problem now is all the data from the last few hours was missing out the of the indexer log and it only contained recent entires... Fortunately I had made a copy of the log a few hours ago that showed when this resource was started to be prepared for indexeing and it incudes the first hour or so worth of errors log againist it. So I am attachng two sets of logs.

I had trouble getting the logs to upload directly here so have posted to mega upload:

http://www.megaupload.com/?d=GOA1OBZF (Log 3:15PM)

http://www.megaupload.com/?d=PYKA7CN0 (Log 5:56PM)

Dave Hooton

Bradley,

Am I immune with Use Internet = NO?

Robert

https://community.logos.com/discussion/comment/14384#Comment_14384

Is there a way around this and future Beta updates? I am looking forward to updating, and its not that I am trying to avoid testing these betas. It's just that I am generally spending around 2 days updating (and losing my computer during the update) for 1 day of actually using L4.

I would like to take a break from updating and have time to actually use the program for a while.

Rob

Simon’s Brother

https://community.logos.com/discussion/comment/14397#Comment_14397

I am sharing your pain on that one Rob....just when I think I'm about to get into the application along comes another update that usually causes a problem and its basically one-two days later before I'm back on my feet.

Dave Hooton

https://community.logos.com/discussion/comment/14401#Comment_14401

Hey Guys, check my question above + http://community.logos.com/forums/p/1274/10684.aspx#10684

How do you think I avoided all your pain whilst protecting my download limit for the month!!

The Beta software is only 24MB and 1 re-index. The resource updates are the killer.

Edit: it pays to be around when the software updates as I still had to cancel a "suspicious" update after B3 installed! But I don't get anything in-between.

Robert

https://community.logos.com/discussion/comment/14410#Comment_14410

I also have internet use unchecked to avoid as many of these slowdowns as possible. I will find out tomorrow morning if this will avoid the update and I will get to use libronix during the weekend (when I have time to play around more), or if it will be out of commission for the time I am off.

It seems from your other question that it should help.

Simon’s Brother

https://community.logos.com/discussion/comment/14410#Comment_14410

Hey Guys, check my question above + http://community.logos.com/forums/p/1274/10684.aspx#10684

How do you think I avoided all your pain whilst protecting my download limit for the month!!

The Beta software is only 24MB and 1 re-index. The resource updates are the killer.

Edit: it pays to be around when the software updates as I still had to cancel a "suspicious" update after B3 installed! But I don't get anything in-between.

In this case the pain seems to be caused by an lbx file last updated in 2003. Prevously , beta 1, I had removed all lbx files prior to 2006 out of c drive as advised by Logos... however they have not changed so that drives besides c would also be scanned..so now this file was attempted to be processed and failed miserably.. Bradley advises b4 will handle these older file better... so why make the change to scan other drives when using other drives was out saftey net for these potentail indexing killers before putting in place the code that would handle these files much more gracefully than it currently is doing ???? Perplexing to say the least as are a lot of other decisions surrounding L4.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/14384#Comment_14384

Am I immune with Use Internet = NO?

As you probably already figured out: yes.

Dave Hooton

https://community.logos.com/discussion/comment/14421#Comment_14421

In this case the pain seems to be caused by an lbx file last updated in 2003.

I had about 3 problems during Indexing for all Beta's, none connected with resources and easily fixed. But then I only have about 1/10 of your resources!

I also understood that all my L3 resource paths would be scanned (I have two on different drives), so if I had to hide any I would have put them outside these paths.

Simon’s Brother

https://community.logos.com/discussion/comment/14443#Comment_14443

In this case the pain seems to be caused by an lbx file last updated in 2003.

I also understood that all my L3 resource paths would be scanned (I have two on different drives), so if I had to hide any I would have put them outside these paths.

This goes against what Bob advised me early on in the beta project when I asked as to whether or not I would need to re-install LL2.0 to work with the LLS files. He said no they would work fine in L3.. Clearly now this is nto the case as L4 is trying to read them and indexing is getting screwed up as a result. So now I am goign to have to think about diggin out my LL2 install disks if I want to access any of those resources in the short term.

Simon’s Brother

https://community.logos.com/discussion/comment/14351#Comment_14351

blank

Ebbe Andréasson

We just pushed out updated licenses to all beta testers; the next time you sign in, you will need to go through "Preparing your library" while the system scans for unlocked resources.

Thank You!

Now I have all my swedish bibles and will live with limmitations in navigation for a while. Indexing work smothly this and previous time.

Dave Hooton

https://community.logos.com/discussion/comment/14517#Comment_14517

This goes against what Bob advised me early on in the beta project when I asked as to whether or not I would need to re-install LL2.0 to work with the LLS files. He said no they would work fine in L3.. Clearly now this is nto the case as L4 is trying to read them and indexing is getting screwed up as a result. So now I am goign to have to think about diggin out my LL2 install disks if I want to access any of those resources in the short term.

This is confusing.. let me attempt to unravel the consequences for L4.

The PBB files in my L3 paths were ignored and I would have expected LLS
files (lix,lsf) also to be ignored by L4 - at least they would have still
been accessible to L3. So now it looks like you have to sacrifice LLS
files by putting them outside your L3 paths**! If you then re-install
the old LLS2.x software L3 will pick up the resource paths and recreate
the problem with L4 accessing them! So why are you thinking about digging out your old install disks?

** some guys were saying L4 never looked beyond their first L3 path but that wasn't consistently true and Bradley insisted all L3 paths were scanned.

Simon’s Brother

https://community.logos.com/discussion/comment/14583#Comment_14583

This goes against what Bob advised me early on in the beta project when I asked as to whether or not I would need to re-install LL2.0 to work with the LLS files. He said no they would work fine in L3.. Clearly now this is nto the case as L4 is trying to read them and indexing is getting screwed up as a result. So now I am goign to have to think about diggin out my LL2 install disks if I want to access any of those resources in the short term.

This is confusing.. let me attempt to unravel the consequences for L4.

The PBB files in my L3 paths were ignored and I would have expected LLS files (lix,lsf) also to be ignored by L4 - at least they would have still been accessible to L3. So now it looks like you have to sacrifice LLS files by putting them outside your L3 paths**! If you then re-install the old LLS2.x software L3 will pick up the resource paths and recreate the problem with L4 accessing them! So why are you thinking about digging out your old install disks?

** some guys were saying L4 never looked beyond their first L3 path but that wasn't consistently true and Bradley insisted all L3 paths were scanned.

Because they would be isntalled under Logos Library System 2 and these pathers would not be under the L3 library paths..L3 only looks to LL2 for license files to my knowledge...but maybe that knowledge is faulty is very difficult to keep up with anything and get a clear picture on anything on these forums at the moment because instead of having clear guidlines posted in the one place by Logos staff when problem come up they are just ad hoc repsones to posts and none of testers I would think have the time to read every post, digest it and work out what it means in practice as to what we should and should not do, and what behaviours we should expect under what circumstances.

Damian McGrath

https://community.logos.com/discussion/comment/14640#Comment_14640

Andrew,

Your frustrations are palpable. My sympathies.

I only have one LLS file - Oxford Bible Commentary and it has indexed without a hitch. There must be a surer way for the program (programmers) to determine which files will cause the program mild heartburn and which will lead to spontaneous combustion and thus eliminate the latter from the indexing.

Are all your files up to date - having checked the logos and galaxie ftp servers?

Simon’s Brother

https://community.logos.com/discussion/comment/14641#Comment_14641

Andrew,

Your frustrations are palpable. My sympathies.

I only have one LLS file - Oxford Bible Commentary and it has indexed without a hitch. There must be a surer way for the program (programmers) to determine which files will cause the program mild heartburn and which will lead to spontaneous combustion and thus eliminate the latter from the indexing.

Are all your files up to date - having checked the logos and galaxie ftp servers?

Yea run updates regulary, I have Oxford also but am not willing to put anything in there at this point prior to Feb 2006.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/14648#Comment_14648

Yea run updates regulary, I have Oxford also but am not willing to put anything in there at this point prior to Feb 2006.

I don't know, but I have never removed any files and I have quite a number of them prior 2006 (many from 2002) and I have had no problems with them.

Simon’s Brother

https://community.logos.com/discussion/comment/14651#Comment_14651

A lot of them will probably be ok but I am going by what Logos has advised as they have not optimzied all of these resources for L4 and I am having massive problems getting indexing to complete in any reasonable time frame.