From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1012 invoked from network); 15 Mar 2005 17:09:25 -0000 Received: from unknown (HELO lists.gnu.org) (199.232.76.165) by sourceware.org with SMTP; 15 Mar 2005 17:09:25 -0000 Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DBFmZ-0004w3-8J for listarch-gnats-devel@sources.redhat.com; Tue, 15 Mar 2005 12:24:39 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DBFlL-0004fS-MM for help-gnats@gnu.org; Tue, 15 Mar 2005 12:23:24 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DBFlE-0004ct-MO for help-gnats@gnu.org; Tue, 15 Mar 2005 12:23:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DBFlE-0004bx-JI for help-gnats@gnu.org; Tue, 15 Mar 2005 12:23:16 -0500 Received: from [66.60.176.163] (helo=sierralogic.com) by monty-python.gnu.org with smtp (Exim 4.34) id 1DBFVX-0000Cf-2v for help-gnats@gnu.org; Tue, 15 Mar 2005 12:07:03 -0500 Received: (qmail 19798 invoked from network); 15 Mar 2005 17:06:24 -0000 Received: from unknown (HELO wizard) (192.168.174.221) by 0 with SMTP; 15 Mar 2005 17:06:24 -0000 From: "Stuart Stevens" To: , "'Chad Walstrom'" Date: Tue, 15 Mar 2005 17:36:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcUo2JnmY+Kkt25TTCO9Y/S97K/wKwAqJi6A In-Reply-To: <1110833108.3886.29.camel@localhost.localdomain> Message-Id: Cc: help-gnats@gnu.org Subject: RE: Gnatsweb: Unparseable reply from gnatsd X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion about GNU GNATS List-Archive: List-Post: List-Help: List-Subscribe: , Sender: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org Errors-To: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org X-SW-Source: 2005-q1/txt/msg00074.txt.bz2 One reason that the reply is unparseable if it is blank is if the server dies unexpectedly. I have seen this happen with 4.0. Stuart -----Original Message----- From: help-gnats-bounces+stuart_stevens=sierralogic.com@gnu.org [mailto:help-gnats-bounces+stuart_stevens=sierralogic.com@gnu.org] On Behalf Of Jeremy Cowgar Sent: Monday, March 14, 2005 12:45 PM To: Chad Walstrom Cc: help-gnats@gnu.org Subject: Re: Gnatsweb: Unparseable reply from gnatsd On Mon, 2005-03-14 at 13:24 -0600, Chad Walstrom wrote: > Make sure your "initial-entry" and "index" specs in dbconfig no longer > contain the fields you don't need. Then, reindex the database with > gen-index. I don't recall if gnatsweb requires certain fields to be > present or not, but browse through the source code just to make certain. Initially, when making all the changes, we ran into problems like this, and that made me create a field mapping and ensure the removed fields no longer existed anywhere. I again verified this w/no problems found. I re-indexed to be safe as well. > The emacs interface may not be making assumptions about which fields are > available whereas gnatsweb may be. > I'm no perl programmer, but I did not see anything making me think there are fields required in gnatsweb.pl. I did, however, find some debug values that might be nice. Here is the results of the raw server reply: server_reply: 200 localhost.localdomain GNATS server 4.0 ready. server_reply: 301 List follows. server_reply: 210-Now accessing GNATS database 'default' server_reply: 210 User access level set to 'admin' server_reply: 301 List follows. server_reply: 350-Integer server_reply: 350-Enum server_reply: 350-Text server_reply: 350-Enum server_reply: 350-Enum server_reply: 350-Enum server_reply: 350-Enum server_reply: 350-Enum server_reply: 350-Date server_reply: 350-Date server_reply: 350-Date server_reply: 350-Enum server_reply: 350-MultiText server_reply: 350-MultiText server_reply: 350-MultiText server_reply: 350-MultiText server_reply: 350-MultiText server_reply: 350 MultiText server_reply: 350-PR Number server_reply: 350-What area does this PR fall into? server_reply: 350-One-line summary of the PR server_reply: 350-How severe is the PR? server_reply: 350-How critical is it that the PR be fixed? server_reply: 350-The user responsible for the PR server_reply: 350-The current state of the PR server_reply: 350-Site-specific identification of the PR author server_reply: 350-Arrival date of the PR server_reply: 350-Date when the PR was closed server_reply: 350-Last modification date of the PR server_reply: 350-Release number or tag server_reply: 350-Precise description of the problem server_reply: 350-Code/input/activities to reproduce the problem server_reply: 350-How to correct or work around the problem, if known server_reply: 350- server_reply: 350-Log of specific changes to the PR server_reply: 350 Miscellaneous text that was not parsed properly server_reply: 350-readonly server_reply: 350-textsearch server_reply: 350-textsearch server_reply: 350-textsearch server_reply: 350-textsearch server_reply: 350-textsearch allowAnyValue requireChangeReason server_reply: 350-textsearch requireChangeReason server_reply: 350-textsearch server_reply: 350-readonly server_reply: 350-readonly server_reply: 350-readonly server_reply: 350-textsearch server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350 server_reply: 350--1 server_reply: 350-pending server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350-open server_reply: 350-unknown server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350- server_reply: 350-\nUnknown server_reply: 350- server_reply: 350- server_reply: 350 server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 Valid values follow server_reply: 301 List follows. server_reply: 301 List follows. server_reply: 301 List follows. server_reply: 301 List follows. server_reply: 301 List follows. server_reply: 211 Ok. server_reply: 210 PR text checked OK. server_reply: 211 Ok. server_reply: Then I changed the error message to include '---' surrounding the server reply message to see exactly what it was complaining about and here is the error message again: Error Unparseable reply from gnatsd: ------ So, it seems to me that the server is returning a blank line and gnatsweb.pl isn't liking it. I'm only guessing, as I have already said, I no perl programmer. Jeremy _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnats _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://lists.gnu.org/mailman/listinfo/help-gnats