savannah-hackers-public
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers-public] Re: [Savannah-reports-private] Cron <addre


From: Sylvain Beucler
Subject: Re: [Savannah-hackers-public] Re: [Savannah-reports-private] Cron <address@hidden> sv_mailman --cron
Date: Thu, 17 Jan 2008 23:33:36 +0100
User-agent: Mutt/1.5.17 (2007-11-01)

On Thu, Jan 17, 2008 at 04:04:41PM -0600, Karl Berry wrote:
>     Anybody knows why ./savannah_wrapper.pl is 644 now?
> 
> I made a mistake, now repaired.  It was only 644 for a couple hours, and
> I did several test creations.  
> 
>     The guiltly has to fix this and make sure the last modified lists (as
>     seen in savannah_wrapper.log) are re-synchronized with Savane :P
> 
> If you're talking about
> "savannah_wrapper.log-last_6_could_not_be_created", I have no idea.  I
> did not touch savannah_wrapper.pl until today, and the last 6 list
> creations in the log file are all from many days ago.  And the last two
> (fab-user and amw-developer), at least (I didn't check further back), do
> indeed exist on lists.gnu.org.

There was 6 ./savannah_wrapper.pl errors reported by cron.

I just realized that, in fact, they could not be logged, because the
logging is part of ./savannah_wrapper.pl. So it's actually useless to
check the logs.

This means that 6 lists in the Savane database are desynchronized with
lists.gnu.org - either still active while marked for deletion, either
inactive while marked for creation.

Maybe this is the test creations - or maybe not.

-- 
Sylvain




reply via email to

[Prev in Thread] Current Thread [Next in Thread]