From Fedora Project Wiki
No edit summary |
(Add info about adding a version.) |
||
| Line 15: | Line 15: | ||
TODO | TODO | ||
=== Release Preparation === | |||
To add a version for release, login to the admin interface at https://admin.fedoraproject.org/mirrormanager/adminview and click on [Add] under Versions. Fill in the request information, and regenerate the publiclist (below) to update the publiclist pages. | |||
=== Troubleshooting and Resolution === | === Troubleshooting and Resolution === | ||
Revision as of 15:38, 4 November 2008
MirrorManager - SOP
Contact Information
Owner: Fedora Infrastructure Team
Contact: #fedora-admin, sysadmin-main, sysadmin-web
Location: Phoenix
Servers: app1, app2, app3, app4, app5, app6, bapp1
Purpose: Manage mirrors for Fedora distribution
Description
TODO
Release Preparation
To add a version for release, login to the admin interface at https://admin.fedoraproject.org/mirrormanager/adminview and click on [Add] under Versions. Fill in the request information, and regenerate the publiclist (below) to update the publiclist pages.
Troubleshooting and Resolution
Regenerating the Publiclist
On bapp1:
sudo su - mirrormanager
then
/usr/share/mirrormanager/server/update-each-server > /tmp/mirrormanager-mirrorlist.log 2>&1 && \ /usr/share/mirrormanager/mm_sync_out
To make this take effect immediately, you may need to remove the cache on the proxies:
# As root on proxy[1-3] rm -rf /srv/cache/mod_cache/*
Hung admin.fedoraproject.org/mirrormanager
This generally happens when an app server loses connection to db2.
- on bapp1 and app[1-6], su up, kill the start-mirrormanager.py script. supervisor will restart it
- on bapp1, if crawlers and update-master-directory-list are likewise hung, kill them too.