BETA 3: REPEATED CRASH ON STARTUP - 2 COMPUTERS
I am dead in the water - both systems I have crash immmediately on startup every time. Attached are logs from one of the systems. HELP!!
Comments
-
WARNING: BEWARE WITH BETA 3!!!!
I tried signing on with a Blank layout (I normally start with Home Page), and it came up fine. I brought up the Library, I clicked Resources because I have resource to download, and it crashed again.
0 -
I started in Offline mode, I was able to bring up library, go to Collections and bring up a collection definition, bring up a Bible, click on about 3 resource from library to open them, all fine. I was beginning to think it was connected to the network/servers. Then I clicked and opened a layout, CRASH.
0 -
Dominick Sela said:
WARNING: BEWARE WITH BETA 3!!!!
Apologies: my initial launch of Logos 4.5b Beta 3 is OK (Home Page appeared); currently waiting for indexing to complete.
Noticed my Logos4error.log on Mac and PC has messages for http://internal.services.logos.com
Keep Smiling [:)]
0 -
Do you happen to use OpenDNS.com's DNS servers?
If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
0 -
Bradley Grainger said:
Do you happen to use OpenDNS.com's DNS servers?
If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
Bradley, I'm a college student that uses campus internet. I don't know what they use. But check this out. Beta 2 ran smooth all day. Beta 3 is crashing over and over right after I updated to it. Doesn't matter now, I' already deleted and in the process of reinstalling a stable version. I'm busy with homework tonight and Beta 3 put a stop to it.
0 -
Matthew Hamrick said:
Doesn't matter now, I' already deleted and in the process of reinstalling a stable version.
As per the beta testing information page, beta releases can't be downgraded to a stable release. (It may work, or it may crash at startup.)
If it doesn't work, and you have to re-upgrade to Beta 3, try following these instructions to configure your computer to use Google's DNS servers: http://code.google.com/speed/public-dns/docs/using.html, or these instructions with pictures: http://techie-buzz.com/how-to/google-public-dns-on-win7-and-winxp.html
(Since I'm not on your campus network, I can't say for sure that it'll fix the problem, but I think that it may work around it until Beta 4 is released.)
A final alternative is to hold down CTRL at startup and click the Work Offline button. This should stop the crash, even if changing DNS servers doesn't.
0 -
I happen to use OpenDNS and do not want to repeat the crashes of others. I have not installed Beta 3 although it downloaded automatically. Is there any way to delete the downloaded upgrade, and just stay with Beta 2 until beta 4 comes around.
0 -
Bradley Grainger said:
If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
Switching to 8.8.8.8 for DNS would not solve name resolution messages:
C:\>nslookup internal.services.logos.com 8.8.8.8Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find internal.server.logos.com: Non-existent domain
Note: can resolve address for services.logos.com
Keep Smiling [:)]
0 -
Thanks for the thread.I am not somewhere that I can afford a full download or to wait for a Beta to be patched. I'll hold off till I know the risk. I was downloading it but cancelled before it was complete.
0 -
Here also beta3 crashes. It isn't a nameserver problem. I have tried the nameservers of my internetprovider AND the OpenDNS nameservers, and in each case Beta3 crashes.
I was using OpenDNS and Beta3 did crash. After changing the nameservers to my internetproviders default nameservers AND restarting Windows, Beta3 works just fine.
0 -
Dominick Sela said:
WARNING: BEWARE WITH BETA 3!!!!
Thanks for the warning, Dominick! I'm holding off on downloading Beta 3 until this problem is fixed and another beta comes out without any crashing disasters reported in the first day of use.
0 -
-
-
Bradley Grainger said:
Do you happen to use OpenDNS.com's DNS servers?
If so, try switching back to your ISP's servers, or Google's public DNS (8.8.8.8) and see if that works around the problem.
Yes I do use OpenDNS. I changed to using Google's DNS servers temporarily and I ran it through some tests and it did not crash. That seems to be the problem!
Bradley, is there an issue with Logos and OpenDNS? I did not realize this may be a problem, I have noticed for quite awhile that response from Logos web site, is a lot slower than other sites. I just chalked it up to being across the country, some sort of Internet congestion etc., since no one else mentioned it. But now I wonder...?
0 -
0
-
Wish I would have read this before I installed the update.
Crashing here too. It crashes consistently on trying to save or load a layout. (sorry didn't save any logs)
It just crashed on cycling through some study Bibles. Here are all the recent logs for that crash (including setup logs, in case they give any help - sure would be nice if the forum software allowed for more than one file to be selected at a time).
4555.DigitalLibraryInstall.log
EDIT: I did not do anything to alter the DNS (never heard of "Open DNS" before this thread) and have no idea what DNS server my ISP uses.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Dominick Sela said:
Bradley, is there an issue with Logos and OpenDNS? I did not realize this may be a problem, I have noticed for quite awhile that response from Logos web site, is a lot slower than other sites. I just chalked it up to being across the country, some sort of Internet congestion etc., since no one else mentioned it. But now I wonder...?
The bug is that we shipped a component in the beta that attempts to communicate with internal.services.logos.com. (This component was supposed to be disabled, since it's not ready for testing yet; however, it accidentally shipped in a semi-enabled state.)
When OpenDNS is queried for a server that doesn't exist, it returns the address of one of their own servers. (Try it! Go to http://internal.services.logos.com/ in your browser if you're using OpenDNS.) This behaviour is a little questionable, because we own the "logos.com" domain, and if we wanted that subdomain name to fail to resolve, that should be our choice. (They probably do it so they can sell ads for mistyped URLs and support the free service. It should also be noted that some major ISPs are doing this, too, although it may only be for mistyped top-level domains, not subdomains.)
Anyway, the request for internal.services.logos.com "succeeds", and our client is redirected through a series of pages to the advertising landing page you see in your browser. One of these sites tries to set a cookie (for opendns.com). Our client still thinks it's talking to logos.com, so the opendns.com cookie can't be loaded correctly (and the .NET Framework throws an exception that crashes the app).
Other than that, there shouldn't be any incompatibility between OpenDNS and Logos. DNS simply exists to turn a name (www.logos.com) into a numeric IP address (216.57.209.226). This should take a few milliseconds. Once that happens, all communications are "direct" to our server and OpenDNS is no longer involved. ("Direct", of course, meaning that the request from your browser to our site has to go through your ISP, some national network, then through our upstream provider.) It seems very unlikely to me that OpenDNS would be specifically making logos.com (or any other particular site) slower without affecting everything.
0 -
Richard DeRuiter said:
Crashing here too. It crashes consistently on trying to save or load a layout. (sorry didn't save any logs)
This crash appears to be unrelated to OpenDNS; can you please start a new thread and post the crash log there? (That will make it easier for Testing to respond to your issue individually.)
0 -
Suggestion: This is the second problem in about a week or so that has only manifested to people outside of Logos's intranet walls (the other being the wiki and topics.logos.com being down from users' perspective, but worked fine internally). I suggest that before any beta is released onto the beta channel, thus disrupting the lives of many hapless beta testers, it be tested on a computer that is connecting to Logos servers via the Internet not internally. Might need to develop a way of installing it manually via DVD's then, in order to avoid having to push it out to the beta channel to get it onto the test computer. Completely broken betas happen all too often. I do understand that beta testing involves risk, but dead-in-the-water from startup should not happen in a beta version. That's alpha type behavior.
0 -
Bradley Grainger said:Richard DeRuiter said:
Crashing here too. It crashes consistently on trying to save or load a layout. (sorry didn't save any logs)
This crash appears to be unrelated to OpenDNS; can you please start a new thread and post the crash log there? (That will make it easier for Testing to respond to your issue individually.)
Done.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Dominick Sela said:
I am dead in the water - both systems I have crash immmediately on startup every time. Attached are logs from one of the systems. HELP!!
I'm having the exact same problem. I've attached my log files. This is a real bummer...today is my message prep day. Note to self: always read the Beta Forum first. [:@]
0 -
Jeff Loven said:
today is my message prep day. Note to self: always read the Beta Forum first.
The same situation, plus I go to the Bible School to teach from Monday[:(] on... I hope we will see a new Beta till then.
Bohuslav
0 -
Jeff Loven said:
I'm having the exact same problem.
Try following these instructions to configure your computer to use Google's DNS servers: http://code.google.com/speed/public-dns/docs/using.html, or these instructions with pictures: http://techie-buzz.com/how-to/google-public-dns-on-win7-and-winxp.html
Or, if you select Obtain DNS server address automatically in those dialogs, you should use your ISP's default servers, which should also avoid the crash.
Another alternative is to hold down CTRL at startup and click the Work Offline button. This should stop the crash, even if changing DNS servers doesn't.
0
