Discussion:
[chora] Chora, Windows, rlog
Trip Kirkpatrick
2007-04-16 20:28:57 UTC
Permalink
Nothing I've found in the mailing list archives or elsewhere online has
solved or helped me move forward my Chora error.

It's the old "Failed to spawn rlog to retrieve file log information for
path/to/file,v", and I've tried a couple things already:
- Installed cygwin with the cvs and rcs packages, pointing the Chora
config to cygwin for all but the cvs.exe
- Loosening perms on the repository
- Making sure the paths don't have spaces in them
- Making sure the paths have forward slashes

I'm running a Windows Server 2003 environment.

Is it possible that the rlog error message is hiding a separate
exception? Is there somewhere to see more detailed errors? (I'm feeling
pretty stupid, 'cause I'm not getting logging to work either.)

Tk
--
Trip Kirkpatrick
SysAdmin / Sr. Programmer
Center for Language Study

e: trip.kirkpatrick at yale.edu
w: http://www.cls.yale.edu/
Chuck Hagenbuch
2007-04-20 20:23:19 UTC
Permalink
Post by Trip Kirkpatrick
Nothing I've found in the mailing list archives or elsewhere online has
solved or helped me move forward my Chora error.
It's the old "Failed to spawn rlog to retrieve file log information for
- Installed cygwin with the cvs and rcs packages, pointing the Chora
config to cygwin for all but the cvs.exe
- Loosening perms on the repository
- Making sure the paths don't have spaces in them
- Making sure the paths have forward slashes
I'm running a Windows Server 2003 environment.
Is it possible that the rlog error message is hiding a separate
exception? Is there somewhere to see more detailed errors? (I'm feeling
pretty stupid, 'cause I'm not getting logging to work either.)
It looks like we don't actually log any of the other potential info
right now. If any of this is useful please let us know and we can add
extra info to the PEAR error object.

You'll want to look around line 760 of VC/cvs.php in the
getBrowseInfo() function. After the exec() call, the $return_array and
$retval variables will have all the information we have on why the
function call failed. It's possible that if you have HTTP server logs
those will help also.

You can add a var_dump to that file, or add var_export($return_array,
$retval) to the PEAR_Error string.

-chuck

Loading...