By default, SmartSVN should be able to request the demo license automatically on the first start. If that fails, e.g., because the machine is not connected to the internet, you may request to get the demo license by email.
Smartsvn License File 22
After unpacking the tar file I had a dir called smartgithg-4_0_3. I moved this folder to my home directory and renamed it smartgit. After running ./bin/smartgithg.sh, another folder was created called .smartgit (note the . prefix).
I simply deleted the .smartgit folder (the dir tree with all the .xml files) and ran the ,/bin/smarthg.sh script again. The whole install process is repeated. Select the non commercial option when it appears.
I deleted the entire Config folder but preserved the files repositories.yml repository-cache repository-grouping.yml. after running SmartGit, it created the config folder (i think it used the config from an older build (to save things like my git credentials)), then i copied back my three files and i had all my repositories which is the most important info i needed.
To start the SVN MultiSite Plus replicator, follow these steps: Open a terminal window on the server and login with suitable file permissions.
Run the svn-multisite service, located in the init.d folder:lrwxrwxrwx 1 root root 37 May 9 10:37 svn-multisite -> /opt/svn-multisite-plus/bin/svn-multisite
Run the start script:[root@localhost init.d]# ./svn-multisite start20130520-164811 (24088) [INFO]: Starting WANdisco MultiSite Plus20130520-164811 (24088) [INFO]: Started replicator (24100)20130520-164811 (24088) [INFO]: Started ui (24110)20130520-164811 (24088) [INFO]: Number of errors: 020130520-164811 (24088) [INFO]: Number of warnings: 0
The two components of SVN MultiSite Plus; the replicator and the UI will start up. Read more about the svn-multisite init.d script
2. Shutting downTo shutdown:
Follow this procedure if you ever need to change your product license. You would need to do this if, for example, you needed to increase the number of subversion users or the number of replication nodes.
By default MultiSite's database directory (/opt/wandisco/svn-multisite-plus/replicator/database) is monitored - this is the location of MultiSite's prevayler database where all data and transactions files for replication are stored.
If the disk space available to a monitored resource is less than the value you have for a "Severe" event then the event is logged and MultiSite's replicator will shut down after a set interval of 10 minutes. You can configure the interval in application.properties file:
Monitors that you set up are stored within an XML file within the application's properties directory:/opt/svn-multisite/replicator/properties/ms-resource-monitoring-elements.xml In the event that this file can't be found, a substitute file is created in the temporary file space, "java.io.tmpdir". The default resource will then be applied:
This class clears selected prevaylers only, when the replicator is shut down. It does not clear all database instances, only those that are being restored during restore process.10. Restore SVN MultiSite DataUse the following procedure to restore SVN MultiSite Plus settings after reinstalling and starting a node: Shutdown the node
Run the following jar file:java -jar fsfsrestore.jar path/to/application.properties path/to/back-up-folderthe first argument, path/to/application.properties is /svn-multisite-plus/replicator/properties/application.properties
Make a text file containing ReplicationgroupAPIDTO XML (as above) called schedule.xmlcurl -u username:password -X PUT -d @schedule.xml 'schedule.xml' file gsg 97913c04-bbad-11e2-877a-028e03094f8d 1 14 N1 c0e486a0-bbab-11e2-863b-028e03094f8e true true 0 AV N3 5480f515-bbad-11e2-8301-028e03094f8c false true 0 T N2 478c766f-bbad-11e2-877a-028e03094f8d false true 0 AV Download the full sample Schedule.xml file.
You can change the current logging level by editing the logger properties file install-dir>/svn-multisite-plus/replicator/properties/logger.properties.You can see a sample logger.properties file.26. Consistency CheckThe consistency Check gives you a quick and easy check whether a selected repository remains in the same state across the nodes of a replication group. Follow these steps to check on consistency:
You can use the Set UUID command to ensure that a new repository that you've created has a UUID that matches with the other replicas:$ svnadmin setuuid /opt/Subversion/Repo0 67d41b33-3c7c-4ba0-8af1-119dbb0d42ba28. Repair an out-of-sync repositoryThere are a number of situations where a repository may be corrupted or lose sync with its other copies -- this could be the result of file/permission changes on the server. In such an event the node on which this copy is situated will stop replicating data for that repository (other repositories will be unaffected and should continue to replicate.) SVN MultiSite Plus has a repair tool that can be used to quickly get the repository repaired and replicating again. Login to a site, click on the REPOSITORIES tab. A repository that is out-of-sync will be flagged as Local RO (Read-only) which signifies that other replica may continue to update. Note that the Status for Repo2 is marked as "Stopped" instead of "Replicating". Click on the Repair button.Out of sync
Run Talkback using the following procedure: Login to the server with admin privileges. Navigate to the SVN MultiSite Plus's binary directory:/opt/wandisco/svn-multisite-plus/bin/talkback
Run talkback.[root@localhost bin]# ./talkback
You'll need to provide some information during the run: ===================== INFO ======================== The talkback agent will capture relevant configuration and log files to help WANdisco diagnose the problem you may be encountering.Is the replicator currently running [Y/n]: yPlease enter replicator admin username: adminUIusername Please enter replicator admin password: thepasswordhereretrieving details for repository "Repo1"retrieving details for repository "Repo3"retrieving details for repository "Repo4"retrieving details for repository "repo2"retrieving details for node "NodeSanFransisco"retrieving details for node "NodeAuckland"retrieving details for node "NodeParis"Please enter your WANdisco support FTP username (leave empty to skip auto-upload process):Skipping auto-FTP uploadTALKBACK COMPLETE--------------------------------------------------------------- Please upload the file: /opt/wandisco/svn-multisite-plus/talkback-201307171524-localhost.localdomain.tar.gz to WANdisco support with a description of the issue. Note: do not email the talkback files, only upload them via ftp or attach them via the web ticket user interface.--------------------------------------------------------------Note that you'll need to talk to Support about setting up access to WANdisco's Support FTP space.
Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system distributed as open source under the Apache License.[2] Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS).
The original development of Subversion used the Berkeley DB package.Subversion has some limitations with Berkeley DB usage when a program that accesses the database crashes or terminates forcibly. No data loss or corruption occurs, but the repository remains offline while Berkeley DB replays the journal and cleans up any outstanding locks. The safest way to use Subversion with a Berkeley DB repository involves a single server-process running as one user (instead of through a shared filesystem).[23] The Berkeley DB backend was deprecated in version 1.8.[24]
In 2004, a new storage subsystem was developed and named FSFS.It works faster than the Berkeley DB backend on directories with a large number of files and takes less disk space,due to less logging.[23]
The etymology of "FSFS" is based on Subversion's use of the term "filesystem" for its repository storage system.FSFS stores its contents directly within the operating system's filesystem, rather than a structured system like Berkeley DB.Thus, it is a "[Subversion] FileSystem atop the FileSystem".
Each revision in a Subversion filesystem has its own root, which is used to access contents at that revision. Files are stored as links to the most recent change; thus a Subversion repository is quite compact. The system consumes storage space proportional to the number of changes made, not to the number of revisions.
The Subversion filesystem uses transactions to keep changes atomic. A transaction operates on a specified revision of the filesystem, not necessarily the latest. The transaction has its own root, on which changes are made. It is then either committed and becomes the latest revision, or is aborted. The transaction is actually a long-lived filesystem object; a client does not need to commit or abort a transaction itself, rather it can also begin a transaction, exit, and then can re-open the transaction and continue using it. Potentially, multiple clients can access the same transaction and work together on an atomic change, though no existing clients expose this capability.
One important feature of the Subversion filesystem is properties: simple name=value pairs of text. Most properties occur on filesystem entries (i.e., files and directories). These are versioned just like other changes to the filesystem. The Subversion client reserves the 'svn:' prefix for built-in properties, but other names can be used to define custom properties. 2ff7e9595c
コメント