public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: Kazunari Sekigawa <sekigawa@neo.shinko.co.jp> To: yngves@sources.redhat.com Cc: gnats-prs@sourceware.cygnus.com Subject: Re: gnatsweb/228: Internal Server Error when "submit edit" Date: Mon, 20 Aug 2001 04:14:00 -0000 [thread overview] Message-ID: <20010820111401.31273.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR gnatsweb/228; it has been noted by GNATS. From: Kazunari Sekigawa <sekigawa@neo.shinko.co.jp> To: Yngve Svendsen <yngve.svendsen@clustra.com> Cc: gnats-gnats@sourceware.cygnus.com, sudheesh@softjin.com Subject: Re: gnatsweb/228: Internal Server Error when "submit edit" Date: Mon, 20 Aug 2001 20:05:03 +0900 Thank you for your reply. Yngve Svendsen wrote: > > I think your problem may be caused by the GNATS database being locked. Such > a lock might be left after running gen-index, for instance. Look for a file > called gnats.lock in the gnats-adm directories of your databases and delete it. > > Gnatsweb should catch this, and I have identified the problem. However, I > don't plan to do any more work on Gnatsweb 2.x unless more serious bugs > surface. I believe that Gnats and Gnatsweb 4 aren't suffering from this > problem. > > Please let me know how this turns out. > > Yngve Svendsen > Gnatsweb maintainer > Before "submit edit," there was no *lock* file. After "submit edit," a lock file is generated in the name of {DB}/gnats-adm/locks/{nnn}.lock where {DB} is a database name and {nnn} is a problem number in {DB} and {nnn}.lock contains a user's name. The internal server error still remains the same. Once a lock file gets generated, then succeeding "submit edit" returns an error message saying: PR {CATEGORY}/{nnn} is locked by {user} This must be OK. After manually removing the lock file, I again issued "submit edit" then got the same internal server error. Thank you again for your help. K. Sekigawa > At 06:17 01.08.2001 +0000, sekigawa@neo.shinko.co.jp wrote: > >Hi, > > > >When I use "submit edit" of gnatsweb, > >HTTP server returns an internal error as follows. > > > >(a) apache 1.3.19 > > [Wed Aug 1 12:56:27 2001] [error] [client 172.30.30.36] Premature > > end of script headers: \ > > /usr/local/apache/cgi-bin/gnatsweb.cgi > > > >(b) Netscape Enterprise Suitespot 3.5 > > [01/Aug/2001:12:46:06] failure: for host aaa.bbb.shinko.co.jp trying > > to POST \ > > /ppp/cgi-bin/gnats1/gnatsweb.cgi, cgi-parse-output reports: \ > > the CGI program /var/ppp/cgi-bin/gnats1/gnatsweb.cgi did not \ > > produce a valid header (program terminated without a valid CGI > > header. \ > > Check for core dump or other abnormal termination) > > > >Notes: > > (1) I've renamed gnatsweb.pl to gnatsweb.cgi. > > (2) I have multiple GNATS DBs. > > > >Thanks. > >K. Sekigawa
next reply other threads:[~2001-08-20 4:14 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-20 4:14 Kazunari Sekigawa [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-08-21 6:02 yngves 2001-08-21 3:04 Yngve Svendsen 2001-08-20 21:14 Kazunari Sekigawa 2001-08-19 17:14 Yngve Svendsen 2001-08-19 14:18 yngves 2001-08-16 0:58 yngves 2001-07-31 23:24 sekigawa
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=20010820111401.31273.qmail@sourceware.cygnus.com \ --to=sekigawa@neo.shinko.co.jp \ --cc=gnats-prs@sourceware.cygnus.com \ --cc=yngves@sources.redhat.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: linkBe 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).