* CVS transient failure
2000-12-30 6:08 CVS transient failure Zack Weinberg
@ 2000-06-02 18:58 ` Zack Weinberg
2000-12-30 6:08 ` Frank Ch. Eigler
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Zack Weinberg @ 2000-06-02 18:58 UTC (permalink / raw)
To: overseers
CVS spat out the following:
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
I tried it again and it worked; the disk is not full and the directory
is writable, so I don't know what went wrong. I note there are an
awful lot of stale files in that directory.
It would be nice if that script read
open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
instead of
open(FILE, ">$filename") || die("Cannot open $filename, stopped");
-- then you'd be told the actual error return from open(2) and have a
chance of figuring out what happened.
zw
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 ` Jason Molenda
@ 2000-06-02 19:08 ` Jason Molenda
0 siblings, 0 replies; 8+ messages in thread
From: Jason Molenda @ 2000-06-02 19:08 UTC (permalink / raw)
To: Zack Weinberg; +Cc: overseers
On Fri, Jun 02, 2000 at 06:58:08PM -0700, Zack Weinberg wrote:
> CVS spat out the following:
>
> Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
> stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
> cvs server: Pre-commit check failed
Yeah, it exists:
-rw-r--r-- 1 pme libstdc+ 36 May 24 11:35 #gcc.lastdir.12290
I've known about a (ahem) oversight in all the projects' commitinfo
setups for a while now, figuring it wouldn't cause problems.
The commitinfo for every repo runs the commit_prep script for all
cvs commits ... but they don't run the log_accum script (which I
assume reliably cleans these things up) if the check-in is related
to the web pages - a separate script to update the web pages is
run for that. So each web page checkin will leave behind a little
commit_prep doodie.
An entry like
htdocs /bin/true
before the DEFAULT entry in repositories' CVSROOT/commitinfo file
would probably take care of the problem, but it'd have to be done
in every repository's setup.
The REAL problem here is that sourceware is too reliable and doesn't
reboot often enough. We should add some bloated software with
memory leaks to cause the system to reboot every week or so. ;-)
Jason (who should be ashamed :)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 ` Frank Ch. Eigler
@ 2000-06-02 19:11 ` Frank Ch. Eigler
0 siblings, 0 replies; 8+ messages in thread
From: Frank Ch. Eigler @ 2000-06-02 19:11 UTC (permalink / raw)
To: Zack Weinberg; +Cc: overseers
Hi -
On Fri, Jun 02, 2000 at 06:58:08PM -0700, Zack Weinberg wrote:
> CVS spat out the following:
> Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
> [...]
>
> I tried it again and it worked; the disk is not full and the directory
> is writable, so I don't know what went wrong. I note there are an
> awful lot of stale files in that directory.
That's exactly what it is: #gcc.lastdir.12290 already exists under a
different user. It looks like the UNIX pid rolls over more frequently
than the junk #*.lastdir files are cleaned.
Good news: the probability of you hitting another stale file is pretty
low right now - ~1/300 (# stale files / sizeof pid space), and will rise
at this sort of rate (inverse exponential?) every month.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5OGlEVZbdDOm/ZT0RAc6lAJsE8x4DlLhA1CEJzHUHN9WNkPhP+gCeOx6p
/+AnoUYrhByBPK0BO0gpy84=
=lKoS
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 ` Jim Kingdon
@ 2000-06-03 11:39 ` Jim Kingdon
0 siblings, 0 replies; 8+ messages in thread
From: Jim Kingdon @ 2000-06-03 11:39 UTC (permalink / raw)
To: zack; +Cc: overseers
> It would be nice if that script read
> open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
Done (but untested). If I broke something, I'm sure someone will let
me know :-).
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 CVS transient failure Zack Weinberg
2000-06-02 18:58 ` Zack Weinberg
@ 2000-12-30 6:08 ` Frank Ch. Eigler
2000-06-02 19:11 ` Frank Ch. Eigler
2000-12-30 6:08 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
3 siblings, 1 reply; 8+ messages in thread
From: Frank Ch. Eigler @ 2000-12-30 6:08 UTC (permalink / raw)
To: Zack Weinberg; +Cc: overseers
Hi -
On Fri, Jun 02, 2000 at 06:58:08PM -0700, Zack Weinberg wrote:
> CVS spat out the following:
> Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
> [...]
>
> I tried it again and it worked; the disk is not full and the directory
> is writable, so I don't know what went wrong. I note there are an
> awful lot of stale files in that directory.
That's exactly what it is: #gcc.lastdir.12290 already exists under a
different user. It looks like the UNIX pid rolls over more frequently
than the junk #*.lastdir files are cleaned.
Good news: the probability of you hitting another stale file is pretty
low right now - ~1/300 (# stale files / sizeof pid space), and will rise
at this sort of rate (inverse exponential?) every month.
- FChE
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5OGlEVZbdDOm/ZT0RAc6lAJsE8x4DlLhA1CEJzHUHN9WNkPhP+gCeOx6p
/+AnoUYrhByBPK0BO0gpy84=
=lKoS
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 CVS transient failure Zack Weinberg
` (2 preceding siblings ...)
2000-12-30 6:08 ` Jim Kingdon
@ 2000-12-30 6:08 ` Jason Molenda
2000-06-02 19:08 ` Jason Molenda
3 siblings, 1 reply; 8+ messages in thread
From: Jason Molenda @ 2000-12-30 6:08 UTC (permalink / raw)
To: Zack Weinberg; +Cc: overseers
On Fri, Jun 02, 2000 at 06:58:08PM -0700, Zack Weinberg wrote:
> CVS spat out the following:
>
> Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
> stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
> cvs server: Pre-commit check failed
Yeah, it exists:
-rw-r--r-- 1 pme libstdc+ 36 May 24 11:35 #gcc.lastdir.12290
I've known about a (ahem) oversight in all the projects' commitinfo
setups for a while now, figuring it wouldn't cause problems.
The commitinfo for every repo runs the commit_prep script for all
cvs commits ... but they don't run the log_accum script (which I
assume reliably cleans these things up) if the check-in is related
to the web pages - a separate script to update the web pages is
run for that. So each web page checkin will leave behind a little
commit_prep doodie.
An entry like
htdocs /bin/true
before the DEFAULT entry in repositories' CVSROOT/commitinfo file
would probably take care of the problem, but it'd have to be done
in every repository's setup.
The REAL problem here is that sourceware is too reliable and doesn't
reboot often enough. We should add some bloated software with
memory leaks to cause the system to reboot every week or so. ;-)
Jason (who should be ashamed :)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: CVS transient failure
2000-12-30 6:08 CVS transient failure Zack Weinberg
2000-06-02 18:58 ` Zack Weinberg
2000-12-30 6:08 ` Frank Ch. Eigler
@ 2000-12-30 6:08 ` Jim Kingdon
2000-06-03 11:39 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
3 siblings, 1 reply; 8+ messages in thread
From: Jim Kingdon @ 2000-12-30 6:08 UTC (permalink / raw)
To: zack; +Cc: overseers
> It would be nice if that script read
> open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
Done (but untested). If I broke something, I'm sure someone will let
me know :-).
^ permalink raw reply [flat|nested] 8+ messages in thread
* CVS transient failure
@ 2000-12-30 6:08 Zack Weinberg
2000-06-02 18:58 ` Zack Weinberg
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Zack Weinberg @ 2000-12-30 6:08 UTC (permalink / raw)
To: overseers
CVS spat out the following:
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
I tried it again and it worked; the disk is not full and the directory
is writable, so I don't know what went wrong. I note there are an
awful lot of stale files in that directory.
It would be nice if that script read
open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
instead of
open(FILE, ">$filename") || die("Cannot open $filename, stopped");
-- then you'd be told the actual error return from open(2) and have a
chance of figuring out what happened.
zw
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2000-12-30 6:08 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-12-30 6:08 CVS transient failure Zack Weinberg
2000-06-02 18:58 ` Zack Weinberg
2000-12-30 6:08 ` Frank Ch. Eigler
2000-06-02 19:11 ` Frank Ch. Eigler
2000-12-30 6:08 ` Jim Kingdon
2000-06-03 11:39 ` Jim Kingdon
2000-12-30 6:08 ` Jason Molenda
2000-06-02 19:08 ` Jason Molenda
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).