public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Stuart Stevens" <stuart_stevens@sierralogic.com>
To: <jcowgar@advancedpricing.com>, "'Chad Walstrom'" <chewie@wookimus.net>
Cc: help-gnats@gnu.org
Subject: RE: Gnatsweb: Unparseable reply from gnatsd
Date: Tue, 15 Mar 2005 17:36:00 -0000	[thread overview]
Message-ID: <E1DBFlE-0004ct-MO@lists.gnu.org> (raw)
In-Reply-To: <1110833108.3886.29.camel@localhost.localdomain>

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

  reply	other threads:[~2005-03-15 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 19:41 Jeremy Cowgar
2005-03-14 20:57 ` Chad Walstrom
2005-03-15  3:38   ` Jeremy Cowgar
2005-03-15 17:36     ` Stuart Stevens [this message]
     [not found] <20050315170600.3290EE90F1@mail.advancedpricing.com>
2005-03-15 17:54 ` Jeremy Cowgar
2005-03-15 18:11   ` Chad Walstrom
2005-03-16  6:43     ` Chad Walstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1DBFlE-0004ct-MO@lists.gnu.org \
    --to=stuart_stevens@sierralogic.com \
    --cc=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    --cc=jcowgar@advancedpricing.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).