Обсуждение: Archives are borked

Поиск
Список
Период
Сортировка

Archives are borked

От
"Joshua D. Drake"
Дата:
Hello,

Apparently we (CMD) have not been able to been able to pull new archives
since the 25th of this month. I show our cron running... but the threads
are not being updated.

Marc?

Joshua D. Drake

--

             === The PostgreSQL Company: Command Prompt, Inc. ===
       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
       Providing the most comprehensive  PostgreSQL solutions since 1997
                      http://www.commandprompt.com/



Re: Archives are borked

От
"Joshua D. Drake"
Дата:
Marc G. Fournier wrote:
> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>
>> Hello,
>>
>> Apparently we (CMD) have not been able to been able to pull new
>> archives since the 25th of this month. I show our cron running... but
>> the threads are not being updated.
>>
>> Marc?
>
> Any errors on your side?  Like, unable to connect to the rsync server? :)

No.. that is just it.. I show the rsync happening, just no updates :)

>
> try it now, should be fixed
>
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664
>


--

             === The PostgreSQL Company: Command Prompt, Inc. ===
       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
       Providing the most comprehensive  PostgreSQL solutions since 1997
                      http://www.commandprompt.com/



Re: Archives are borked

От
"Marc G. Fournier"
Дата:
On Tue, 28 Mar 2006, Joshua D. Drake wrote:

> Marc G. Fournier wrote:
>> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>>
>>> Hello,
>>>
>>> Apparently we (CMD) have not been able to been able to pull new archives
>>> since the 25th of this month. I show our cron running... but the threads
>>> are not being updated.
>>>
>>> Marc?
>>
>> Any errors on your side?  Like, unable to connect to the rsync server? :)
>
> No.. that is just it.. I show the rsync happening, just no updates :)

Odd ... the rsync daemon itself has been down since the 25th, which is why
it hasn't been updating ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664

Re: Archives are borked

От
"Joshua D. Drake"
Дата:
Marc G. Fournier wrote:
> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>
>> Marc G. Fournier wrote:
>>> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>>>
>>>> Hello,
>>>>
>>>> Apparently we (CMD) have not been able to been able to pull new
>>>> archives since the 25th of this month. I show our cron running...
>>>> but the threads are not being updated.
>>>>
>>>> Marc?
>>>
>>> Any errors on your side?  Like, unable to connect to the rsync
>>> server? :)
>>
>> No.. that is just it.. I show the rsync happening, just no updates :)
>
> Odd ... the rsync daemon itself has been down since the 25th, which is
> why it hasn't been updating ...

Why don't we set up SSH keys for this so we don't need the rsync daemon?

J


>
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>


--

             === The PostgreSQL Company: Command Prompt, Inc. ===
       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
       Providing the most comprehensive  PostgreSQL solutions since 1997
                      http://www.commandprompt.com/



Re: Archives are borked

От
"Marc G. Fournier"
Дата:
On Tue, 28 Mar 2006, Joshua D. Drake wrote:

> Marc G. Fournier wrote:
>> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>>
>>> Marc G. Fournier wrote:
>>>> On Tue, 28 Mar 2006, Joshua D. Drake wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> Apparently we (CMD) have not been able to been able to pull new archives
>>>>> since the 25th of this month. I show our cron running... but the threads
>>>>> are not being updated.
>>>>>
>>>>> Marc?
>>>>
>>>> Any errors on your side?  Like, unable to connect to the rsync server? :)
>>>
>>> No.. that is just it.. I show the rsync happening, just no updates :)
>>
>> Odd ... the rsync daemon itself has been down since the 25th, which is why
>> it hasn't been updating ...
>
> Why don't we set up SSH keys for this so we don't need the rsync daemon?

The daemon allows me to setup exclude lists, ssh wouldn't ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664

Re: Archives are borked

От
"Joshua D. Drake"
Дата:
>> Why don't we set up SSH keys for this so we don't need the rsync daemon?
>
> The daemon allows me to setup exclude lists, ssh wouldn't ...

Then perchance a nagios script that will check the rsync daemon?


>
> ----
> Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
>


--

             === The PostgreSQL Company: Command Prompt, Inc. ===
       Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
       Providing the most comprehensive  PostgreSQL solutions since 1997
                      http://www.commandprompt.com/



Re: Archives are borked

От
"Marc G. Fournier"
Дата:
On Tue, 28 Mar 2006, Joshua D. Drake wrote:

>
>>> Why don't we set up SSH keys for this so we don't need the rsync daemon?
>>
>> The daemon allows me to setup exclude lists, ssh wouldn't ...
>
> Then perchance a nagios script that will check the rsync daemon?

Actually, the reason why it wasn't is already fixed ... I had, for some
reaosn I can't recall, commented out the entry awhile back ... I suspect
it was when I was mucking around and didn't want the 'visible archives' to
get any errors ... the server rebooted and the daemon didn't come back up
again ...

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ: 7615664

Re: Archives are borked

От
"Dave Page"
Дата:

> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake
> Sent: 29 March 2006 00:42
> To: Marc G. Fournier
> Cc: PostgreSQL WWW
> Subject: Re: [pgsql-www] Archives are borked
>
>
> >> Why don't we set up SSH keys for this so we don't need the
> rsync daemon?
> >
> > The daemon allows me to setup exclude lists, ssh wouldn't ...
>
> Then perchance a nagios script that will check the rsync daemon?

Added.

Regards, Dave.