Repeating Crash - Logos Unusable

I left L4 open with a simple layout. On trying to close said layout, L4 crashed. I am now unable to open the programme without it crashing. I am able to open to a blank layout, but as soon as I try and open any resource, L4 crashes again. It is unusable at the moment.

I have attached the logs and wonder if anyone is able to cast any insight into how I may fix this?

I updated yesterday to the latest service release.

Thanks in anticipation.

Andy

65865.Archive.zip

2425.Logos4Crash.txt.zip

Find more posts tagged with

Comments

Andy

Actually, having played around with this problem a little more, I have discovered L4 only crashes when I try and open a bible. All other resources, as far as I can tell, appear to work.

I thought I remember reading about someone encountering a problem where the Bible index/database corrupted. I seem to recall that the fix involved deleting a file and forcing L4 to rebuild.

TCBlack

https://community.logos.com/discussion/comment/371785#Comment_371785

You should be able to fix a broken bible index by typing the following command in the command box:

rebuild bible index

Keep Smiling 4 Jesus :)

I updated yesterday to the latest service release.

Looking at Logos4Crash.txt, the error message "Failed to read past end of stream" is the same as another Logos 4 Mac user; suggest calling Logos Tech Support => http://www.logos.com/about/contact that is in the Logos 4 Windows forum => http://community.logos.com/forums/p/50369/371610.aspx#371610

By the way, the archive file does not have Logos diagnostic logs: Logos4.log and Indexer.log

Optional: download and use 5504.Logos4MacLogging.app.zip to display your logging setting, then change to enable logging.

the applescript application uses the terminal commands in wiki => http://wiki.logos.com/Diagnostic_Logging#Mac

Keep Smiling [:)]

Rick Harrell

Had a similar problem yesterday - contacted tech support and was passed on to level 2 support. The tech (who was patient and persistent and polite) tried a number of things and finally deleted my NIV. Logos runs now, sans NIV. He said he will get back to me when he figures out the problem.

Rick Harrell

https://community.logos.com/discussion/comment/371823#Comment_371823

I like NASB better anyway

Thomas Ball

https://community.logos.com/discussion/comment/371794#Comment_371794

I updated yesterday to the latest service release.

Looking at Logos4Crash.txt, the error message "Failed to read past end of stream" is the same as another Logos 4 Mac user; suggest calling Logos Tech Support => http://www.logos.com/about/contact that is in the Logos 4 Windows forum => http://community.logos.com/forums/p/50369/371610.aspx#371610

By the way, the archive file does not have Logos diagnostic logs: Logos4.log and Indexer.log

Optional: download and use 5504.Logos4MacLogging.app.zip to display your logging setting, then change to enable logging.

the applescript application uses the terminal commands in wiki => http://wiki.logos.com/Diagnostic_Logging#Mac

Keep Smiling

Andy

https://community.logos.com/discussion/comment/371794#Comment_371794

Thanks, everyone, for the assistance.

By the way, the archive file does not have Logos diagnostic logs: Logos4.log and Indexer.log

Apologies, KS4J, I thought I had pressed command on start up in order to initiate diagnostic logging. I used your superb script and have now attached all of the logs available.

I presume, from your response, that 'Rebuild Bible Index' is unlikely to work? Is there anything else you are able to suggest? I am happy to try hiding the NIV, but note that L4 crashes when I attempt to open any bible (or open the home page, which has bible passages embedded).

I will call technical support if there is no other alternative, but with the difference in timezones, this can make things tricky.

Thanks again for you kind assistance.

46046.Archive.zip

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/371901#Comment_371901

I presume, from your response, that 'Rebuild Bible Index' is unlikely to work? Is there anything else you are able to suggest? I am happy to try hiding the NIV, but note that L4 crashes when I attempt to open any bible (or open the home page, which has bible passages embedded).

I will call technical support if there is no other alternative, but with the difference in timezones, this can make things tricky.

Looking at Logos4.log file, noticed error "Failed to read past end of stream" for a media item on the Home Page.

My apologies: personally not know how to resolve "Failed to read past end of stream" error, which has been posted by three Logos 4 Mac users. Suspect Sync Manager is encountering an error while processing a downloaded sync item.

Wonder if can work offline ? possibly a workaround until can connect with Logos Tech Support

Keep Smiling [:)]

Andy

https://community.logos.com/discussion/comment/371903#Comment_371903

Wonder if can work offline ? possibly a workaround until can connect with Logos Tech Support

Thanks for your patience, KS4J.

I have tried working off line, alas, the crash persists.

I will try and call technical support later.

