To assist in a speedy resolution of problems with AccuRev usage or performance, AccuRev Customer Support personnel may ask you to provide data that you may not be accustomed to gathering on a day-to-day basis. The most frequently requested items are listed below, with instructions on how to gather the data. In your initial email communication with Customer Support, please include the data item(s) that you know (or suspect) are related to your specific issue.
1. Run the accurev backup command. This command will back up your metadata into the AccuRev site_slice/backup directory.
2. Use accurev show slices to find the location of the relevant depot directory (slice).
4. tar your site_slice directory (including the backed-up metadata from step 1). Example:
5. tar the relevant depot directory (slice), but exclude the data subtree. (The data subtree contains the content of the files you have placed into AccuRev source control; please do not send it to us!) Example:
6.
8. Send the gzipped files (.tar.gz suffix) to Customer Support. We recommend using FTP rather than email, since the files may be too large for your outgoing email server. Please contact support@accurev.com to obtain a username and password for our FTP server.
1. Run the accurev backup command. This command will back up your metadata into the AccuRev site_slice/backup directory.
2. Use accurev show slices to find the location of the relevant depot directory (slice).
4. Create a ZIP archive of the entire site_slice directory (including the backed-up metadata from step 1). Typically, it is C:\Program Files\AccuRev\storage\site_slice.
5. Create a ZIP archive of the relevant depot directory (slice). Typically, it's a subdirectory of C:\Program Files\AccuRev\storage\depots. Remove the data subtree from the ZIP archive. (The data subtree contains the content of the files you have placed into AccuRev source control; please do not send it to us!)
7. Send the ZIP files to Customer Support. We recommend using FTP rather than email, since the files may be too large for your outgoing email server. Please contact support@accurev.com to obtain a username and password for our FTP server.
4. Get output of accurev info on the AccuRev Server machine.
5. Copy (ZIP or tar file) all AccuRev Server logs, located in subdirectory .../storage/site_slice/logs. Search for any messages that might be the cause of your issue: disk failure, power outage, etc.
8. Get output of maintain dbcheck.If you experience your problem while running the AccuRev GUI, then running the GUI in Java debug mode can help diagnose and further troubleshoot your problem. Running in debug mode is also useful for monitoring the commands that the GUI sends to the AccuRev Server. This can help with scripting efforts, for example:java -Daccurev.debug.acapi -cp "oro.jar;xercesImpl.jar;xml-apis.jar;fw.jar" fw.MainApp$acjre -Daccurev.debug.acapi -Daccurev.debug.env -classpath "oro.jar:xercesImpl.jar:xml-apis.jar:fw.jar" fw.MainAppNote that if you are running AccuRev 3.7 or earlier, the class path specified in the command should be "oro.jar, xerces.jar, fw.jar". If AccuRev is not installed in the standard location, you will also need to specify the correct path in your commands.You can diagnose authentication problems with the accurev secinfo command:The user is allowed to perform operations on streams except where permissions require an authenticated user.How can you get the version information about the AccuRev Server without having to log into the server machine? You can perform either of the following operations on any AccuRev client machine:
• To get the major/minor/patch version numbers of the AccuRev Server, use the accurev xml command:
1. Create a file (say, ver.xml), containing this very short XML document:
2. Submit this file as an argument to the xml command:<serverInfo>
<serverVersion
major="4"
minor="7"
patch="2"/>
<handleCount>10</handleCount>
</serverInfo>If you are reporting a problem with an AccuRev integration with a third-party IDE, send to Customer Support:
2. The steps required to reproduce the problem. Be sure to include the type of project you're working with in the IDE and the location of the AccuRev workspace you're accessing through the IDE.
•
• The keys.txt file (in .../storage/site_slice). [NOTE: keys.txt licensing is no longer supported as of AccuRev 5.4.]
• Output from accurev info, executed on the AccuRev Server machine.
• Output from accurev show users.
• A copy of the acserver.cnf file from both the master server and the replica server.
• A copy of the acserver.log file from both the master server and the replica server.
2. What exactly was the user trying to do? Does the performance problem occur with other users, on different client machines? Or is it a common issue on the same machine?
3.
7. Is the user's home directory on a remote disk? If so, consider moving the home directory so that it is on the machine where the AccuRev client software runs.
• Complete AccuRev server logs (in .../storage/site_slice/logs)
• Two samples of output from accurev diag, run on the AccuRev Server machine in the depot storage directory.
• Two samples of output from accurev diag, run on the client machine in the user's workspace directory.
• Output from accurev show triggers.
• The contents of the trigger script files with the names listed below, located anywhere under the storage directory on the AccuRev Server machine:The filenames might include a suffix, such as .bat on Windows.
1. Create a file (say, tasks.xml), containing this very short XML document:
2. Submit this file as an argument to the xml command:The contents of tasklist.out will resemble this example:<tasklist>
<task>
<task_id>1299</task_id>
<task_name>promote</task_name>
<user>john</user>
<host>192.168.89.222</host>
<status>1</status>
<starttime>2006/07/25 14:42:49</starttime>
<seconds_on_server>2</seconds_on_server>
<depot_write_lock>true</depot_write_lock>
<progress_counter
counter="0"
count="6"
max_count="11"/>
<progress_counter
counter="1"
count="200"
max_count="900"/>
</task>
<task>
<task_id>1300</task_id>
<task_name>xml</task_name>
<user>john</user>
<host>192.168.89.222</host>
<status>1</status>
<starttime>2006/07/25 14:42:51</starttime>
<seconds_on_server>0</seconds_on_server>
</task>
</tasklist>If you cannot see an element that you believe that exists, there is a good chance that your AccuRev administrator has set element-level security using the eacl command, and you are being denied access to the element (or its container directory). For more information about EACLs and their behavior, see Element ACLs (EACLs) on page 252.If you perform an Update, and the version displayed in the File Browser is correct but the content of the file does not appear to have been updated, this is typically due to a timestamp problem. It usually occurs when a file is changed outside of the workspace and then copied back in. The timestamp of the file that was dropped back into the workspace has a date and time stamp older than the date and time stamp of the file in the workspace. To update the file, temporarily uncheck Timestamp Optimization and perform the Update again. For more information, see “Validity of Traditional Timestamp Optimization” in the AccuRev Administrator’s Guide for more information.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |