Missing resources

Hi! I've just downloaded and installed Logos 4, and I'm very impressed! However, I have encountered a few problems. (I'm running OSX 6.4, though I'm currently in the process of upgrading to 6.8, which should then allow me to buy and install OSX Lion.)

Firstly, indexing didn't occur automatically. I had to type "rebuild index" to start indexing, and it took only 15 minutes to index my resources.

That brings me to my second problem. I purchased the Catholic Library Builder, which contains 238 books. But it seems only 63 are installed.

The wireless network I'm on isn't always user-friendly. For example, security protocols prevent me from accessing the iTunes store. It often seems the only internet access available is via the browser, which prompts a request for my network name and password without any problem. Other applications don't allow me to enter that data, and so internet access is denied. Could this be contributing to my problems with Logos?

6648.Logos4.log

Find more posts tagged with

Comments

JT (alabama24)

John - FIrst, welcome to the forums! I am not a techie, so I will let someone else look at your logs.

I purchased the Catholic Library Builder, which contains 238 books. But it seems only 63 are installed.

I do not have this resource, but I read somewhere that some of the books are being completed and are not ready for download yet. If you only have 63 resources, I wouldn't expect it to take too long to index, but 15 minutes does sound short.

Keep Smiling 4 Jesus :)

The wireless network I'm on isn't always user-friendly. For example, security protocols prevent me from accessing the iTunes store. It often seems the only internet access available is via the browser, which prompts a request for my network name and password without any problem. Other applications don't allow me to enter that data, and so internet access is denied. Could this be contributing to my problems with Logos?

Welcome [:D]

Network proxy can interfere with Logos downloads and sync.

Would like to look at diagnostic logging for Indexer, which downloads resource file(s). The attached Logos4.log file shows Logos 4 Indexer did not have logging enabled,

Wiki Mac Troubleshooting => How to Report Bugs in Logos 4 Mac includes link to 5504.Logos4MacLogging.app.zip (display logging setting, then optionally change); also links to Logos Log Scribe (create zip file of Logging folder with copy of console messages)

Other option is contacting Logos Mac Support => http://www.logos.com/about/contact With your permission, Logos can connect with desktop sharing (if proxy permits).

Keep Smiling [:)]

John Corrigan

https://community.logos.com/discussion/comment/299794#Comment_299794

Thanks guys. I've installed the logging app and attached the resulting logs.

4064.Indexer.log

3326.Logos4.log

Jon

https://community.logos.com/discussion/comment/299800#Comment_299800

Looking at the logs, It looks like you didn't give it long enough to download all the books...

At 19:04:30 it starts downloading 102 resources, then at 19:05:53 you run rebuild index which restarts the indexer process.

John Corrigan

https://community.logos.com/discussion/comment/299851#Comment_299851

Oops. Good point Jon.

How significant is it, that the Logos icon disappears from the menu bar? The logs make it clear that things are still happening, even though the icon disappears.

I re-installed this morning. I noticed that the "Downloading Resources" dialogue informed I was downloading a whole 131.8 KB, though it was clearly more than this because it took some time. The progress bar did some funny things. It would reach 6000% then drop back to 10%, progress up to 800% and drop back to 12%, and so on, reaching a peak of 11,000% towards the end.

Since then, I have left the program open for four hours, and attach the logs below. Despite the reports of downloading activity, I still have only the 63 books which are downloaded at the time of installation.

8623.Indexer.log

74862.Logos4.log

Perhaps the only answer is to try a different network.

John Corrigan

https://community.logos.com/discussion/comment/300099#Comment_300099

Yep. It all came down to an over-zealous firewall.