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