#2932 Outage: database and vpn server outage: 2011-09-07 21:00UTC
Closed: Fixed None Opened 11 years ago by kevin.

Outage: database and vpn server outage: 2011-09-07 21UTC

There will be an outage starting at 2011-09-07 21:00 UTC, which will last
approximately 1 hour.

To convert UTC to your local time, take a look at
or run:

date -d '2011-09-07 21:00 UTC'

Reason for outage:

Our primary postgresql server is being migrated from a RHEL5 to a RHEL6 instance.
Our primary vpn server is being migrated from a RHEL5 to RHEL6 instance.

The vpn outage should be very short as vpn resources are moved around. While the database is down, authentication to the wiki will be unavailable, but existing pages will be viewable. Bodhi, accounts, fedora community, pkgdb will not be available during this outage.

Affected Services:

Bodhi - https://admin.fedoraproject.org/updates/
Fedora Community - https://admin.fedoraproject.org/community/
Fedora Account System - https://admin.fedoraproject.org/accounts/
Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
Package Database - https://admin.fedoraproject.org/pkgdb/
Wiki - http://fedoraproject.org/wiki/ (partially affected)

Unaffected Services:

BFO - http://boot.fedoraproject.org/
Buildsystem - http://koji.fedoraproject.org/
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
Docs - http://docs.fedoraproject.org/
Email system
Fedora Hosted - https://fedorahosted.org/
Fedora Insight - https://insight.fedoraproject.org/
Fedora People - http://fedorapeople.org/
Main Website - http://fedoraproject.org/
Mirror List - https://mirrors.fedoraproject.org/
Smolt - http://smolts.org/
Spins - http://spins.fedoraproject.org/
Start - http://start.fedoraproject.org/
Torrent - http://torrent.fedoraproject.org/

Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2932

Contact Information:

Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

Updating mirrormanager to be affected.

This outage is over.

We went over our window somewhat due to a odd vpn issue on the main proxy (proxy1).

Will try and fix things moving forward so it's not such a single point of failure.

Login to comment on this ticket.