What happened to RIPE Database full text search?
Dear all, since a short time I get the following answer on any query in http://www.ripe.net/cgi-bin/ripedbsearch:
The following problem occured during the search:
No objects were found matching the search criteria
Please try again!
Maybe this error arose since the new RIPE-db version 2.1.3 has been implemented last Monday? -- Ludger Bornhorst, Deutsche Telekom AG, ZDK Zentrum fuer Datenkommunikation, Oldenburg, Germany Tel.: +49 441/234-5678 Fax : +49 441/27463
Dear all, Nothing happens to the RIPE DB itself. However, the full search text is not working at this moment. We are investigating and working on fixing it. You can still look at the RIPE DB with the normal whois query interfaces (including the one on the web http://www.ripe.net/db/whois.html) The indexes for the full text search were not created this last night and will be recreated as soon as possible. However, the creation of full text indexes takes a while and the service will be unavailable for a few hours. The DB itself is OK and can be accessed in any of the other usual ways. Sorry for any incovenience Joao Damas RIPE DB Group RIPE NCC ludger.bornhorst@t-online.de (Ludger Bornhorst) writes: * Dear all, * * since a short time I get the following answer on any query in * http://www.ripe.net/cgi-bin/ripedbsearch: * * >The following problem occured during the search: * > * > No objects were found matching the search criteria * > * > Please try again! * * Maybe this error arose since the new RIPE-db version 2.1.3 * has been implemented last Monday? * * -- * Ludger Bornhorst, Deutsche Telekom AG, ZDK * Zentrum fuer Datenkommunikation, Oldenburg, Germany * Tel.: +49 441/234-5678 Fax : +49 441/27463 *
However, the full search text is not working at this moment. We are investigating and working on fixing it.
You can still look at the RIPE DB with the normal whois query interfaces (including the one on the web http://www.ripe.net/db/whois.html)
What about create some special web page called "hot status". This page should contains info about not working services etc. Something like IBM's network status info page. -- Tomas 'TPS' Ulej tps@internet.sk, tu36-ripe c0re Slovakia coordinator, c0re Society, http://www.c0re.sk System Administrator, ISP NETLAB+ Slovakia, http://www.netlab.sk sk.FreeBSD.org coordinator, FreeBSD Project, http://www.sk.freebsd.org
We had a problem with customers using RIPE last night. Was there a change this past weekend? We copied over the RIPE database and it is taking longer than normal to process. Is indexing information usually passed along with the FTP copy of the RIPE database? Regards, Cleve... ------------------------------------------------------------------------- | Cleve K. Mickles | MCI | | IP Engineering | 2100 Reston Parkway | | cmickles@mci.net | Reston, Virginia 20191 | | (703) 715-7047 | (703) 715-7066 FAX | | | VNET 272-7047 | ------------------------------------------------------------------------- Joao Luis Silva Damas <joao@ripe.net> wrote: * Dear all, * Nothing happens to the RIPE DB itself. * * However, the full search text is not working at this moment. * We are investigating and working on fixing it. * * You can still look at the RIPE DB with the normal whois query interfaces * (including the one on the web http://www.ripe.net/db/whois.html) * * The indexes for the full text search were not created this last night and wi * ll * be recreated as soon as possible. However, the creation of full text indexes * * takes a while and the service will be unavailable for a few hours. * * The DB itself is OK and can be accessed in any of the other usual ways. * * Sorry for any incovenience * * Joao Damas * RIPE DB Group * RIPE NCC * * ludger.bornhorst@t-online.de (Ludger Bornhorst) writes: * * Dear all, * * * * since a short time I get the following answer on any query in * * http://www.ripe.net/cgi-bin/ripedbsearch: * * * * >The following problem occured during the search: * * > * * > No objects were found matching the search criteria * * > * * > Please try again! * * * * Maybe this error arose since the new RIPE-db version 2.1.3 * * has been implemented last Monday? * * * * -- * * Ludger Bornhorst, Deutsche Telekom AG, ZDK * * Zentrum fuer Datenkommunikation, Oldenburg, Germany * * Tel.: +49 441/234-5678 Fax : +49 441/27463 * * * *
Hi Cleve, "Cleveland K. Mickles" <cmickles@mci.net> writes: * * We had a problem with customers using RIPE last night. Was * there a change this past weekend? A script was missing and that caused the files in the ftp site to be empty. * * We copied over the RIPE database and it is taking longer * than normal to process. Is indexing information * usually passed along with the FTP copy of the RIPE * database? No, indexing information is not contained on the ftp files. They contain only the data itself. You have to index them after ftp-ing them to your machine. Indexes are dependent on your PERL setup (eg. if you index the database with perl5.003, a whoisd using perl5.004 won't be able to use them), so there is no point in distributing the indexes. The files on the ftp site were restored at 12:00 (our time). What you got depends on the time you got it. Anyway it should not be taking longer than normal because you either got an empty file or a correct one (unless you happened to ftp the file at the same time we were putting it in our ftp site and you have a truncated file. Then the indexing program can choke. Have you checked file length against the one in our ftp site?) Now almost everything is back to normal, including the full search text search. The missing bit is the full version of the database file with the attributes translated to the long version. This file takes so long to generate that we calculated by the time it was finished, the process to generate today's one would be starting so we preferred to get the full search text indexing done first. Apologies for any incovenience. Regards, Joao Damas RIPE NCC * * Regards, * * Cleve... *
Joao, The ftp-able files have an EOF marker: # EOF Any software should check for it. Daniel
participants (5)
-
Cleveland K. Mickles -
Daniel Karrenberg -
Joao Luis Silva Damas -
ludger.bornhorst＠t-online.de -
Tomas TPS Ulej