Difference: RestoreVOOnSlaveServer (1 vs. 2)

Revision 22012-01-05 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="UseCases"
Deleted:
<
<
 

VOMS: How to restore a VO on a slave server

If something goes wrong with a slave VOMS server and nothing else you can try, you have to restore the database on the slave. For example, consider to have a problem with argo VO database.

Line: 31 to 30
 /etc/init.d/voms restart argo
Deleted:
<
<
-- SergioTraldi - 2012-01-04
 \ No newline at end of file

Revision 12012-01-04 - SergioTraldi

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="UseCases"

VOMS: How to restore a VO on a slave server

If something goes wrong with a slave VOMS server and nothing else you can try, you have to restore the database on the slave. For example, consider to have a problem with argo VO database.

* Delete the VO (including the database)

/usr/sbin/voms-admin-configure.py remove --undeploy-database --vo=argo

* Re-create the VO

/usr/sbin/voms-admin-configure.py install --vo=argo --dbtype mysql

* Start the VO

/etc/init.d/voms-admin start argo

* Configure the replica (assuming that your /etc/my.cnf is OK)

/root/voms-scripts/next_replicas.sh --master-db=voms_argo --db=voms_argo

* Restart the VO

/etc/init.d/voms restart argo

-- SergioTraldi - 2012-01-04

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback