From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31306 invoked from network); 14 Sep 2003 08:23:46 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by sources.redhat.com with SMTP; 14 Sep 2003 08:23:46 -0000 Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.22) id 19yS97-0004Qb-Ds for listarch-gnats-devel@sources.redhat.com; Sun, 14 Sep 2003 04:22:13 -0400 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.22) id 19yS91-0004QS-GX for help-gnats@gnu.org; Sun, 14 Sep 2003 04:22:07 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.22) id 19yS8z-0004Px-SA for help-gnats@gnu.org; Sun, 14 Sep 2003 04:22:06 -0400 Received: from [202.7.78.170] (helo=localhost.localdomain) by monty-python.gnu.org with esmtp (Exim 4.22) id 19yS8y-0004Pq-Jn for help-gnats@gnu.org; Sun, 14 Sep 2003 04:22:05 -0400 Received: (from andrewg@localhost) by localhost.localdomain (8.11.2/8.11.2) id h8E8PKi02709; Sun, 14 Sep 2003 18:25:20 +1000 Date: Sun, 14 Sep 2003 08:51:00 -0000 Message-Id: <200309140825.h8E8PKi02709@localhost.localdomain> From: "Andrew J. Gray" To: prashanthguduru@yahoo.com In-reply-to: <20030910132517.57978.qmail@web13408.mail.yahoo.com> (message from Prashanth Guduru on Wed, 10 Sep 2003 06:25:17 -0700 (PDT)) References: <20030910132517.57978.qmail@web13408.mail.yahoo.com> Cc: help-gnats@gnu.org Subject: Re: Error Code 431 X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: General discussion about GNU GNATS List-Archive: List-Post: List-Help: List-Subscribe: , Sender: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org Errors-To: help-gnats-bounces+listarch-gnats-devel=sources.redhat.com@gnu.org X-SW-Source: 2003-q3/txt/msg00087.txt.bz2 Hi Prashanth, > Is there a way i can view the > logs/output of gnatsd. I have had a look into the gnatsd logging functionality to see if it might help you with this problem. Sometimes gnatsd will log error messages to the system log, so it might be worthwhile looking there to see if there are any messages that appear when the problem occurs. (I think the system log is /var/log/messages on a default Red Hat GNU/Linux installation.) The gnatsd code has functionality for logging "debugging" information, but there is no interface for enabling this. To enable it you would need to make a small change to the source code, rebuild and reinstall GNATS. A patch file with the the required change is at the end of this message. The information logged when a PR is successfully created is not very extensive, it looks like this: Sep 14 13:22:08 olga gnatsd[1936]: gnatsd: responsible person is: andrewg Sep 14 13:22:08 olga gnatsd[1936]: gnatsd: PR written out: /usr/local/com/gnatsdb/hammer/2 It is difficult to say if enabling debug logging would help you find the cause of the problem you are seeing. I guess it might be worth a try if you exhaust other approaches. Andrew J. Gray GNU GNATS Maintainer --- gnats-4.0/gnats/gnatsd.c Tue Oct 22 20:40:57 2002 +++ gnats-4.0patch/gnats/gnatsd.c Sun Sep 14 13:20:15 2003 @@ -1003,6 +1003,7 @@ fflush (stdout); init_logging (NULL); + enable_debugging (); if (gethostname (myname, MAXHOSTNAMELEN) != 0) { _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://mail.gnu.org/mailman/listinfo/help-gnats