Another Crash with L5 ... Apple Report but logs not working

L5 crashed.

I have attached the contents of the report to Apple.

I have also zipped the log folder ... but fear that it will not be of much use since L5 has suddenly stopped logging (after a previous crash). I have followed the Wiki instructions as to starting logging but this seems to have had no effect.

I am assuming that the Logs are still in a path with Logos 4 ... just using a different filename. The time stamps on these have not changed since yesterday. Maybe the logs will suggest why the logging has stopped.

The indexer also crashed and disappeared from the menu.

4606.Report to Apple.txt

7282.Logging.zip

Find more posts tagged with

Comments

Jack Caviness

L5 has suddenly stopped logging

Use KS4J's little applescript (don't know if it works on 10.8) 6403.Logos Log Scribe R2.zip

Also 6403.Logos Log Scribe R2.zip will gather logs and create an archive on your desktop—still works with L5

Martin Folley

https://community.logos.com/discussion/comment/417620#Comment_417620

Thanks Jack.

Martin Folley

https://community.logos.com/discussion/comment/417863#Comment_417863

Still no logging with the indexer. I had to wait for something free in Vyrso ... which is currently 20% complete ... but the indexer log remains dated from the 4th November.

There are two files in logging that are being updated, Console Messages and Logos Errors, updated yesterday (5th).

The console log includes, towards the end, two messages about logging but I have no idea if they are relevant.

Nov 5 11:42:34 server.local SubmitDiagInfo[3046] <Notice>: Removed expired file file://localhost/Users/Martin/Library/Logs/DiagnosticReports/PluginProcess_2012-10-06-091248_server.crash

Nov 5 11:42:34 server.local SubmitDiagInfo[3046] <Notice>: Removed expired plist file file://localhost/Users/Martin/Library/Logs/DiagnosticReports/.PluginProcess_2012-10-06-091248_server.crash.plist

Should there be an Indexer Log file under L5?

Jack Caviness

https://community.logos.com/discussion/comment/418682#Comment_418682

Should there be an Indexer Log file under L5?

Are you looking in the correct folder?

Indexer should run—at least briefly—every time you restart L5. Logos 4 is in the path because Logos could not rename the folder without replacing all its contents. They did not want that massive download for each customer.

Martin Folley

https://community.logos.com/discussion/comment/418738#Comment_418738

It is the same path as under L4.

I had a shortcut on my desktop (from L4 Beta Testing) ... some of the logs were showing L5 errors (at least on Sunday when I first installed L5).

The path is the same but some of the filenames are different under L5 ...

Jack Caviness

https://community.logos.com/discussion/comment/418857#Comment_418857

The path is the same but some of the filenames are different under L5 ...

I waited about two weeks, then deleted the ones that had not been modified since L5 beta was installed.

Thomas Ball

https://community.logos.com/discussion/comment/418886#Comment_418886

Hello Martin,

If Logso 5 is still crashing can you post updated logs immediately after the crash? Logos 5 logging instructions: Logos 5 Diagnostic Logging for Mac - Logos Bible Software