Stefan acknowledged the alert on 2008-07-04 07:36:15 (per nagios
history), which makes it stop complaining (with the comment that I
should be looking at it - doesn't have any effect if I don't actually
have time to do that before I go on vacation). It still showed up under
services that were down if you went to the nagios website.
> Any idea why there were no alerts? Ae we monitoring pgsql-aardvarks
> instead of pgsql-zebras?
> On 8/1/08, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Joshua D. Drake wrote:
>>> Tom Lane wrote:
>>>> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>>>>> Why is the email below now appearing in a search?
>>>> Probably because nothing has gotten indexed for a month or more.
>>>> Whoever is supposed to maintain the archive indexer has been
>>>> on vacation since it broke ...
>>> That would be Magnus and you are correct. He just got back. The problem
>>> (last I checked) is an issue with Russian emails.
>> Looking at it now. That clearly wasn't the only problem, because there
>> was a "sleep 1800" process that had been running since July 3. Logfiles
>> weren't touched etc. Just restarting it fixed that part, which clearly
>> somebody else could've done as well ;)
>> I found the bug with the Russian emails, btw. It seems mhonarc encoded
>> the invalid UTF8 sequences inside valid HTML escape entities And the
>> code applied the "fix broken UTF8" logic *before* it unescaped the HTML
>> entities. Now it does it both before and after..
>> Oh, and this should never have affected messages on -hackers for
>> example, because it was always processed before ru-general. It would hit
>> the PUG lists, -www, -patches and a few others.
>> Sent via pgsql-www mailing list (pgsql-www(at)postgresql(dot)org)
>> To make changes to your subscription:
In response to
pgsql-www by date
|Next:||From: damien clochard||Date: 2008-08-04 16:27:34|
|Subject: broken link on news page|
|Previous:||From: dpage||Date: 2008-08-01 13:23:39|
|Subject: Re: Email search failure|