Thank you once again for your assistance. As alway, it is very much appreciated. Have a good day.

Andy

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/371906#Comment_371906

Wonder if crash repeats when open to a blank layout ?

Keep Smiling [:)]

Andy

https://community.logos.com/discussion/comment/371908#Comment_371908

Wonder if crash repeats when open to a blank layout ?

This is the first thing I tried. I am able to open to a blank layout and even able to open resources. As soon as I touch a bible or try to move to the home page, L4 shuts down suddenly and unexpectedly.

Thomas Ball

https://community.logos.com/discussion/comment/371945#Comment_371945

Hi Andy,

I'm going to contact you offline regarding this issue.

Nevermind, it seems you've called us.

Andy

https://community.logos.com/discussion/comment/372051#Comment_372051

Thanks, Tommy. I am about half way through reindexing and am hopeful that this will address the problem.

Thank you again for your assistance.

Paul-C

https://community.logos.com/discussion/comment/372206#Comment_372206

Hi Andy, are you hoping this issue will be resolved by doing a full re-index? Just checking for future reference! Very best of luck with that!

Andy

https://community.logos.com/discussion/comment/372246#Comment_372246

are you hoping this issue will be resolved by doing a full re-index? Just checking for future reference!

Hi Paul,

Just to confirm that rebuilding the index did successfully fix the problem. I do wonder, with hindsight, whether just rebuilding the Bible index would have fixed the problem (as the crash occurred when selecting Bibles).

Very best of luck with that!

It took around 20 hours to reindex 5630 resources on the recent MBA...

I am very pleased to have Logos back and working.

Thank you to the tech team for the excellent customer support.

Paul-C

https://community.logos.com/discussion/comment/372310#Comment_372310

Glad it's all worked out Andy! [Y]

[Deleted User]

https://community.logos.com/discussion/comment/372395#Comment_372395

Mine is repeatedly crashing -- I can open it to a blank document, but it crashes every time that I try to click on any resource or even load the HOME screen.

I am about to just delete and reinstall the whole thing, but it takes so darn long.

[Deleted User]

https://community.logos.com/discussion/comment/372641#Comment_372641

1016.Indexer.log 7762.Logos4Crash.txt 7652.Logos4Error-2.logHere are my logs ... just in case someone has some input.

8321.Logos4Error.log

Andy

https://community.logos.com/discussion/comment/372641#Comment_372641

I am about to just delete and reinstall the whole thing, but it takes so darn long.

Hi Jason,

I am not proficient enough in reading logs to be able to diagnose whether your issues are the same as mine. I thought, however, it was worth clarifying that a complete reindex fixed the issues I was experiencing. I do wonder whether the command, 'rebuild bible index', would have achieved a positive result as the error only occurred when I accessed bibles. This would have taken considerably less time than a complete reindex. Most significantly, I did not need to uninstall/reinstall L4.

I am not advising that you reindex (which will not do any harm, but will take a very long time), but would caution you against taking the drastic step of reinstalling unless you have absolutely no choice whatsoever.

I appreciate that tech support is closed over the weekend, but I am sure they will be able to assist should you be able to wait until Monday.

In summary, I would caution you to only reinstall as a last resort. It may well be that another forum user can make sense of your log files and advise accordingly.

God bless,

Andy

Jack Caviness

https://community.logos.com/discussion/comment/372643#Comment_372643

Jason

I cannot read logese, so I cannot provide any direct assistance. Just wanted to say that you may need to start a new thread and prefix the title with "BUG". That way, you post will get more attention than simply appending your problem to a thread whose problem has been resolved.

JT (alabama24)

https://community.logos.com/discussion/comment/372641#Comment_372641

Jason -

The logs you provided didn't provide much to me, but I am not quite a techie. I think you will need to provide a fresh logos4.log. NOTE: this diagnostic log is not generated automatically unless you have turned on diagnostic logging. You might want to download the script KS4J wrote (link below) which allows you to easily turn logging on & off.

5504.Logos4MacLogging.app.zip

Jack Caviness

https://community.logos.com/discussion/comment/372683#Comment_372683

ou might want to download the script KS4J wrote (link below) which allows you to easily turn logging on & off.

Additionally, you could download Logos Log Scribe which will automate collection and archiving of log files.

Thomas Ball

https://community.logos.com/discussion/comment/372643#Comment_372643

Hi Jason

The indexer log provided does not record a crash. Can you re-record the process, and be sure to allow the indexer to crash before posting the logs? Make sure the log is actually recording the current session as well rather than it being a log from earlier. You can open it up and look at the time-stamp on the left at the very bottom of the log list to make sure.