Logos down ... again.

Well we seem to have been down ... again. Although most of Faithlife seems to be accessible my Logos program still can't log in so that I am working off-line. Hopefully that helps persuade everyone that we are in not in any position to go all 'online' in the foreseeable future. Or is my pessimism is showing!

Find more posts tagged with

Comments

Floyd Johnson

Well we seem to have been down ... again. Although most of Faithlife seems to be accessible my Logos program still can't log in so that I am working off-line. Hopefully that helps persuade everyone that we are in not in any position to go all 'online' in the foreseeable future. Or is my pessimism is showing!

Yes

Erwin Stull, Sr.

Well we seem to have been down ... again. Although most of Faithlife seems to be accessible my Logos program still can't log in so that I am working off-line. Hopefully that helps persuade everyone that we are in not in any position to go all 'online' in the foreseeable future. Or is my pessimism is showing!

I've always preferred the offline (local) model over the online (cloud), however the cloud and semi-cloud is where things are going. I will continue to strive to maintain as much control as possible. As far as the outage goes, I didn't experience any login problems, but there was an incident report produced earlier.

Ronald Quick

https://community.logos.com/discussion/comment/778514#Comment_778514

Although I understand that things are moving towards the cloud, I hope Logos continues to function offline.

JT (alabama24)

http://status.faithlife.com

Floyd Johnson

https://community.logos.com/discussion/comment/778519#Comment_778519

http://status.faithlife.com

Martin Folley

https://community.logos.com/discussion/comment/778519#Comment_778519

I am currently online but the sync on my desktop app has a red exclamation mark. The status page says everything is green.

Do you know whether it is an automated site based on tests from an external place, or does it rely on FL staff discovering an issue and updating the page?

Is there a way of troubleshooting 'exclamation' marks? I am not sure if posting logs will do it. I wonder if ping (or something more sophisticated may do it).

@FL: is is possible for the exclamation mark to give a tooltip as to what it thinks is the issue?

Thanks.

JohnB

https://community.logos.com/discussion/comment/778539#Comment_778539

I still can't log in and have to go on off-line. All other services have been OK for over 12 hours.

Martin, that is something I would love to know.

Also who/where do we email if we spot a problem?

alabama24 - I am aware of what the status page states and I lso get the status messages which are great - but frustrating when you know it is not fully solved and FL believe that it is. [:D]

Levi Durfey

https://community.logos.com/discussion/comment/778539#Comment_778539

Is there a way of troubleshooting 'exclamation' marks? I am not sure if posting logs will do it.

The logs will show problems with syncing. I had a red exclamation mark a few months ago that I tracked down to a syncing problem with customdictionaries.db. I deleted the file and fixed it.

Don't assume all syncing problems are on FL's end. It could be a corrupted file that refuses to sync. Logs will help you find that file.

Martin Folley

https://community.logos.com/discussion/comment/778558#Comment_778558

Don't assume all syncing problems are on FL's end. It could be a corrupted file that refuses to sync.

I agree that Logs might sort it ... I forgot to actually attach them [:$] ... but I wonder how a corrupted file would stop syncing completely without notification ... surely there would be error trapping code to inform the user about any such corruption or other issue relating to syncing... which does kind of lay it at the door of FL.

However, I have attached the logs that I forgot to attach earlier ...

3157.LogosLogs.Martin.20151109-122447.zip

JT (alabama24)

https://community.logos.com/discussion/comment/778543#Comment_778543

alabama24 - I am aware of what the status page states and I lso get the status messages which are great - but frustrating when you know it is not fully solved and FL believe that it is.

[Y]

Don't assume all syncing problems are on FL's end. It could be a corrupted file that refuses to sync. Logs will help you find that file.

[Y] Also, Logos doesnt seem to be too "smart" in the sense that if you open the app when things are down, you would need to restart your app to make sure the connection is made again. In some cases restarting your computer might be helpful too.

J
http://status.faithlife.com

Thanks for making that active Floyd. It would not let me do so at the time.

Levi Durfey

https://community.logos.com/discussion/comment/778559#Comment_778559

surely there would be error trapping code to inform the user about any such corruption or other issue relating to syncing... which does kind of lay it at the door of FL.

That's what the logs are for...I am just a novice at looking at logs but I see a lot of prayerlist items associated with sync errors in your LogosError.log. What I did, by the way, is opened the LogosError.log and typed "Sync" in the search box.

I am going to say that if you delete your PrayerList folder from the Logos folder in your Application Support folder, (Quit Logos first) it should fix the problem. Logos will rebuild the folder when you restart.

Floyd Johnson

https://community.logos.com/discussion/comment/778560#Comment_778560

http://status.faithlife.com

Thanks for making that active Floyd. It would not let me do so at the time.

Glad to be of help.

At first I was surprised at the oversight, but then I had quite a time trying to make it active. I assumed, as you stated, that you were having the same problems making it active that I was having.