From: "Andrew J. Gray" <andrewg@gnu.org>
To: prashanthguduru@yahoo.com, yngve.svendsen@sun.com
Cc: help-gnats@gnu.org
Subject: Re: Fwd: Re: Error Code 431
Date: Thu, 11 Sep 2003 18:41:00 -0000 [thread overview]
Message-ID: <200309111202.h8BC2ME10653@localhost.localdomain> (raw)
In-Reply-To: <5.2.1.1.0.20030910202620.00c5fcf8@ms-etro01-01.norway.sun.com> (message from Yngve Svendsen on Wed, 10 Sep 2003 20:28:05 +0200)
Hi Prashanht,
> > >properly by the gnatsd. Is there a way i can view
> > the
> > >logs/output of gnatsd. Have anybody seen this kinda
> 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.
>
> I am also copying Andrew on this. Hopefully he can contribute some further
> advise.
I haven't got any advice beyond what Yngve has suggested at this
stage. If you can discover what steps are required to reproduce the
problem then I can look into it further myself.
I will look into the gnatsd logging functionality to see if you can
use that to get more information. I might also see if I can recreate
a similar problem based on the description you have given.
--
Andrew J. Gray
GNU GNATS Maintainer
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-09-11 12:46 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
2003-09-11 18:41 ` Andrew J. Gray [this message]
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=200309111202.h8BC2ME10653@localhost.localdomain \
--to=andrewg@gnu.org \
--cc=help-gnats@gnu.org \
--cc=prashanthguduru@yahoo.com \
--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).