public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: Marisol.Garcia@gbr.xerox.com
To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org
Subject: gnatsweb/373: Can not create new PR, a core file is generated in the gnats-queue directory
Date: Fri, 05 Apr 2002 01:57:00 -0000 [thread overview]
Message-ID: <E16tQQa-0004Fb-00@fencepost.gnu.org> (raw)
>Number: 373
>Category: gnatsweb
>Synopsis: Can not create new PR, a core file is generated in the gnats-queue directory
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 05 04:54:40 -0500 2002
>Originator: Marisol Garcia
>Release: Gnats 3.113.1
>Organization:
Xerox UK Ltd
>Environment:
Unix server (Solaris 8)
>Description:
Our Gnats system was working fine until the end of March.
Since Monday (2nd of april), when creating a new problem report, the gnats-web interface displays the succesfull message.
The actual PR doesn't seem to go any further than the gnats-queue directory:
The PR is correctly stored in the queue-pr queue
Once the PR is processed by the "queue-pr --run", a core file is place in the gnats-queue directory, and nothing else happends. The index and current files within the gnats-adm directory are not updated, and the PR is not stored under the appopiate category folder. No e-mail messages are sent either.
>How-To-Repeat:
Date environment system format is British Summer Time:
Friday April 5 10:31:47 BST 2002
(In case if have something to do with the 1 hour change last weekend).
>Fix:
Unknown
>Unformatted:
_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs
reply other threads:[~2002-04-05 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E16tQQa-0004Fb-00@fencepost.gnu.org \
--to=marisol.garcia@gbr.xerox.com \
--cc=bug-gnats@gnu.org \
--cc=gnats-prs@gnu.org \
--cc=pdm-gnats@zamazal.org \
/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).