From: Mel Hatzis <hatzis@juniper.net>
To: help-gnats@gnu.org
Subject: Re: Unparseable reply from gnatsd....
Date: Tue, 22 Jun 2004 18:30:00 -0000 [thread overview]
Message-ID: <40D71EEE.8040402@juniper.net> (raw)
In-Reply-To: <40D70A0C.8090508@gointernet.co.uk>
On 06/21/2004 09:17 AM, Adam Cade submitted:
> Gnats was working just fine.... i did not use it for a few weeks, then
> got this error:
>
> Unparseable reply from gnatsd
I'm guessing you're getting this error in gnatsweb. If so,
gnatsweb is not handling the error returned from gnatsd
and is giving you the "catchall" message.
The easiest way to determine what is wrong is to telnet to the
port gnatsd is listening on and issue your command(s) directly
to gnatsd. This requires a little familiarity with the GNATS
protocol, but it cuts out all the middleware and you can see
the exact reply from gnatsd.
[ The GNATS protocol commands are fairly straightforward to use.
Just enter 'help' and you'll see the list of available commands. ]
Otherwise, please provide a little more information about
what it is you're doing to get this error...is it a query,
a PR create, edit, etc.
--
Mel Hatzis
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2004-06-21 17:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 16:45 Adam Cade
2004-06-21 17:48 ` Chad Walstrom
2004-06-22 18:30 ` Mel Hatzis [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-29 18:40 Eicke Felipe
2003-04-29 18:55 ` Yngve Svendsen
2003-04-29 18:20 Eicke Felipe
2003-04-29 18:23 ` Yngve Svendsen
2003-04-29 17:59 Eicke Felipe
2003-04-29 18:13 ` Yngve Svendsen
2003-04-29 17:37 Eicke Felipe
2003-04-29 17:58 ` Yngve Svendsen
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=40D71EEE.8040402@juniper.net \
--to=hatzis@juniper.net \
--cc=help-gnats@gnu.org \
/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).