Re: alioth is down (again)
On Die, 31 Jän 2012, Paul Wise wrote: On Tue, Jan 31, 2012 at 2:58 AM, Julien Cristau wrote: Like ldapsearch(1)? That kind of already exists... More like a frontend to ldapsearch that doesn't require people to know about LDAP, about the Debian schema, nor ldapsearch itself. The status field in ldap unfortunately isn't really all that well maintained, and therefore not too useful. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120131094958.gb7...@anguilla.noreply.org
Re: alioth is down (again)
On Tue, Jan 31, 2012 at 09:31:00AM +0800, Paul Wise wrote: On Tue, Jan 31, 2012 at 2:58 AM, Julien Cristau wrote: Like ldapsearch(1)? That kind of already exists... More like a frontend to ldapsearch that doesn't require people to know about LDAP, about the Debian schema, nor ldapsearch itself. Yes, but that doesn't require a machine-parsable version of machines.cgi, does it? -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120131200325.gb20...@grep.be
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 zo...@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 sg...@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 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/44a0e2a37c3cd2111e20785a5de6dcc5.squir...@hal.hierax.net
Re: alioth is down (again)
On Mon, Jan 30, 2012 at 10:42:48 +0800, Paul Wise wrote: I guess DSA would welcome a patch adding machine-parsable output and status information to this: https://db.debian.org/machines.cgi I guess the devscripts maintainers would also welcome a script to read the resulting info and print it out. Like ldapsearch(1)? That kind of already exists... Cheers, Julien signature.asc Description: Digital signature
Re: alioth is down (again)
On Tue, Jan 31, 2012 at 2:58 AM, Julien Cristau wrote: Like ldapsearch(1)? That kind of already exists... More like a frontend to ldapsearch that doesn't require people to know about LDAP, about the Debian schema, nor ldapsearch itself. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6fc1sv_6pzqodcc6msgqtscxktzuounb76-zckmmfi...@mail.gmail.com
Re: alioth is down (again)
On Sun, Jan 29, 2012 at 2:15 PM, Stephen Gran sg...@debian.org wrote: Hello, Unfortunately, one of the pair of machines providing the alioth service (vasks.debian.org) won't power on. We are working on it, and apologize for any inconvenience caused. Cheers, Hello, First, thanks from a plain user, to all people working to provide infrastructure to Debian project. 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... approach one) Run a public nagios, monit, whatever, configured with templates to notify to this list on defined events (i.e. more than 10 minutes down? the service, the DNS, the whole machine, the whole network? is service recovered again? approach two) Search across available opensource monitoring systems, some than can run some status.debian.org, so instead of emails, users having an issue can lookup such dashboard, and see present and past status or issues. approach three) Write a fast and furious bash/perl/python script (can be cool to just use priority = standard or as few depends as possible), that takes a debian.org/infrastructure.yaml file (or .json or .txt or xml or ...) that defines Debian machines and services... the CLI client runs against such file (so it diagnoses that network connection to d.o is ok in first instance) and prints a report of unreachable services... (one run, one check. So no too much overload unless lot of users synchronize a DoS, that can be done with or without this tool). approach four) Search or write a distributed monitoring service, that provides the one or two approaches, but from different geolocalized places, so after detect that a service/machine is down from here, it tries to communicate with other continents monitoring systems and contrast results before validate the issue. approach five) ... sure that people more clever than me, can propose better solutions, to automate issue notification and tracking... please do! This is not one big neither important, improvement front, to Debian, these are just suggestions on ideas to improve the process, from my personal view point, that of course maybe plainly wrong from outside the project. I can just help with details on the ideas, with code if needed, and collaborate from my home aDSL to distributed monitoring in case it's needed, but I think that my home connection fails more often than Debian machines do. Again thanks to every people doing the work. -- Iñigo -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKDTd8QhJ14=ubtwvstvqzxrfd5ejs9m9bhipkn_ha8w6nz...@mail.gmail.com
Re: alioth is down (again)
On Sun, Jan 29, 2012 at 8:40 PM, Poison Bit poison...@gmail.com wrote: [] Add more brain dump: The solution can be split: monitoring for DD/NM services, and monitoring for final users (i.e. websites, wiki, mailing lists and official mirrors). Monitoring, dashboard, yaml file or whatever. I use to think too much as final user... I.E. I could love to use a Debian anonymous DNS servers instead of be tracked on 8.8.8.8 to get publicity. Sorry it that annoys to someone. Greetings. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKDTd8STJR1apjGDuUNk14-TDTz-=alj2b5rfvzmzg6kbun...@mail.gmail.com
Re: alioth is down (again)
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 sg...@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. [1] http://lists.debian.org/debian-services-admin/2012/01/msg3.html -- Martin Zobel-Helas zo...@debian.org | Debian System Administrator Debian GNU/Linux Developer | Debian Listmaster GPG key http://go.debian.net/B11B627B | GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120129201303.gc3...@ftbfs.de
Re: alioth is down (again)
On Sun, Jan 29, 2012 at 3:13 PM, Martin Zobel-Helas zo...@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 sg...@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. Thanks! -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Maintainer http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cal6k_axnob1z_gx9owp5bag_u-uzofbfg8vp2xa2sc2jp0n...@mail.gmail.com
Re: alioth is down (again)
Am 29.01.2012 20:52, schrieb Poison Bit: On Sun, Jan 29, 2012 at 8:40 PM, Poison Bit poison...@gmail.com wrote: [] [...] I use to think too much as final user... I.E. I could love to use a Debian anonymous DNS servers instead of be tracked on 8.8.8.8 to get publicity. Sorry it that annoys to someone. Providing infrastructure services like DNS is not the job of a distribution, but providing software for doing this on your own, which is the case :-) -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org */ signature.asc Description: OpenPGP digital signature
Re: alioth is down (again)
Hi Andrew On Sun, Jan 29, 2012 at 03:53:21PM -0500, Andrew Starr-Bochicchio wrote: On Sun, Jan 29, 2012 at 3:13 PM, Martin Zobel-Helas zo...@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 sg...@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. Martin Zobel-Helas is probably refering to the DSA Wiki [1]. [1] http://dsa.debian.org/ Hope that helps, Salvatore signature.asc Description: Digital signature
Re: alioth is down (again)
On Mon, Jan 30, 2012 at 3:40 AM, Poison Bit wrote: approach one) Run a public nagios, monit, whatever, configured with templates to notify to this list on defined events (i.e. more than 10 minutes down? the service, the DNS, the whole machine, the whole network? is service recovered again? I don't think it would be appropriate to notify d-d-a or d-i-a on every service flap. Servers are already monitored: http://dsa.debian.org/ https://nagios.debian.org/nagios3/ http://munin.debian.org/ approach two) Search across available opensource monitoring systems, some than can run some status.debian.org, so instead of emails, users having an issue can lookup such dashboard, and see present and past status or issues. http://dsa.debian.org/ https://nagios.debian.org/nagios3/ http://munin.debian.org/ approach three) Write a fast and furious bash/perl/python script (can be cool to just use priority = standard or as few depends as possible), that takes a debian.org/infrastructure.yaml file (or .json or .txt or xml or ...) that defines Debian machines and services... the CLI client runs against such file (so it diagnoses that network connection to d.o is ok in first instance) and prints a report of unreachable services... (one run, one check. So no too much overload unless lot of users synchronize a DoS, that can be done with or without this tool). I guess DSA would welcome a patch adding machine-parsable output and status information to this: https://db.debian.org/machines.cgi I guess the devscripts maintainers would also welcome a script to read the resulting info and print it out. approach four) Search or write a distributed monitoring service, that provides the one or two approaches, but from different geolocalized places, so after detect that a service/machine is down from here, it tries to communicate with other continents monitoring systems and contrast results before validate the issue. Sounds like something that would be doable with nagios, I suggest you send a patch for DSA's puppet configuration when alioth returns: git://anonscm.debian.org/mirror/dsa-puppet.git (currently down due to alioth being down) http://dsa.debian.org/howto/puppet-setup/ -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6GLfm768u0Z1dvY2UjMU-jKXTk4Hnp=2qxkrlt82hv...@mail.gmail.com
