Re: email follow up to GNATS PRs

[Hans-Albert Schneider]

>>>>> "Elena" == Elena  <address@hidden> 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 <database-name>
   from the cron job.  Watch for error messages, exit code,
   core file etc.:

        cd <database-dir>/gnats-queue
        queue-pr -r -d <database-name>

   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/<vendorname>-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: address@hidden