public inbox for [email protected]  

help / color / mirror / Atom feed

From: Magnus Hagander <[email protected]>
To: [email protected]
Cc: Joshua D. Drake <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Email search failure
Date: Fri, 01 Aug 2008 15:36:42 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

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.

//Magnus

[email protected] wrote:
> Any idea why there were no alerts? Ae we monitoring pgsql-aardvarks
> instead of pgsql-zebras?
> 
> On 8/1/08, Magnus Hagander <[email protected]> wrote:
>> Joshua D. Drake wrote:
>>> Tom Lane wrote:
>>>> Bruce Momjian <[email protected]> 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.
>>
>> //Magnus
>>
>> --
>> Sent via pgsql-www mailing list ([email protected])
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-www
>>
> 
> 

view thread (9+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Email search failure
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox