L6 (6.0.1.0032) Crashes on startup with Diagnostic Logging enabled (start fine with it disabled)
L6 (6.0.1.0032) Crashes on startup with Diagnostic Logging enabled. I am having crashes consistently with another feature, but cannot adequately report on the problem because when I enable Logging (through command line or through key combos or through Logos Logging Utility) it crashes. I am starting a new thread for the other problem to which the automatic response is "send us logs."
I have done a very time consuming clean install and first index (28 GB of download - over 7000 books).
I have manually rebuilt the index.
I am running Yosemite 10.10.1 on this:
Any suggestions? Other than, can you first send us logs...
Comments
-
Jeffrey S. Robison said:
Any suggestions? Other than, can you first send us logs...
Not really (I'm a PC guy). But: When crashing, Logos writes logs even when Diagnostic Logging wasn't rurned on - which might help with the other problem, too. And your Mac OS should write a lot of logging information (other users spammed several screen pages by pasting this into forum posts) - more Mac-savvy users may be able to tell you where to find that stuff.
An alternative is to have Logos Technical Support log on to your machine from remote.
Have joy in the Lord!
0 -
When you start with command key held down, does the sign in dialog display before the crash? Can you start it in offline mode if it does?
0 -
Starts from login screen in offline. Command button has to be pressed just after you click to start app. Still has other crash. grabbed logs.
0 -
I grabbed a copy of your uploaded file before everything went wonky over the weekend on Logos servers:
7802.3568.LogosLogs.jeffreyrobison.20141122-095251.zip
Unfortunately, it only contains the "Console Message.log" file. It looks like you went through the proper procedure to enable logging, if you saw the login screen. I'm bumping this back up so that, hopefully, a mac expert can assist.
0 -
Randy W. Sims said:
I grabbed a copy of your uploaded file before everything went wonky over the weekend on Logos servers:
Any update on wonky servers?
0 -
Jeffrey S. Robison said:
Starts from login screen in offline. Command button has to be pressed just after you click to start app. Still has other crash. grabbed logs.
Can you check the permissions on your logging folder, is should be located at Users/jeffreyrobison/Library/Application Support/Logos4/Logging? It appears that both the crash when running with logging enabled and building a PBB may be the result of incorrect permissions.
Mac Developer
Faithlife0 -
What do the permissions need to be for the Logos4 folder and sub-folders?
0 -
Jeffrey S. Robison said:
What do the permissions need to be for the Logos4 folder and sub-folders?
The default permissions for you Home folder, which includes ~/Library/Application Support/Logos4, should be 755. This means that your user has read/write/execute permissions and your group/everyone else have read/execute. If you are unfamiliar with Terminal, you can select Get Info on the folder, then under the Sharing & Permissions section you should see that you have Read & Write, your group has Read only and everyone has Read only.
Mac Developer
Faithlife0 -
Logos4 folder and all in it need to be 644 instead of 755???
0 -
Jeffrey S. Robison said:
Logos4 folder and all in it need to be 644 instead of 755???
The basic options that are displayed in the GUI when you use "Get Info" does not display the execute option.
If you know how to set them via Terminal, they should be set to 755.
Mac Developer
Faithlife0 -
Thanks Martin. I can set it in terminal. Is it 755 for everything in the subfolders as well?
0 -
Jeffrey S. Robison said:
Thanks Martin. I can set it in terminal. Is it 755 for everything in the subfolders as well?
Yes, it should be 755 for Logos4 and all its subfolders. Once the permissions have been updated, if it is still crashing, please post your logs from building your PBB (the current crash is related to being unable to create the log file for building).
Mac Developer
Faithlife0 -
Changed to 755. Logging folder did not add my user to permissions. System was owner. Continued to crash. I added my user ID to Logging folder and gave Read Write permissions and it created logs and let me build PBs.
Thanks Martin. Any idea why my user was not added to Logging folder? Is that a 10.10.1 issue?
0 -
Martin Potter said:Jeffrey S. Robison said:
Starts from login screen in offline. Command button has to be pressed just after you click to start app. Still has other crash. grabbed logs.
Can you check the permissions on your logging folder, is should be located at Users/jeffreyrobison/Library/Application Support/Logos4/Logging? It appears that both the crash when running with logging enabled and building a PBB may be the result of incorrect permissions.
Had exact same problem.
I had downloaded Logging Utility yesterday just for fun. Logos (for quite a while now has run really slow on my computer and I wanted to try figure out why. Extensive reading yesterday on the forums indicate maybe it is Hebrew that has been the problem.)
Today when I tried to restart Logos it continued to crash on startup. I was on Mac OS 10.10 at the time. Wondering if it might be OS related (Yosemite is full of bugs!) I upgraded to 10.10.2 but Logos continued to crash on startup.
Providentially, this was the first link that came up when I googled the problem. Disabled logging, and it started normally. I checked the ~/Library/Application Support/Logos4/Logging folder and sure enough the system has Read & Write, everyone else has Custom.
Changed my user permissions to "Read & Write", re-enabled logging, and Logos started fine.
This needs to be fixed, as others may get this problem and be unable to quickly diagnose it as I was, if they are unable to find this page.
Currently running Mac OS 10.10.2 and Logos 6.0.2.0075.
2009 27" iMac 2.8GHz 8GB RAM
It probably should be noted that I use my computer on a standard (non-admin) account for security reasons, although of course I have the administrator details when required.
0
