Connectivity BUG: Reading List in Logos 5.2b Beta 6 doesn't populate
Started to a blank layout (since otherwise the HANG reported elsewhere kicks in), opened a Reading List:
2014-08-02 10:49:26.7424 1 Info PanelViewModel Got panel settings for Preferences: SelectedList=Epistle%20to%20Titus!Logos,%20Community!http://topics.logos.com/Epistle_to_Titus!1
Note that Logos didn't become unresponsive, it just took its time searching for this list (which isn't specific to that list in particular, happens all the time).
I refrained from doing anything in Logos - read the forum, prepared this post, looked into the Logos.log from time to time - and bingo, at 11:23 the list populated.
Logos.log: 3618.Logos.log empty layout & RL.zip
CEF-Log just in case: 5554.cef.log
The logos.log has this ominous web exception warnings for thumbnail pictures (when I click on the URL they show in my browser instantly) and an error for a web exception, but earlier than the call of the RL.
Actually I'm not sure when this issue started - maybe with the re-configurations of Logos' servers that were done to increase connectivity for Proclaim? Or the switch to the CEF internal browser?
This bug nearly prevents me from checking the Reading List features and updating topics.logos.com
Have joy in the Lord! 
Comments
-
I get a different result ... but not the reading list when I request the Verbum Practicum
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."
0 -
I am not able to reproduce this issue this morning.
Can you please check if you are still able to reproduce it? Looks like it was a server issue and it most likely got fixed. [:)]
0 -
Just done - verbum Win 7
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."
0 -
Angela Murashov said:
Can you please check if you are still able to reproduce it?
Sure. Worse today, 80 minutes with Logos mostly idle from
2014-08-04 20:06:53.9283 1 Info AppCommand (Timed) Executing command: ReadingLists
2014-08-04 20:06:53.9943 1 Info PanelViewModel Applying panel settings for Preferences: SelectedList=Hermeneutics!Andrew%20Mckenzie!http://topics.logos.com/Hermeneutics!0
2014-08-04 20:06:54.0113 1 Info PanelViewModel Got panel settings for History: SelectedList=Hermeneutics!Andrew%20Mckenzie!http://topics.logos.com/Hermeneutics!1
2014-08-04 20:06:54.5104 1 Info AppCommand (579ms) Executing command: ReadingListsto the RL showing at 21:07 and I activated a feature with
2014-08-04 21:28:21.1829 1 Info MainWindow MainWindow activated.
2014-08-04 21:28:21.1859 1 Info LDLS4.AppModel App is no longer idle.Again the app busied itself with trying to download superfluous thumbnails like http://d17g46tfi0dv3u.cloudfront.net/8933/4338933_large_07617305360743aca91e3068233b4df2.jpg which appears instantly on my browser. I have never seen this and it seems not to be a product Logos or Vyrso sells.
Log: 3580.Logos (5).zip
Have joy in the Lord!
0 -
MJ. Smith said:
Just done - verbum Win 7
NB.Mick said:Sure. Worse today, 80 minutes with Logos mostly idle from
Dylan and I both tested this with our Verbum apps on Windows (both in-network and out-network) and we were not able to reproduce. [:(]
Can you please post up a new set of logs including the LogosError.log files? That might show the Developer more clues about what's going on. Thanks [:)]
0 -
Angela Murashov said:
we were not able to reproduce.
Can you please post up a new set of logs including the LogosError.log files? That might show the Developer more clues about what's going on.
I wasn't expecting you to be able to reproduce.
Restarted to empty layout, let indexer finish. Only had the PB tool open (a wrong click) but not doing anything with it. Opened RL to "Trinity" ( a saved list) around 1:36 and had it running until about 2:30 - all available logs attached: 5241.logs.zip
This was running in Logos mode and English UI - so no exotics. You probably can tick off all entries that match the same test on a Win 32 machine on your side - anything that's different should give the dev's a clue.
Have joy in the Lord!
0 -
There seems to be something very strange happening with your Internet connection, but it's not something I'm able to diagnose from your logs.
Firstly, it's not limited to just Logos servers. Cloudfront.net is a CDN operated by Amazon; it's supposed to be globally distributed and very fast, so to see this kind of error is very surprising:
2014-08-05 01:12:26.7029 4 Warn HttpWebRequestUtility WebException reading WebResponse from 'http://d17g46tfi0dv3u.cloudfront.net/1397/651397_large_80f1fb02396a41bbab6ede32ec79cb27.jpg': The operation has timed out
These lines are also extremely atypical:
2014-08-05 01:20:33.8778 4 Info UpdateManager (Timed) Checking for patches.
...
2014-08-05 01:32:31.0488 4 Info UpdateManager (11m 57.2s) Checking for patches."Checking for patches" submits a number of HTTP HEAD requests to a remote Amazon server. It should complete in well under a minute.
Meanwhile, some Logos servers are returning data quite quickly:
2014-08-05 00:59:56.2380 26 Info ResourceMetadataUpdateServiceClient Requesting all community metadata with milestone greater than '133148'.
2014-08-05 00:59:57.3570 26 Info ResourceMetadataUpdateServiceClient 1000 community metadata records retrieved from service.But others are taking an extremely long time:
2014-08-05 02:04:38.0840 27 Info HomePageViewModel (57m 36.2s) Getting RSS feeds
It sounds like those Cloudfront URLs load instantly in your browser? It's hard to know if that's always true, or happens because Logos has already (very slowly) requested the image and it's now cached closer to you. Or there could be an intermediate proxy that doesn't recognise/like Logos' User-Agent string and discards its requests.
Whatever the case, it seems unlikely that Amazon's servers are the problem here, so I suspect the issue is somewhere between them and Logos.exe on your machine (including local network security software). I imagine you've already tried many common troubleshooting steps, but here are some things I can think of:
- netsh int ip reset (http://support.microsoft.com/kb/299357)
- disable any local firewall software
- check your proxy settings; make sure they haven't been taken over by malware
- try a different ISP (e.g., take your laptop, if you have one, to an Internet cafe)
- use Fiddler or Wireshark to capture low-level HTTP traces
0 -
Bradley Grainger (Logos) said:
here are some things I can think of
Also check your DNS server settings to make sure they haven't been hijacked by malware; using your ISP's DNS servers is recommended, or you can try Google's public DNS servers (https://developers.google.com/speed/public-dns/docs/using).
0
