From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25693 invoked from network); 11 Mar 2003 03:02:55 -0000 Received: from unknown (HELO monty-python.gnu.org) (199.232.76.173) by 172.16.49.205 with SMTP; 11 Mar 2003 03:02:55 -0000 Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18sa2N-0008Ti-0A for listarch-gnats-devel@sources.redhat.com; Mon, 10 Mar 2003 22:02:43 -0500 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18sa25-0008Mo-00 for help-gnats@gnu.org; Mon, 10 Mar 2003 22:02:25 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18sa22-0008Bv-00 for help-gnats@gnu.org; Mon, 10 Mar 2003 22:02:24 -0500 Received: from [207.44.208.66] (helo=ns1.brooklyn-realty.com) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18sa21-00083g-00 for help-gnats@gnu.org; Mon, 10 Mar 2003 22:02:21 -0500 Received: from EEL.brooklyn-realty.com (host3.209.113.225.conversent.net [209.113.225.3]) (authenticated (0 bits))h2B3LoL10186; Mon, 10 Mar 2003 22:21:58 -0500 Message-Id: <5.1.0.14.2.20030310213557.03fd7478@mail.brooklyn-realty.com> X-Sender: elena@brooklyn-realty.com@mail.brooklyn-realty.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 11 Mar 2003 03:02:00 -0000 To: Hans-Albert@ha-schneider.de From: Elena In-Reply-To: <15981.5994.104607.163764@habakuk.home.ha-schneider.de> References: <5.1.0.14.2.20030303093522.04240c30@mail.reefedge.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: help-gnats@gnu.org Subject: Re: email follow up to GNATS PRs X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: General discussion about GNU GNATS List-Help: List-Post: List-Subscribe: , List-Archive: 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-q1/txt/msg00093.txt.bz2 Hans-Albert, Thank you so much for detailed description. I must apologize - as I have found the root of the problem - but failed to report it back to the list. At one point I was looking for a way to allow for a text to be added to the audit-trail manually (append) and I have followed an example - which suggest to add "Add-to-Audit-Trail" parameter in dbconfig - and also entailed setting "Audit-Trail" parameter to "read-only" When I removed "Add-to-Audit-Trail" parameter (no longer needed) I forgot to remove "read-only" from the "Audit-Trail". This what have caused the behavior I described. Not sure - whether it is a bug - or desired behavior - but I though it was a little odd. If it was truly read-only - I would of not expected to have "on-change" entries getting appended to audit-trail - and they did. Not sure what "read-only" really means for this parameter - whether it read-only for "user" or "internal system" etc... but ever since I have removed it - everything seem to be working just fine. Thanks again for your help! P.S. I have compiled Gnats - running Linux Red Hat 6.2 with 2.4.18 kernel -elena At 11:53 PM 3/10/2003 +0100, Hans-Albert Schneider wrote: >>>>>> "Elena" == Elena writes: > > Elena> Hi, Can anyone point me to the right direction.... > > Elena> We have gnats 4.0 beta version. When someone sends > Elena> email follow up to gnats, following happens: > > Elena> 1. file "gnatsBlah" created in the gnats-queue > Elena> directory 2. Short thereafter file disappears from the > Elena> the gnats-queue directory (I think it is getting > Elena> parsed correctly than) 3. Gnats sends email > Elena> confirmation "The following reply was made to PR > Elena> .....; it has been noted by GNATS." with a body of > Elena> follow up. 4. Nothing else happens > > Elena> I was expecting that at #4 I would see follow up > Elena> appended to the PR's audit-trail, but this never > Elena> happens. Any ideas of what may be wrong? I have > Elena> checked file permissions, GNATS can write to > Elena> PRs. Also, audit-trail entries working otherwise > Elena> (State change, etc) > > Elena> Any help is much appreciated! -elena > > >Try the following: > >a) temporarily remove the cron job (so 2. will not happen by > accident) > >b) send a new follow-up e-mail > >c) when this mail is in the queue, manually run the > queue-pr -r -d > from the cron job. Watch for error messages, exit code, > core file etc.: > > cd /gnats-queue > queue-pr -r -d > > This hopefully gives you some error messages that point you > into the right direction. > > Next, check the exit status ("echo $?" for bash, ksh and friends, > "echo $status" for (t)csh). > > You may want to look for a "core dump": > ls -l *core* > > If there is a core file, use the "file" command to find out > which application produced it (probably queue-pr) and try to > find the code location of the crash with a debugger, e.g.: > > gdb /usr/local/libexec/gnats/queue-pr core > > I don't know whether you are a programmer, and I am not good > at describing debuggers. The debugger has a command that > lists the stack frames; for GNU gdb this is "where". > > >d) If this doesn't help you, repeat b) and c), but add "-D" to the > queue-pr command. This switches debug messages on; try to get > a clue from them. > > >e) re-activate the cron job. > > >If you get some new information, but cannot solve the problem, >please come back *to the list* with this info (not to me, I will >be on vacation soon; sorry.) > > >Please also state which operating system and hardware platform >you use ("uname -a"). > >If this is a Linux system, please also state the vendor (RedHat, >SuSE, Debian, Mandrake, ...) and vendor version (e.g., "RedHat >7.2"); some systems have a file /etc/-release (e.g., >/etc/SuSE-release) that should contain this information. > >Did you compile GNATS yourself, or did you use a pre-compiled >package? > > >Hans-Albert > >-- >Hans-Albert Schneider >Munich, Germany >EMail: Hans-Albert@HA-Schneider.de _______________________________________________ Help-gnats mailing list Help-gnats@gnu.org http://mail.gnu.org/mailman/listinfo/help-gnats