Skip to Content.
Sympa Menu

metadata-support - Re: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]

Subject: InCommon metadata support

List archive

Re: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]


Chronological Thread 
  • From: "Cantor, Scott" <>
  • To: "" <>
  • Subject: Re: [Metadata-Support] Re: [InCommon NOTICE] How to Protect Against Failed Metadata Processes [ACTION REQUIRED]
  • Date: Tue, 22 Sep 2015 17:50:07 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 164.107.81.218) smtp.mailfrom=osu.edu; incommon.org; dkim=none (message not signed) header.d=none;incommon.org; dmarc=bestguesspass action=none header.from=osu.edu;
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:23
On 9/22/15, 1:45 PM,
"
on behalf of Tom Scavo"
<
on behalf of
>
wrote:

>On Tue, Sep 22, 2015 at 9:41 AM, David Gersic
><>
> wrote:
>>
>> A suggestion for this page: how to detect fail(ing) metadata updates. A
>> simple paragraph on what to look for, how would I know if I'm affected by
>> this, that kind of thing. I think it's as simple as checking to see that
>> the file is updated and that the expiration date in the file is changing
>> appropriately.
>
>Everyone needs to implement the workaround to the logging issue. If
>you do, and a memory issue does occur, it will be logged. If you
>don't, a memory issue will be masked by the logging issue, and you
>will be unaware that anything has gone wrong.

Yes, I would say so. If you really wanted to go write a script that looks at
the file time I guess you could.

-- Scott


Archive powered by MHonArc 2.6.16.

Top of Page