Dear LIR's, What's up with the database ? Do you think it's normal that this machine crashes every 3-4 weeks ? Does RIPE need some more guys to manage that ? I think all LIR's whould be ok to pay RIPE a little bit more fee that RIPE may have a VERY HIGH BIGGER MTBF (Mean Time Between Failure). What do you think about that ? Or what else solution do you have guys (LIR's and RIPE)... to be continued .... Regards, Pascal PGL2-RIPE, AS6893, CH-PETREL Pascal Gloor Network Manager _________________________ SPAN(tm) / Petrel Communications SA A Cable & Wireless company Tél : + 41 22 304 47 47 Fax : + 41 22 304 47 99 E-mail : pgl@cw.span.ch Web : http://www.span.ch
At Thu, 18 May 2000, owner-lir-wg@ripe.net wrote:
What do you think about that ? Or what else solution do you have guys (LIR's and RIPE)...
Well, maybe you can run a mirror database and give us the hostname? Mark Lastdrager Pine Internet -- email: mark@lastdrager.nl :: ML1400-RIPE :: tel. +31-70-3111010 http://www.pine.nl :: RIPE RegID nl.pine :: fax. +31-70-3111011 PGP key ID 92BB81D1 :: Dutch security news @ http://security.nl Today's excuse: the xy axis in the trackball is coordinated with the summer soltice
Dear Pascal Gloor, Pascal Gloor wrote:
Dear LIR's,
What's up with the database ? Do you think it's normal that this machine crashes every 3-4 weeks ? Does RIPE need some more guys to manage that ? I think all LIR's whould be ok to pay RIPE a little bit more fee that RIPE may have a VERY HIGH BIGGER MTBF (Mean Time Between Failure).
What do you think about that ? Or what else solution do you have guys (LIR's and RIPE)...
The good news is that the Database is up and running again. The server crash did not affect queries, but delayed the updates. Nothing is lost and the updates are now being processed. To be honest, the last crash happened at the end of March, and that was a hardware problem. What happened this time was a break signal sent to DB server by the console server (which resulted in server reboot), the situation we have not expected, but sure it will not happen again. There is always a probability that something goes wrong, but we try to do our best to minimize the problems it causes. Regards, Andrei Robachevsky DB Group Manager RIPE NCC P.S. If you really plan to mirror the RIPE Database, you will need to sign an AUP. This is normal practice. Please write to <ripe-dbm@ripe.net> to discuss this issue.
to be continued ....
Regards,
Pascal PGL2-RIPE, AS6893, CH-PETREL
Pascal Gloor Network Manager _________________________ SPAN(tm) / Petrel Communications SA A Cable & Wireless company
Tél : + 41 22 304 47 47 Fax : + 41 22 304 47 99 E-mail : pgl@cw.span.ch Web : http://www.span.ch
Hi, On Thu, May 18, 2000 at 06:22:39PM +0200, Andrei Robachevsky wrote:
There is always a probability that something goes wrong, but we try to do our best to minimize the problems it causes.
Servers just notice if you're out of country and find some way to fail behind your back... While everybody is complaining, I just want to note that the overall service of the RIPE DB is very good (the turnaround times for updates are slow during the day time, but knowing the history of the RIPE DB, it's amazing that it still works at all ;-) ). You are doing good work, RIPE-DBM people! greetings from Budapest, Gert Doering -- NetMaster -- SpaceNet GmbH Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299
Hello,
-----Urspr|ngliche Nachricht----- Von: owner-lir-wg@ripe.net [mailto:owner-lir-wg@ripe.net]Im Auftrag von Pascal Gloor Gesendet am: Donnerstag, 18. Mai 2000 16:51 An: lir-wg@ripe.net Betreff: RIPE Database crashes ...
Dear LIR's,
What's up with the database ? Do you think it's normal that this machine crashes every 3-4 weeks ? Does RIPE need some more guys to manage that ? I think all LIR's whould be ok to pay RIPE a little bit more fee that RIPE may have a VERY HIGH BIGGER MTBF (Mean Time Between Failure).
What do you think about that ? Or what else solution do you have guys (LIR's and RIPE)...
to be honest, RIPE is providing a really good job to the community. There are always reasons for faults, especially when human beings are involved :-) If something happens with the Database, there was no loss of data in the past years and if you submit a mail to RIPE it will be processed even if there is an outage. So you can trust on RIPE. If i compare the service of RIPE with other organisations we _have_ to work with, the service of RIPE NCC is nearly unbeatable. If you send an email to internic or denic you cant be sure that the mail will be processed and you must check every mail if it is processed or not and in case of faults nobody sends email like RIPE, that the service is interrupted and all mails will be queued. Even the desaster from this french-guy who deleted huge amounts of handles, took only one day for RIPE to present the tracking data to the community. So there are other organisations to blame before we start with RIPE - we think they are doing a really good job for all of us just my 0.02 -- http://www.nextra.de -- feel green-feel nextra -- Winfried.Haug@nextra.de - nextra Baden-Wuerttemberg | Winfried Haug Geschaeftsfuehrer Communication | Nadlerstrasse 21 D-70173 Stuttgart Service Provider GmbH | tel +49-711-6015-0 fax +49-711-6015-199 ---------------------------------------------------------------------------- --
participants (5)
-
Andrei Robachevsky -
Gert Doering, Netmaster -
Mark Lastdrager -
Pascal Gloor -
Winfried Haug