Changes between Version 3 and Version 4 of Doc/SCDB/Server

Timestamp:

May 19, 2007, 4:21:25 PM (18 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Doc/SCDB/Server

@@ -55 +55 @@
 == Troubleshooting Server-side Scripts ==
 
-If there is a problem with deployment after entering command `ant deploy`, people listed in `NOTIFY` variable of hook scripts should receive an email describing the problem. Note than `ant deploy` reports a success even if something wrong happens during deployment : `ant` success or failure only reflects Subversion commit (implied by `ant deploy`) status.
+If there is a problem during deployment, after entering command `ant deploy`, people listed in `NOTIFY` variable of hook script should receive an email describing the problem. With some misconfiguration, it can happen you don't receive an email about the deployment failure. 
 
-With some misconfiguration, it can happen you don't receive an email about the deployment failure. Or you may want to troubleshoot the problem. To achieve this, it is possible to execute manually the deployment script, `build-tag.pl`. For this you must proceed as follow (assuming your SCDB local cache is in `/root/quattor/svncache` and `build-tag.pl` is installed in `/root/quattor/scripts`) :
+''Note : `ant deploy` reports a success even if something wrong happens during deployment : `ant` success or failure only reflects Subversion commit (implied by `ant deploy`) status.''
+
+To troubleshoot server side configuration problems, it is necessary to execute manually the server scripts. This is a two-step processes :
+ 1. Check successful execution of deployment script, `build-tag.pl`.
+ 1. Check successful execution of SVN hook script.
+
+=== Troubleshooting deployment script ===
+
+''To troubleshoot deployment script, `build-tag.pl`, you must log on the Quattor server as the user configured to run deployment script (generally `root`).''
+
+The step-by-step procedure to troubleshoot deployment script (examples below assume it is in default location `/root/quattor/scripts`) is :
+ 1. Look in `/etc/build-tag.conf', if it exists, location of SVN cache on the Quattor server. Default location (`/root/quattor/svncache`) is assumed in following examples : replace with the appropriate location for your site.
+ 1. Check the last tag checked out with the following command :
 {{{
 svn info /root/quattor/svncache
----> look at the current tag name, everything after /tags in the URL
-svn update /root/quattor/svncache
----> Check it completes successfully
+---> look at the current tag name, everything after /tags/ in the URL (without leading /)
+}}}
+ 1. Check the tag has been successfully checked out. If the following command updates anything, it means the previous attempt to switch to this tag was unsuccessful. If the command fails again, retry it until it is successful. Failure to switch to a tag is generally related to a Subversion server problem, not to Quattor itself : check Subversion server logs for more information.
+{{{
+svn update
+}}}
+ 1. Try to redeploy the same tag with the following command :
+{{{
 /root/quattor/scripts/build-tag.pl TAG-VALUE
 }}}
+
+If SVN cache is empty (not recognized as a valid SVN working copy by `svn info`), you need to identify last tag in `tags` branch of Quattor SCDB repository using `svn ls`.
+
+=== Troubleshooting SVN hook script ===
+
+Most of the deployment problems, after initial configuration, are related to deployment script. As the hook script mainly launches the deployment script, it is important complete previous check before troubleshooting SVN hook script.