CollabNet Subversion Edge windows版 问题详解

Windows Installation Information#

The Windows installer is a standard MSI-based Windows installer. We are using Advanced Installer by Caphyon to author the installation process. Running the installer is simple, the only option during the wizard is to select the location to install the product. We default the path to C:\csvn. We chose this as the default, as opposed to using C:\Program Files to minimize issues around dealing with paths that have spaces in the name and also to avoid Windows User Account Control (UAC) issues on Vista and later OS. We can test these scenarios and resolve issues in the product but as you start adding hook scripts and other integrations to Subversion it is an issue you are always dealing with. So we chose a default path that avoids some of these problems and makes the overall experience easier for the administrator.

Things we do during the install process#

Here are some of the things we do during the install process, beyond simply copying the bits to your drive.

1. Check for and install a valid Java 6 runtime. This is handled as an installation pre-requisite automatically. If a JRE is not found, we run the Sun/Oracle installer.
2. Set/replace the JAVA_HOME environment variable to point to the Java 6 runtime
3. Install Python 2.5 runtime, including mod_python and Windows extensions
4. Set/replace the registry entries for Python2.5 to point to the version we install
5. Set/replace the PYTHONHOME environment variable to point to our Python 2.5 runtime
6. Add Windows service for the CollabNet Subversion Edge Console
7. Add Windows service for the CollabNet Subversion Server (Apache)
8. Add Windows Firewall exceptions for the Apache executable and the default Subversion Edge port (3343)
9. Create a Start Menu shortcut to open browser to http://localhost:3343/csvn
10. Add the csvn\bin and csvn\Python25 folders to beginning of PATH

Troubleshooting Problems#

The main issues that customers experience on a new install are related to the services that we install. Either they fail to install at all or they fail to start. This will give you some information on what to look for to resolve any problems you are having.

Server never says it is Ready

After running the install the web page that we bring up to show you the server is starting never says it is Ready. This means that either the service never installed or it did not start. Please do the following:

Check if the service installed

Open the Windows Services control panel and see if there is a CollabNet Subversion Edge service. If you prefer to check from a command line try this:

C:\>sc query CSVNConsole

SERVICE_NAME: CSVNConsole
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

This shows a running service. This is what you would see if the service is not installed:

C:\>sc query CSVNConsole
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.

Service Not Installed

The primary reason we have seen for the service not being installed is that Java is not in your PATH. The Sun/Oracle JRE normally adds java.exe to the Windows system folder, but there have been some users that install the JDK and do not install the JRE so they do not have anything in PATH. To check, just run this command:

C:\>java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) Client VM (build 19.1-b02, mixed mode, sharing)

If you get some output, then it is in your PATH. You can install the service manually by going to the folder C:\csvn\svcwrapper\bat and running the script installService.bat

C:\>cd \csvn\svcwrapper\bat

C:\csvn\svcwrapper\bat>installService.bat

C:\csvn\svcwrapper\bat>if . == . goto skip

Apr 14, 2011 5:37:43 AM org.apache.commons.vfs.VfsLog info
INFO: Using "C:\DOCUME~1\markphip\LOCALS~1\Temp\1\vfs_cache" as temporary files
store.
Service CSVNConsole installed

You should now be able to see the service and start it. You can run the script startService.bat to start it, or you can start it from the Services Control Panel.

Service Exists But Will not Start

The service exists but it fails to start. The main cause of this seems to be that Java is not in PATH. Use the technique shown before to check if it is in PATH. Install the JRE if you do not have Java in your PATH an that should resolve the problem. If it doesn't, there are some logs you can check:

C:\csvn\appserver\wrapper.log.0

This log file shows the output from starting the service. There would not typically be any errors in this log file, but it is worth checking.

C:\csvn\data\logs\console_YYYY_MM_DD.log

This log file has the output from the actual application when it starts. Look for error messages and they should give a clue as to why the app did not start. Mail the log file to our discussion forum if you need help.

Problems we are aware of#

Here are some issues we are aware with the install.

1. Trying to use ViewVC can give an Internal Server Error - 500. This problem is typically caused because you have conflicting DLL's in your Windows system32 folder. We did not want our installer to mess around with this folder, so we do not try to fix your system. In our own testing, the most common cause of this problem was if you have previously installed ActiveState Python 2.5. Their installer puts some DLL's that begin with "py" in the system32 folder. Moving these to a temp folder immediately solves the problem. We are using the Python distribution from python.org and the DLL's appear to conflict with one another. A similar problem can occur if you have conflicting OpenSSL DLL's in the system32 folder. These are the files (libeay32.dll and ssleay32.dll). Typically, rebooting the server after installing our application resolves this problem because we put our folder first in the PATH. You could also remove the DLL's.

1. 64-bit Windows. We are providing a native Windows 64-bit installer and we check for and install a native 64-bit JRE. However, the Apache and Subversion native binaries that we are currently providing are still 32-bit. We will be updating these to true 64-bit binaries in the near future. By using the 64-bit installer, you will be connected to the right package repository to receive these updates automatically in the future. We are also fully testing the installer and binaries on 64-bit versions of Windows 2003 and 2008.

http://whxhz.iteye.com/blog/1294253