No Sync or Logos Web

Anthony H
Anthony H Member Posts: 1,155 ✭✭
edited November 2024 in English Forum

Has anyone heard what the deal was last night on no ability to sync the Logos app nor access the website? It started here around 4:30-5:00 and lasted well after midnight.

I'm not going to complain to much...LOL "but" on a Wednesday night, OUCH!

Comments

  • Donnie Hale
    Donnie Hale Member Posts: 2,038 ✭✭✭

    I experienced the problem, too, but I'm not sure how to interpret what I saw. From my laptop in a Hyatt hotel, I could get to anywhere on the internet that I tried *except* any Logos-related site (community.logos.com, www.logos.com, biblia.com, and the sync domain). Best I can tell, the DNS infrastructure for Logos (Fibercloud ???) was having problems - the issue was that the DNS lookups for the Logos domains was timing out.

    What made it more curious was that I could reach the Logos sites from my Blackberry. I thought that it might have just been something very weird with the hotel's connectivity (given that I could reach anyplace else). But if you had similar problems, it must have been a wider outage.

    Donnie

     

  • Anthony H
    Anthony H Member Posts: 1,155 ✭✭


    I experienced the problem, too, but I'm not sure how to interpret what I saw. From my laptop in a Hyatt hotel, I could get to anywhere on the internet that I tried *except* any Logos-related site (community.logos.com, www.logos.com, biblia.com, and the sync domain). Best I can tell, the DNS infrastructure for Logos (Fibercloud ???) was having problems - the issue was that the DNS lookups for the Logos domains was timing out.

    What made it more curious was that I could reach the Logos sites from my Blackberry. I thought that it might have just been something very weird with the hotel's connectivity (given that I could reach anyplace else). But if you had similar problems, it must have been a wider outage.

    Donnie

     


     

    Very interesting. So maybe some bad DNS records got propagated across more than just Fibercloud name servers yet not through the whole distributed NS system.

    May be a few people upset on this one. Sparking another flare-up of "ANTI-CLOUD" computing.

  • TCBlack
    TCBlack Member Posts: 10,980 ✭✭✭

    In the words of colonel Klink, "I know nothing".  But I understand your pain.  :-)

    Hmm Sarcasm is my love language. Obviously I love you. 

  • Anthony H
    Anthony H Member Posts: 1,155 ✭✭


    In the words of colonel Klink, "I know nothing".  But I understand your pain.  :-)


    I have nothing to truly complain about as our service wasn't halted. Truth is that most would agree that we have more issues on a semi frequent basis with a service being interrupted by “other” technical issues than cloud computing by itself would cause. Though the cloud would add one more variable to deal with.

    LOL, "I know nothing".  yes.... wait wasn't it Shultz who said that? [:D]

  • Wes Saad
    Wes Saad Member Posts: 1,601 ✭✭✭

    Looked to me like Fibercloud, a datacenter, went down, which would have taken Logos servers and DNS with it.

  • Donnie Hale
    Donnie Hale Member Posts: 2,038 ✭✭✭

    That's what I was thinking, right up until I could reach stuff from my Blackberry but not my laptop...

    -Donnie

     

  • Mark Watson
    Mark Watson Member Posts: 125 ✭✭

    Kind of makes you wonder what a church would have had for its presentation software last night if they were using the new Logos version of "internet only" church presentation software.

    This is why being "cloud-only" will be the reason I will not purchase some softwares.  Here, with our internet service, we have several hours at a time where the internet in not available at all.  And on a fairly frequent basis.

  • Rich DeRuiter
    Rich DeRuiter MVP Posts: 6,729

    In the words of colonel Klink, "I know nothing".

    That was Sargent Shultz (John Banner).

    Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun.

     Help links: WIKI;  Logos 6 FAQ. (Phil. 2:14, NIV)

  • TCBlack
    TCBlack Member Posts: 10,980 ✭✭✭

    In the words of colonel Klink, "I know nothing".

    That was Sargent Shultz (John Banner).

    Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun.

    Apparently I really "know nuzzing" [:p]

    Hmm Sarcasm is my love language. Obviously I love you. 

  • Rich DeRuiter
    Rich DeRuiter MVP Posts: 6,729

    In the words of colonel Klink, "I know nothing".

    That was Sargent Shultz (John Banner).

    Recently watched the entire Hogan's Heroes series on DVD. Campy, but fun.

    Apparently I really "know nuzzing" Stick out tongue

    Maybe a nice, fresh  [8] 'Shtrooooodle' [8] will help!

     Help links: WIKI;  Logos 6 FAQ. (Phil. 2:14, NIV)

  • Anthony H
    Anthony H Member Posts: 1,155 ✭✭

    How come there was no official word on the event?

  • Mark Watson
    Mark Watson Member Posts: 125 ✭✭

    Anthony H said:


    How come there was no official word on the event?


     

    I second that request.  If Logos is going to continue to go "cloud based" then all problems should be investigated and tracked so that users will have some history of problems and up-time data to know how much risk we may be of being out of service for items especially like the Proclaim software.

  • Bob Pritchett
    Bob Pritchett Member, Logos Employee Posts: 2,280

    Here's the answer. (Summary: It wasn't us. :-) But we are now investigating ways to avoid this particular path and not be at risk here.)

     


     

    Reason for Outage

     

     

     

    Ticket:

     

    Location: Bellingham

     

    Service Impact: DNS
    traffic

     

    Start:       5:45pm     PT                           Date: 01/19/2011

    End:        10:50pm   PT                           Date: 01/19/2011

    Duration:

     

     

     

     

    Trouble Type: Partial
    DNS issue through one upstream provider

     

    Trouble Resolution:

     

     

     

    Overview:

     

    The issue with DNS
    was due to a path problem between one of our upstream providers and our DNS
    servers. This event was not a full outage. All traffic coming through
    FiberCloud’s other upstream providers reached its destination without a
    problem.  Once FiberCloud rerouted traffic from the upstream provider that
    was having the path issue the problem was fixed.

     

    FiberCloud will not
    route traffic back through this provider until they have determined the cause
    and fixed the path issue.

  • (‾◡◝)
    (‾◡◝) Member Posts: 928 ✭✭✭

    Instead of Artificial Intelligence, I prefer to continue to rely on Divine Intelligence instructing my Natural Dullness (Ps 32:8, John 16:13a)

  • Anthony H
    Anthony H Member Posts: 1,155 ✭✭

    I appreciate your responding. I had no doubt you were on top of a solution but rather thought it odd that it wasn't mentioned.

    I would add though that my durration was longer as there was no sync before 5:30pm CT and this outage included Logos.com domains and Bibla which were all offline till after 11:30pm CT.

    I do understand that my longer durration may have more to do with me being further down the "DNS pipeline" and the potential time it takes for the correct record path to propagate through the NS system.

    Thanks for the update.

    Anthony

  • MJ. Smith
    MJ. Smith MVP Posts: 55,539

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Alan Macgregor
    Alan Macgregor Member Posts: 2,438 ✭✭✭

    iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8

    MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8

    iPad Pro 32GB WiFi iOS 13.5.1

    iPhone 8+ 64GB iOS 13.5.1

  • Mark Watson
    Mark Watson Member Posts: 125 ✭✭

    Bob,

    Thank you very much for the response and its detail.  Your honesty is refreshing in today's world.

    God Bless and many continued years of business.