From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,936ac7676e90326c X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 29 Jan 2009 07:49:11 +0100 From: Georg Bauhaus Reply-To: rm.tsoh-bauhaus@maps.futureapps.de User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: ViewMTN service restored on www.ada-france.org References: <4c94ce54-cb0b-4375-af57-58d2d0bd9d5c@l33g2000pri.googlegroups.com> <02ade2e6-ab9b-4b0c-84c5-55dc37fcb9aa@f40g2000pri.googlegroups.com> <427f3949-5477-4e21-af9b-c494affc4de2@t39g2000prh.googlegroups.com> <82c49742-d8ed-4f7c-a725-966da3f31a6d@p23g2000prp.googlegroups.com> In-Reply-To: <82c49742-d8ed-4f7c-a725-966da3f31a6d@p23g2000prp.googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-ID: <49815167$0$31329$9b4e6d93@newsspool4.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 29 Jan 2009 07:49:11 CET NNTP-Posting-Host: 86f406e2.newsspool4.arcor-online.net X-Trace: DXC=o>>[GV5oG Ludovic Brenta wrote: > On Jan 28, 11:49 am, Anders Wirzenius wrote on comp.lang.ada: >> >> Now at least the last three links are not giving that >> error. 12.45 EET, from 194.251.142.28. > > Thanks for the reports. I have investigated the logs and asked the > author of ViewMTN what the problem might be. As it turns out, you get > a "500 Internal Error" if you send a request to ViewMTN while someone > else, at the same time, is using the monotone server (over netsync). > The monotone server locks the database and ViewMTN cannot read from > it. > > So, the simple solution if you see this error message again is: try > again a few moments later. Maybe the author of ViewMTN could use HTTP status code 409 (conflict) or 503 (service unavailable)? (In case you happen to exchange mail again.)