public inbox for
 help / color / mirror / Atom feed
From: Jeremy Cowgar <>
Subject: Gnatsweb: Unparseable reply from gnatsd
Date: Mon, 14 Mar 2005 19:41:00 -0000	[thread overview]
Message-ID: <1110827078.3886.17.camel@localhost.localdomain> (raw)

When creating a task via Gnatsweb, I recieve the following error:



Unparseable reply from gnatsd

Thank you for your report. It will take a short while for your report to
be processed. When it is, you will receive an automated message about
it, containing the Problem Report number, and the developer who has been
assigned to investigate the problem.


In my apache log:


[Mon Mar 14 14:00:21 2005] gnatsweb: unparseable gnatsd
output: ; user=jcowgar, db=default; stacktrace: In: main::get_reply <=
main::client_cmd <= main::submitnewpr <= main::main
at /usr/lib/cgi-bin/ line 442, <SOCK> line 215., referer:


I use the emacs interface all day long and have no problems. This is the
only information I can find about the problem. Does anyone have any
ideas? I did go through and reformat quite a bit in the dbconfig to
better suit our needs. Everything I did was remove items, I added no new
ones, just removed those we did not need. I have been up and down the
config file w/no luck in finding anything wrong.

The gnatsweb edits bugs just fine, it just cannot create them. Send-pr
and the emacs interface works great w/no problems.



Help-gnats mailing list

             reply	other threads:[~2005-03-14 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 19:41 Jeremy Cowgar [this message]
2005-03-14 20:57 ` Chad Walstrom
2005-03-15  3:38   ` Jeremy Cowgar
2005-03-15 17:36     ` Stuart Stevens
     [not found] <>
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:

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

  git send-email \
    --in-reply-to=1110827078.3886.17.camel@localhost.localdomain \ \ \

* 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).