Yet Another Checkout Error. I've verified that the CVSROOT, username and password I configured my CVSMonitor repository with can indeed checkout the module from the commandline. The error message in the server logs (iPlanet, not Apache) reads:
[23/Feb/2004:14:30:42] failure (10256): for host 10.251.6.73 trying to GET /cgi-bin/cvsmonitor/cvsmonitor.pl, cgieng_scan_headers reports: the CGI program /lcl/dev/data/htdocs/cgi/cvsmonitor/cvsmonitor.pl did not produce a valid header (name without value: got line "begin failed--compilation aborted at (eval 33) line 1.")
It strikes me as odd that cvsmonitor.pl is returning an unformatted Perl error message since 1) the script runs fine from the commandline and 2) I've moved CGI::Carp qw{fatalsToBrowser} up directly underneath the #! line. Why isn't the error being reported to the browser (ie, with a valid HTTP 1.1 header and all)?
Finally, as best I can tell, no logs are being generated.
This is with CVSMonitor 0.6.2. I can list the version numbers of our installed modules if needed; all were flagged as green during the installations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I've tested with the latest (0.6.3 beta 3) and I get basically the same error:
[02/Mar/2004:08:31:48] failure (10256): for host 10.251.6.73 trying to GET /cgi-bin/cvsmonitor/cvsmonitor.pl, cgieng_scan_headers reports: the CGI program /lcl/dev/data/htdocs/cgi/cvsmonitor/cvsmonitor.pl did not produce a valid header (name without value: got line "begin failed--compilation aborted at (eval 34) line 1.")
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One thing I forgot to add; I noticed in the documentation the following qualifier: "There is a bug against 'greater than one level deep' paths at this time. Please use with caution." The problem is that most of our modules are located greater than one level deep. I've read through the bug (800496 I presume), and I tried checking out a module that was only one level deep, but I still got the same error, so the two appear to be unrelated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now that 0.6.3 is out and we don't have to maintain compatibility any more, some more significant changes should start to appear, including replacing the error message capture code.
This will hopefully result in more detailed error messages, from which we can get a much better idea of what these YACE are being caused by.
If you wanted to add a "monitor" to the devel release branch on CVS Monitor, you will be notified when a reasonably useful 0.7 devel release is available.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yet Another Checkout Error. I've verified that the CVSROOT, username and password I configured my CVSMonitor repository with can indeed checkout the module from the commandline. The error message in the server logs (iPlanet, not Apache) reads:
[23/Feb/2004:14:30:42] failure (10256): for host 10.251.6.73 trying to GET /cgi-bin/cvsmonitor/cvsmonitor.pl, cgieng_scan_headers reports: the CGI program /lcl/dev/data/htdocs/cgi/cvsmonitor/cvsmonitor.pl did not produce a valid header (name without value: got line "begin failed--compilation aborted at (eval 33) line 1.")
It strikes me as odd that cvsmonitor.pl is returning an unformatted Perl error message since 1) the script runs fine from the commandline and 2) I've moved CGI::Carp qw{fatalsToBrowser} up directly underneath the #! line. Why isn't the error being reported to the browser (ie, with a valid HTTP 1.1 header and all)?
Finally, as best I can tell, no logs are being generated.
This is with CVSMonitor 0.6.2. I can list the version numbers of our installed modules if needed; all were flagged as green during the installations.
Always test with the latest version. There's 14 months worth of small internal changes to 0.6.3 that make things more likely to work.
OK, I've tested with the latest (0.6.3 beta 3) and I get basically the same error:
[02/Mar/2004:08:31:48] failure (10256): for host 10.251.6.73 trying to GET /cgi-bin/cvsmonitor/cvsmonitor.pl, cgieng_scan_headers reports: the CGI program /lcl/dev/data/htdocs/cgi/cvsmonitor/cvsmonitor.pl did not produce a valid header (name without value: got line "begin failed--compilation aborted at (eval 34) line 1.")
One thing I forgot to add; I noticed in the documentation the following qualifier: "There is a bug against 'greater than one level deep' paths at this time. Please use with caution." The problem is that most of our modules are located greater than one level deep. I've read through the bug (800496 I presume), and I tried checking out a module that was only one level deep, but I still got the same error, so the two appear to be unrelated.
Now that 0.6.3 is out and we don't have to maintain compatibility any more, some more significant changes should start to appear, including replacing the error message capture code.
This will hopefully result in more detailed error messages, from which we can get a much better idea of what these YACE are being caused by.
If you wanted to add a "monitor" to the devel release branch on CVS Monitor, you will be notified when a reasonably useful 0.7 devel release is available.