L5 will NOT start!

I have never had this happen. L5 for Mac will not start. I get the "sign in" box but that is all! I have done a disk permission and a disk repair (both of which did find problems but were corrected). Using boot camp I checked L5 for Windows which boots fine! Not sure what happened on the Mac side! Any help?

Reinstalled L5 for Mac (dmg file) and tried again=NO GO!

Logs attached

5367.LogosLogs.rcdeacon.20131124-064722.zip

Find more posts tagged with

Comments

Jack Caviness

Found the following error in your Logos.log—

'/Users/rcdeacon/Library/Application Support/Logos4/Documents/d8m8u31f.fwz/LayoutManager/layouts.db'. ~SQLiteException: database disk image is malformed

Perhaps deleting the layouts.db and allowing Logos to rebuild will correct the problem. I say perhaps, because I am still an amateur at log reading.

As as aside, with Logs shut down, perhaps you can clear your logging folder. It contains a multitude of old log files.

Bob Deacon

https://community.logos.com/discussion/comment/545574#Comment_545574

OK Jack, you win the "you're the man" award for this Sunday November 24th! That is exactly what the problem was and I am up and running again! Thanks for the help!

Bob

Patrick S.

https://community.logos.com/discussion/comment/545574#Comment_545574

Found the following error in your Logos.log—

~ SQLiteException: database disk image is malformed

~ deleting the layouts.db and allowing Logos to rebuild will correct the problem.

One wonders if this sort of thing (health checking of critical files) which obviously happens when Logos starts up could be advised to the user in a user friendly type of message...

"There appears to be a problem with one of your Logos system files [layouts.db] which is stopping Logos from starting. Would you like the file corrected?" Yes | No

so the user's install could be automatically cleaned up so they could work.

Given that it seems the file(s) can be removed and automatically rebuilt with no ill effect to the Logos application it seems it would be a helpful user functionality to include.

Lee

https://community.logos.com/discussion/comment/545594#Comment_545594

Another terrific user suggestion.

Jack Caviness

https://community.logos.com/discussion/comment/545580#Comment_545580

OK Jack, you win the "you're the man" award for this Sunday November 24th! That is exactly what the problem was and I am up and running again! Thanks for the help!

I was a bit hesitant about giving that advice since reading logs is a new experience. Supremely pleased that it worked for you.

Jack Caviness

https://community.logos.com/discussion/comment/545594#Comment_545594

One wonders if this sort of thing (health checking of critical files) which obviously happens when Logos starts up could be advised to the user in a user friendly type of message...

"There appears to be a problem with one of your Logos system files [layouts.db] which is stopping Logos from starting. Would you like the file corrected?" Yes | No

so the user's install could be automatically cleaned up so they could work.

Given that it seems the file(s) can be removed and automatically rebuilt with no ill effect to the Logos application it seems it would be a helpful user functionality to include.

You may be onto something good here. Sounds like an excellent suggestion. Perhaps you could post this in the Suggestions forum, or send a message to suggestion@logos.com

Dave Hooton

https://community.logos.com/discussion/comment/545594#Comment_545594

One wonders if this sort of thing (health checking of critical files) which obviously happens when Logos starts up could be advised to the user in a user friendly type of message...

Logos is not performing a health check as much as establishing that the data structure it needs is intact e.g. "Found existing database ..." messages. Corruption is not always evident until the database is actually read, and then the ability to deal with and recognise the culprit can be buried by system default actions. I would certainly urge Logos to identify the culprit when logging the error, as automatically correcting it can be complicated because of inter-dependencies and could even result in data loss. Their attempt at automatically fixing indexing errors hasn't been encouraging.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/545628#Comment_545628

Given that it seems the file(s) can be removed and automatically rebuilt with no ill effect to the Logos application it seems it would be a helpful user functionality to include.

You may be onto something good here. Sounds like an excellent suggestion. Perhaps you could post this in the Suggestions forum, or send a message to suggestion@logos.com

No need to post it in Suggestions; we're already aware of this idea.