Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
Directory Tree
Check_Svn
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Overview
Checks a Subversion (SVN) repository using the svn, http or https protocols.
It uses the svn command line client to fetch a directory listing from the subversion server. Use --verbose once to display the directory listing at the end of the status output on one line.
Takes various options including username, password, protocol, port, directory, verbosity, timeout limit and timing information on how long the test took. Follows Nagios coding standards with built in default timeouts, -vvv verbosity debugging for full dump output for troubleshooting etc.
Basic Usage:
check_svn -H server1
SVN OK: svn repository online - directory listing successful
check_svn -H server2
SVN CRITICAL: Error connecting to svn server - Can't connect to host 'server2': Connection refused
More Usage Examples
check_svn -H server2 --port=3690 --username=hari --password=somethingsecret --verbose
SVN OK: svn repository online - directory listing: dir1 dir2 dir3 file1 file2 file3...
./check_svn -H svn.collab.net --http --dir /repos/svn --timing
SVN OK: svn repository online - directory listing successful. Test completed in 2.712 seconds
./check_svn -H svn.collab.net --http --dir /repos/svn -v
SVN OK: svn repository online - directory listing: README branches/ developer-resources/ mk.xiv/ svn-logos/ tags/ trunk/
Options
There are several switches to control the test
See
./check_svn --help
For full details
Other
NOTE: Some people have had problems with the following message:
SVN CRITICAL: Error connecting to svn server - Can't open file '/root/.subversion/servers': Permission denied
This is a Nagios environment issue rather than a plugin issue. To fix it, set the HOME environment variable explicitly to the home directory of the nagios user in your commands configuration file:
command_line export HOME=/home/nagios && $USER1$/check_svn .......
Support
For support, feature requests or bug fixes contact me at hpsekhon at googlemail dot com.
Checks a Subversion (SVN) repository using the svn, http or https protocols.
It uses the svn command line client to fetch a directory listing from the subversion server. Use --verbose once to display the directory listing at the end of the status output on one line.
Takes various options including username, password, protocol, port, directory, verbosity, timeout limit and timing information on how long the test took. Follows Nagios coding standards with built in default timeouts, -vvv verbosity debugging for full dump output for troubleshooting etc.
Basic Usage:
check_svn -H server1
SVN OK: svn repository online - directory listing successful
check_svn -H server2
SVN CRITICAL: Error connecting to svn server - Can't connect to host 'server2': Connection refused
More Usage Examples
check_svn -H server2 --port=3690 --username=hari --password=somethingsecret --verbose
SVN OK: svn repository online - directory listing: dir1 dir2 dir3 file1 file2 file3...
./check_svn -H svn.collab.net --http --dir /repos/svn --timing
SVN OK: svn repository online - directory listing successful. Test completed in 2.712 seconds
./check_svn -H svn.collab.net --http --dir /repos/svn -v
SVN OK: svn repository online - directory listing: README branches/ developer-resources/ mk.xiv/ svn-logos/ tags/ trunk/
Options
There are several switches to control the test
See
./check_svn --help
For full details
Other
NOTE: Some people have had problems with the following message:
SVN CRITICAL: Error connecting to svn server - Can't open file '/root/.subversion/servers': Permission denied
This is a Nagios environment issue rather than a plugin issue. To fix it, set the HOME environment variable explicitly to the home directory of the nagios user in your commands configuration file:
command_line export HOME=/home/nagios && $USER1$/check_svn .......
Support
For support, feature requests or bug fixes contact me at hpsekhon at googlemail dot com.
Reviews (3)
bylmichoux, June 2, 2014
All options I was expecting are in there.
Good job mate.
Ludovic
Good job mate.
Ludovic
bysunnysthakur, March 4, 2013
Worked on Nagios alerts for space issues on servers.
When i am going to add below line in command.cfg on nagios server
command_line export HOME=/home/nagios && $USER1$/check_svn
below error is coming while compile the nagios.cfg file
Reading configuration data...
Read main config file okay...
Processing object config file '/etc/nagios/objects/commands.cfg'...
Error: Unexpected token or statement in file '/etc/nagios/objects/commands.cfg' on line 26.
Error processing object config files!
***> One or more problems was encountered while processing the config files...
Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
When i am going to add below line in command.cfg on nagios server
command_line export HOME=/home/nagios && $USER1$/check_svn
below error is coming while compile the nagios.cfg file
Reading configuration data...
Read main config file okay...
Processing object config file '/etc/nagios/objects/commands.cfg'...
Error: Unexpected token or statement in file '/etc/nagios/objects/commands.cfg' on line 26.
Error processing object config files!
***> One or more problems was encountered while processing the config files...
Check your configuration file(s) to ensure that they contain valid
directives and data defintions. If you are upgrading from a previous
version of Nagios, you should be aware that some variables/definitions
may have been removed or modified in this version. Make sure to read
the HTML documentation regarding the config files, as well as the
'Whats New' section to find out what has changed.
Thank you very much!
It worked perfect!
It worked perfect!