public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Prashanth Guduru <prashanthguduru@yahoo.com>
To: Yngve Svendsen <yngve.svendsen@sun.com>
Cc: help-gnats@gnu.org
Subject: Re: Fwd: Re: Error Code 431
Date: Thu, 11 Sep 2003 12:46:00 -0000	[thread overview]
Message-ID: <20030910200424.22655.qmail@web13405.mail.yahoo.com> (raw)
In-Reply-To: <5.2.1.1.0.20030910202620.00c5fcf8@ms-etro01-01.norway.sun.com>

Hi yngve,

Thats ok. I did the same thing of sending you twice.
Well, i have compared the setups but i am gonna do it
again, very closely. Will get back with the findings.
Thanks again,
Prashanth

--- Yngve Svendsen <yngve.svendsen@sun.com> wrote:
> (sorry I am sending this to you twice, Prashanth,
> but I forgot to cc 
> help-gnats)
> 
> At 07:17 10.09.2003 -0700, Prashanth Guduru wrote:
> >Hi Yngve,
> >
> >THanks for your prompt response. I have actually
> done
> >that, i mean having "?debug=all" appended to the
> url.
> >I have 2 different databases, the first one i
> created
> >was "test", it doesnt have any categories except
> for
> >the default ones.
> 
> (snip)
> 
> 
> >THis is the last client command that is run in both
> >the cases. For the test database i can see the
> >server_reply: 210 PR added and in case of the other
> >database when PR is created the "server_reply:" is
> >empty and thats when i get "Error: Unparseable
> reply
> >from server" and that follows the "Problem Report
> >Sent. THank you for your report...........". I have
> >closely observed the both databases, except for the
> >categories there is no difference in them atall. I
> >dont quite understand why isnt there a 210 PR added
> >response from server and why is'nt the gnats.lock
> file
> >getting deleted. Any comments.
> 
> I have seen similar things happening before and am
> pretty sure that what 
> happens is that gnatsd stumbles upon some config
> problem in the second 
> database during PR submission and that it gets so
> confused that it crashes. 
> That would explain why it never gets as far as to
> give the 210 confirmation 
> message and thus also never deletes the lock file.
> Of course, gnatsd should 
> never crash, no matter what, so if I am correct,
> this would certainly be a bug.
> 
> There are two ways to attack this. The simplest is
> probably if you check 
> the setup of the second database very carefully,
> especially the syntaxof 
> all the config files. The other way is to attach a
> debugger to the gnatsd 
> process and see where it crashes. Unfortunately, I
> have too little 
> experience with that kind of thing to advise you. I
> suggest you try to go 
> very carefully through the setup and report what you
> find.
> 
> Perhaps Andrew can contribute some further advise on
> this?
> 
> - Yngve
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2003-09-10 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 20:09 Yngve Svendsen
2003-09-11 12:46 ` Prashanth Guduru [this message]
2003-09-11 18:41 ` Andrew J. Gray
2003-09-11 21:47   ` Prashanth Guduru
2003-09-12 14:21     ` Mel Hatzis
2003-09-14  9:54     ` Andrew J. Gray

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=20030910200424.22655.qmail@web13405.mail.yahoo.com \
    --to=prashanthguduru@yahoo.com \
    --cc=help-gnats@gnu.org \
    --cc=yngve.svendsen@sun.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).