Difference between revisions of "GHN clean 350"

Latest revision as of 12:35, 20 February 2013

1) Download the upgrade script from

wget http://svn.research-infrastructures.eu/public/d4science/gcube/trunk/ghn-distribution/upgrade-scripts/clean-ghn-3-6-0.sh

and make it executable:

chmod 700 clean-ghn-3-5-0.sh

2) Verify that the GLOBUS_LOCATION environment variable is correctly set

echo $GLOBUS_LOCATION

3) Run the upgrade script with the following arguments:

./clean-ghn-3-5-0.sh <port> restart

4) Verify the upgrade operation using the infrastructure monitoring tools

http://www.d4science.org/web/guest/monitor

@@ Line 1: / Line 1: @@
 ) Download the upgrade script from
-  wget http://svn.research-infrastructures.eu/public/d4science/gcube/trunk/ghn-distribution/upgrade-scripts/clean-ghn-3-4-0.sh
+  wget http://svn.research-infrastructures.eu/public/d4science/gcube/trunk/ghn-distribution/upgrade-scripts/clean-ghn-3-6-0.sh
 and make it executable:
 <pre>
-chmod 700 upgrade-ghn-3-4-0.sh
+chmod 700 clean-ghn-3-5-0.sh
 </pre>
 ) Verify that the GLOBUS_LOCATION environment variable is correctly set
@@ Line 10: / Line 10: @@
 ) Run the upgrade script with the following arguments:
 * <port>: The port where the container runs.
-* <restart/norestart>: tells if the container has to be restarted or not after the upgrade
+* restart:  the container has to be restarted  after the upgrade
-  ./upgrade-ghn-3-4-0.sh <port> <restart/norestart>
+  ./clean-ghn-3-5-0.sh <port> restart
 ) Verify the upgrade operation using the infrastructure monitoring tools
-  http://monitor.d4science.research-infrastructures.eu
+  http://www.d4science.org/web/guest/monitor