- General information
- Data readiness
- Calibration
- Databases
- Frequently Asked Questions
- How-To: user section
- How-To: admin section
- How-To: subsystem coordinator
- Online Databases
- Offline Databases
- FileCatalog Databases
- Software Infrastructure Databases
- Maintenance
- DB & Docker
- Development
- Test
- Quality Assurance
- Grid and Cloud
- Infrastructure
- Machine Learning
- Offline Software
- Production
- S&C internal group meetings
- Test tree
HOW-TO: create a new Run RunLog browser instance and retire previous RunLog
Updated on Mon, 2009-11-09 08:53. Originally created by testadmin on 2009-01-15 15:36.
Under:
1. New RunLog browser:
- Copy the contents of the "/var/www/html/RunLogRunX" to "/var/www/html/RunLogRunY", where X is the previous Run ID, and Y is the current Run ID
- Change symlink "/var/www/html/RunLog" pointing to "/var/www/html/RunLogX" to "/var/www/html/RunLogY"
- TBC
2. Retire Previous RunLog browser:
- Grep source files and replace all "onldb.starp : 3501/3503" with "dbbak.starp:340X", where X is the id of the backed online database.
- TrgFiles.php and ScaFiles.php contain reference "/RunLog/", which should be changed to "/RunLogRunX/", where X is the run ID
- TBC
3. Update /admin/navigator.php immediately after /RunLog/ rotation! New run range is required.
»
- Printer-friendly version
- Login or register to post comments