Oddities in L5 logs

I was looking at my Logos5 logs and noted several warning messages like the following:

Warn UpdateManager Version '2009-10-28T23:14:59Z' returned by server for 'LLS:39.20.2' is older than currently cached version '2012-10-05T23:50

I counted 99 such errors. Some as little as 1 hour different. The oldest one I found was this one:

Warn UpdateManager Version '2002-08-08T19:04:44Z' returned by server for 'LLS:60.0.5' is older than currently cached version '2012-10-08T17:42:

This seems odd. Why doesn't Logos update files on the server?

I checked an old Logos4 log and don't see these warn messages, so this seems like a behavior that's new to Logos5 (though I don't know if it's new to this beta cycle).

I am also finding multiple instances (i.e., dozens) of this which I reported before here:

2013-01-11 08:12:03.1403 1 Error MethodBehaviorConverter Type 'NamedObject' has no matching method 'Load'.
2013-01-11 08:12:03.1403 1 Error MethodBehaviorConverter Type 'NamedObject' has no matching method 'NamedDelete'.

and this:

2013-01-11 08:12:03.1715    1    Error    MethodBehaviorConverter    Type 'NamedObject' has no matching method 'Update'.
2013-01-11 08:12:03.1871    1    Error    MethodBehaviorConverter    Type 'NamedObject' has no matching method 'Load'.
2013-01-11 08:12:03.1871    1    Error    MethodBehaviorConverter    Type 'NamedObject' has no matching method 'Delete'.

These also seem new to Logos5 (but I don't have any logs before this beta cycle to compare it with). Is there a reason for these multiple errors? Does this point to a problem in my system, or to a yet-to-be-implemented feature of Logos5?

FYI: Logos seems to be running normally otherwise.

Find more posts tagged with

Comments

Rich DeRuiter

Bump.

Any word on whether these anomalies are significant in any way?

Bradley Grainger (Logos)

This seems odd. Why doesn't Logos update files on the server?

The warning is indicating that the latest version of the resource is (currently) only available to Logos 5 users, not Logos 4 users. This is an artifact of the beta/initial launch that we will fix. (All LLS resources should be compatible with both Logos 4 and 5.)

Rich DeRuiter

https://community.logos.com/discussion/comment/454437#Comment_454437

The warning is indicating that the latest version of the resource is (currently) only available to Logos 5 users, not Logos 4 users. This is an artifact of the beta/initial launch that we will fix. (All LLS resources should be compatible with both Logos 4 and 5.)

Thanks for the info Bradley.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/454437#Comment_454437

The warning is indicating that the latest version of the resource is (currently) only available to Logos 5 users, not Logos 4 users. This is an artifact of the beta/initial launch that we will fix.

This should be fixed now.

Rich DeRuiter

https://community.logos.com/discussion/comment/455170#Comment_455170

The warning is indicating that the latest version of the resource is (currently) only available to Logos 5 users, not Logos 4 users. This is an artifact of the beta/initial launch that we will fix.

This should be fixed now.

Appears to be.

However, now I'm seeing several other Warn messages like this:

Warn MetadataServiceUtility Invalid Titles (Count=1), Languages (Count=0), or MilestoneIndexes (Count=0); rejecting metadata record for {0AF5CA4B-7D90-40FC-B93A-53E7A2CF93CC}.

And this:

Warn MetadataServiceUtility Invalid Titles (Count=1), Languages (Count=0), or MilestoneIndexes (Count=0); rejecting metadata record for {0AF5CA4B-7D90-40FC-B93A-53E7A2CF93CC}.

And this:

Warn MetadataServiceUtility Invalid ResourceId (LLS:1.0.1201), Version (2002-11-04T21:45:51Z), or ResourceType (); rejecting metadata record.

And this:

Warn HttpClientUtility Unexpected HTTP response when accessing 'http://covers.assets.logos.com/rvi_apfthri/cover.jpg': 404 Not Found; retrying request.