From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 867 invoked from network); 14 Mar 2005 20:57:53 -0000 Received: from unknown (HELO lists.gnu.org) (199.232.76.165) by sourceware.org with SMTP; 14 Mar 2005 20:57:53 -0000 Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DAws4-000583-VE for listarch-gnats-devel@sources.redhat.com; Mon, 14 Mar 2005 16:13:05 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DAwic-0000rH-At for help-gnats@gnu.org; Mon, 14 Mar 2005 16:03:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DAwiX-0000ou-7K for help-gnats@gnu.org; Mon, 14 Mar 2005 16:03:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DAwiV-0000n7-Ft for help-gnats@gnu.org; Mon, 14 Mar 2005 16:03:11 -0500 Received: from [24.140.1.135] (helo=smtp-1.sssnet.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1DAwR2-0006lY-B0 for help-gnats@gnu.org; Mon, 14 Mar 2005 15:45:08 -0500 Received: (qmail 15344 invoked by uid 509); 14 Mar 2005 20:45:08 -0000 Received: from 24.140.53.38 by smtp-2.sssnet.com (envelope-from , uid 501) with qmail-scanner-1.25 (uvscan: v4.2.40/v4445. Clear:RC:1(24.140.53.38):. Processed in 0.07386 secs); 14 Mar 2005 20:45:08 -0000 Received: from cable-53-38.sssnet.com (HELO [192.168.0.138]) ([24.140.53.38]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 14 Mar 2005 20:45:07 -0000 From: Jeremy Cowgar To: Chad Walstrom In-Reply-To: <20050314192405.GC21618@wookimus.net> References: <1110827078.3886.17.camel@localhost.localdomain> <20050314192405.GC21618@wookimus.net> Content-Type: text/plain Organization: Advanced Medical Pricing Services Date: Tue, 15 Mar 2005 03:38:00 -0000 Message-Id: <1110833108.3886.29.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit 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 Reply-To: jcowgar@advancedpricing.com 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/msg00070.txt.bz2 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