Re: alioth is down (again)
Il Dom, 29 Gennaio 2012 20:53, Andrew Starr-Bochicchio ha scritto:
> On Sun, Jan 29, 2012 at 3:13 PM, Martin Zobel-Helas <zobel@debian.org>
> wrote:
>> Hi,
>>
>> On Sun Jan 29, 2012 at 20:40:57 +0100, Poison Bit wrote:
>>> On Sun, Jan 29, 2012 at 2:15 PM, Stephen Gran <sgran@debian.org> wrote:
>>> Second, a suggestion or some brain dump about ideas on howto improve
>>> the issues communication:
>>>
>>> I imagine the scenario, where some DD is trying to work from any
>>> place in the world. Nowadays, there are many points to check if a
>>> service is not working... is it my last upgrade? is it my last config
>>> change? is it my ISP? is it some intermediate ISP? is it the service
>>> that is really down? of course, this kind of email notifications are
>>> just fine to notify a known issue.
>>>
>>> So I ask myself... the reason to do not run "any" public monitoring
>>> system, is much increase in the workload of the sysadmins ? There are
>>> different approaches to do it...
>>
>> There is a monitoring, but it seems most DDs and non-DDs do not care and
>> start to pester the admins directly [1].
>>
>> URL and access to the monitoring is documented publicly.
>
> Do you mean: http://db.debian.org/machines.cgi
>
> If so, it's not reporting vasks as down, but that still seems to be
> the case. If you're referring to something else, I'd love to know
> about it.
there is nagios.debian.org
from dsa blog:
"For a list of servers check ud-ldap, or munin, or nagios (try dsa-guest,
no password)."
Ciao,
francesco
--
.''`. Francesco Namuri
: :' : http://hal.hierax.net/
`. `' «Dave, my mind is going. I can feel it. I'm a ...fraid.»
`- 4096R/0E2B1756 - 5036 41CC 7DDE 2F3D 19F8 51CB 4CB7 C22F 0E2B 1756
Reply to: