So, you're having a problem with the campus subversion servers.
Here are the things that you can do to help us solve your problem quicker.
Tell us:
- What operating system you are running, including the version number?
For example:
- Windows XP, service pack 3
- Red Hat Enterprise Linux 5, 64bit
- Ubuntu Linux 9, 32bit
- What subversion client and version are you running?
For example:
- Red Hat default client version 1.6.5
- TortoiseSVN version 1.6.7
- What is the IP address of the machine you are coming from?
- Explain the problem
- Does the problem only happen on certain repositories
- Does the problem happen every time
- Does the problem only happen at certain times
- What exactly are you doing when the problem happens
- List any error messages received
- If there are no error messages, then please state that too
- If at all possible, please tell us the exact error message
- Tell us when you first noticed the problem and the last time you experienced this problem
For example:
- I had the problem yesterday at 3:17pm and again at 4:03pm.
- I've had the problem every time I've used subversion since 2010/01/23
- It doesn't happen every time, but it appeared to start the beginning of March
- Send any debug output you are able to gather
This is probably easier for people working on linux systems.
If you edit ~/.subversion/servers, look for the configuration block titled "global"
and after it, place the following line:neon-debug-mask = 130
Then try to recreate the problem. The subversion client will output a lot of
debugging output so you may want to capture this with another program, say script.
<h3>Linux Users</h3>
The following commands will give us most of the data that we need.
uname -a
svn --version
ldd `which svn`
ldd libneon.so # You will need to figure out which libneon to use by looking at the
- output of the previous command.
/sbin/ifconfig -a